New One-click installs: WordPress, WooCommerce, Mage-OS and PrestaShop on any server

See the plans
Magento, WordPress and more1 min readUpdated

Install a Magento extension on a Gen2 server

With Composer over SSH or by uploading the code, then the commands that make it live, ideally on staging first.

Install extensions on a staging copy first, test them, then push the files to live. That keeps a bad extension from ever reaching your customers.

  1. Create or refresh the staging copyStaging tab of the store.
  2. Install the extension on staging

    With Composer over SSH (an SSH user of the staging application):

    composer require vendor/module
bin/magento module:enable Vendor_Module

    Or upload the code to app/code/Vendor/Module by SFTP.

  3. Make it live on staging

    Actions: setup:upgrade, Compile, Static content deploy, then Flush all caches.

  4. Test

    Front, cart, checkout and the admin pages the extension touches.

  5. Push to live

    Push files from staging to live. The deploy steps run on live for you.

Marketplace extensions need your Marketplace keys in Composer's auth.json for that application. Never commit auth.json to a repository.

Using Git? Commit composer.json and composer.lock and deploy from Git deploys: the deploy runs composer install, compile and static deploy into a new release.

Did this solve it? If not, tell us what you see and we look at your server.

Open a ticket

Keep reading

All 4 guides
WordPress and WooCommerce on a Gen2 serverUpdates from the console, caching, wp-cron, file permissions and the settings that matter for WooCommerce.1 min read

Still stuck? Ask a person.

Tickets go straight to the engineers who run ShopWhizzy servers. Tell us the store, what you see and when it started, and we take it from there.

Open a ticket Help center