How to activate your module
Activate a paid mypresta.rocks module from its License tab or with your license key. Your settings stay. What each activation message means.
Activate a paid module from its License tab in your shop's admin. Activation keeps your installation and settings: the module changes from demo to licensed where it already sits.
What we would do
We would keep activation separate from a module update or configuration change, so any problem has a clear cause. Your route depends on the installed module, the selected shop, who owns the purchase and whether you are working on the live site or a copy.
If you also need to change the release or settings, rehearse those changes on a private staging copy with your existing modules, integrations, theme and data. Record the previous configuration. For a release change, back up the shop files and database and rehearse restoring them before the planned live switch. Complete licence activation on the intended live shop, following the installation-type restrictions below.
Choose your route
| Your situation | Recommended route |
|---|---|
| You own the purchase and can sign in. | Use account approval to select the licence from your purchases. |
| Your agency configured the demo, but you own the purchase. | Approve activation yourself, or give the agency the key through a private channel for manual activation. Keep your account password private. |
| You have a paid download but no module installed. | Follow the installation steps below, confirming the destination is the intended live shop before uploading. |
Before you start
- Your shop server must be able to reach mypresta.rocks. Activation always runs online, also with a licence key.
- Sign in to your shop's admin as an employee who may edit the module.
- In a multistore, select the one shop you activate, not all shops.
- Have your mypresta.rocks account login ready, or your licence key.
Nothing is reinstalled and nothing is reset. You keep every setting you made during the demo.
Activate from the License tab
- In your shop's admin, open the module and its License tab.
- Click Activate from mypresta.rocks. A new browser tab opens.
- Sign in to the mypresta.rocks account that owns the purchase.
- Choose the licence and click Approve activation. Unused licences are listed first.
- Go back to the module's tab and wait a few seconds. It confirms the activation and reloads.
The License tab now shows Activated or Licensed. This is the route for most people.
Activate with your licence key
Every licence has a key in the form MPR-XXXX-XXXX-XXXX-XXXX, where each X is a digit or a letter from A to F. You find it in your account: My Licenses, Products, the module, then License & order details.
- On the module's License tab, click Enter key manually.
- Paste the whole key.
- Click Activate key.
You do not need to sign in to mypresta.rocks for this. The shop still has to reach mypresta.rocks: a key does not activate a module offline.
Not installed yet
- Sign in to your account and open My Licenses.
- Open Products and the module, click Download and choose a release compatible with your shop's PrestaShop and PHP versions.
- In your shop's admin, upload the ZIP in Modules, Module Manager, Upload a module.
A paid download binds to the first live shop it is installed on. If the License tab still asks for activation, use one of the two ways above.
Check the result
- After the module reloads, confirm its licence status in the same selected shop.
- Open settings you saved during the demo and check that the expected values remain.
- Exercise the task the module handles. For a product display, check representative products with your actual theme; for an integration, check its result in the connected system.
If the licence is confirmed but the task fails, record that as a functional problem with a reproducible example. Repeating activation will not identify a theme or integration fault.
If a message appears
| Message | What to do |
|---|---|
| Confirm your license in the new tab. If it did not open, click Activate again. | Finish the approval in the new tab. If no tab opened, click the button again. |
| Activation expired. Click Activate to try again. | Start again from the License tab. |
| Activation could not be completed. Please try again or paste your license key. | Try again, or activate with your licence key. |
| Invalid format. Expected: MPR-XXXX-XXXX-XXXX-XXXX | Copy the complete key again from your account. |
| Network error, or we could not reach mypresta.rocks | Try again later. If it keeps failing, ask your host whether the shop server may connect to mypresta.rocks. Opening the site in your browser does not test the shop server's connection. |
| Select a specific shop before changing its license. | In a multistore, select one shop first. |
| You do not have permission to change licenses or support for this module. | Ask an employee with edit rights for the module. |
| Activation disabled on this installation | Read the reason shown with it. Activation is blocked on development or copied installations. Activate on your live shop. |
| Assigned. Automatic activation needs attention. Refresh to try again. | Click Refresh, or Finish license activation if it appears. |
Still stuck? Contact us and quote the exact message. Include the module name and release, PrestaShop version, selected shop, live domain and whether this is a copied installation. Hide the key in screenshots.
More about licences
Support periods, what one licence covers and how domains work are explained in Licensing and support.
Questions owners ask
Why is my purchase missing from the approval screen?
Check which mypresta.rocks account is signed in, especially if your browser already has an agency account open. If the purchase is still missing from the purchaser's account, ask support to check it using your order reference.
What should I ask my developer before a domain change?
Ask which live domain and shop the licence is assigned to, whether a release or settings change is included, and how they will confirm activation after the move. Resolve assignment questions with support before switching domains.