Before updating, read the release notes and check the requirements for the new version, including compatibility with your Joomla and PHP versions.

Create a complete backup before making changes. For an active store, test the update on a separate copy of the website first.

Installing the Update
To update using the complete installation package:

1. Download the MirandaPlace ZIP package from your AKB Project account.
2. In Joomla administration, go to System → Install → Extensions.
3. Select Upload Package File.
4. Upload the ZIP without extracting it.
5. Wait for installation to finish and review all messages.
6. Open Components → MirandaPlace and check the administration interface.

Install the update over the existing installation. Uninstalling MirandaPlace is not a required update step.

The update process applies the database changes included in the release. If installation reports an error, do not assume that the update completed successfully.

Components, Modules & Plugins
The component, modules, and plugins have their own version numbers. Different version numbers do not necessarily indicate a problem.

Use the extensions supplied or specified for the release. Updating only selected files manually may leave the installation inconsistent.

Checks After Updating
Check the functions used by your website, including:

• category and product pages;
• layouts, images, and frontend modules;
• customer login and the customer area;
• checkout, payment, and shipping methods;
• invoice downloads and protected digital files;
• support tickets and scheduled tasks, where used.

If the interface displays outdated styling after an update, clear the Joomla cache and refresh the browser.

A complete backup must include the database, website files, and MirandaPlace private storage.

These parts work together. A database backup alone does not contain the files attached to its records.

Database
Back up the complete Joomla database.

MirandaPlace relies on both its own tables and Joomla data, including users, extension settings, permissions, and menu items.

Its database records include products, categories, configuration, orders, customer profiles, payment references, download permissions, licences, and customer service activity.

Website Files
Include the complete Joomla installation, particularly:

• components, modules, and plugins;
• templates and template overrides;
• product, category, and manufacturer images;
• other uploaded media;
• configuration.php.

The Joomla installation secret stored in configuration.php is used to protect stored provider credentials. A restore or migration must preserve this secret so that existing encrypted credentials remain readable.

Private Storage
Check the private storage location in Store Configuration → Private Storage.

This directory contains protected files such as:

• invoices and credit notes;
• support ticket attachments;
• digital download files.

The directory may be outside the website root. Confirm that your backup process explicitly includes it.

A backup of the website folder does not automatically include an external private storage directory.

Backup Consistency
Capture the database and files from a consistent point in time. On an active store, coordinate the backup to avoid mismatches caused by new orders, uploads, or document generation during the process.

Keep backups in a protected location and periodically test a full restore on a separate environment.

Restore the database, website files, and private storage together from the same backup set.

Uploading an older MirandaPlace ZIP is not a substitute for restoring a backup: it does not reverse database changes or restore missing records.

Restoring the Installation
After restoring:

1. Check the Joomla database connection and server paths.
2. Preserve the original Joomla installation secret.
3. Confirm that MirandaPlace can locate its private storage.
4. Check filesystem permissions for images and protected files.
5. Test the administration interface and frontend.
6. Verify customer access, document downloads, and digital downloads.

If the server or directory structure changes, the previous private storage path may no longer be valid.

For a working installation, Transfer storage in Store Configuration provides the supported workflow for moving the private files. This operation does not replace a complete website backup.

Domain Changes
When moving to another domain, review payment callback and webhook configuration.

Where supported, use the payment method’s Verify and configure action to check the configuration for the new website address.

Also review menu links, email settings, scheduled tasks, and any external services connected to the website.

Test Copies
Before using a restored copy for testing, review live payment credentials, outgoing emails, webhooks, and scheduled tasks. Configure the copy so that testing does not affect real customers or production transactions.

Restoring an Active Store
Restoring an older backup removes local changes made after that backup. It does not reverse payments or refunds already processed by an external provider.

Before reopening checkout, review transactions and orders created since the backup and reconcile any differences.

Installation or Update Errors

Check:

• that the ZIP is complete and intended for your installation;
• Joomla and PHP compatibility;
• server upload and execution limits;
• available disk space;
• permissions for Joomla temporary and installation directories.

Keep the exact installation error message. If the error mentions missing database tables or columns, report it before attempting manual database changes.

Missing Products or Unexpected Behaviour
Check the publication state, category assignment, language, and relevant menu or module filters.

Also check the category’s operating mode. A category can use an explicit mode or inherit the default from Store Configuration.

Selecting a different Dashboard view does not change category modes or store configuration.

Missing Images or Incorrect Layouts
Check that the image files exist and that their directories are accessible.

For layout problems, review the global layout selection, category overrides, and publication state of the selected layout.

Clear cached output after configuration changes if the frontend still displays an older result.

Unavailable Payment or Shipping Methods
Check that the method is published and that its required plugin is enabled.

Review customer group restrictions, destination rules, product types, and any configured shipping limits.

For online payments, verify credentials, test or live environment, and webhook configuration.

An Order Remains Pending
Check the order’s payment events and the corresponding transaction in the provider account.

A customer returning to the website does not, by itself, confirm payment.

If payment reconciliation is configured, check the scheduled task and its execution results. Avoid asking the customer to pay again until the existing transaction has been checked.

Invoices or Protected Downloads Are Unavailable
Check:

• private storage availability and permissions;
• whether the requested file exists;
• the PDF plugin, when PDF generation is involved;
• the customer’s ownership and access rights;
• download expiry, limits, and order status.

Emails Are Not Received
Check Joomla mail configuration, spam folders, and server mail logs.

Email delivery is separate from saving an order, reply, or other record. Check whether the action completed before repeating it.

When reporting a problem, provide enough information to identify the affected workflow.

Include:

• the installed MirandaPlace version;
• Joomla and PHP versions;
• the affected page or administration section;
• the steps needed to reproduce the problem;
• the expected result and the actual result;
• the exact error message;
• whether the problem started after an update, migration, or configuration change.

For payment or order problems, include the relevant order reference and the approximate date and time.

Screenshots and relevant log excerpts can help explain the issue. Remove passwords, API secrets, access tokens, and unnecessary customer information before sharing them.

If further investigation requires debugging or changes to configuration, reproduce the issue on a test copy whenever possible.

Avoid Uninstalling as a Troubleshooting Step
Uninstallation can remove MirandaPlace database tables or managed images, depending on the options saved in Store Configuration.

Check those settings and create a complete backup before any deliberate uninstall operation.

For routine troubleshooting, start with the error message, configuration, plugin state, and relevant logs.