Staging Environments

Staging Environments

CRU mainly uses staging environments for new website builds as well as to test major core and plugin updates as well as major development changes before updating live sites.
CRU offers temporary staging site environment access to clients who wish to test changing pages, layouts and content changes or other testing or learnings that they do not want to perform on their live site.
Clients need to consider and understand the following:
  • CRU uses these Staging sites and may need to be reset them at any time. If a client wishes to use one then communication with CRU when and for how long in use should be sent as a ticket to ensure no developer overlap or overwrites.
  • Client do not have access to ‘Push’ any changes from Staging to Live, nor can they “reset” the Staging environment. CRU would have to reset Staging at the request of the client via a ticket.
  • CRU would have to push any changes from Staging to Live which would be charged as a CRU TASK depending on which files need to be pushed.
  • Staging sites consist of assets, such as images or videos, and database copies. We have the option to push just assets, or just database changes, or both. It should be noted that overwriting live site databases and files should only be done by CRU developers to avoid any breakages and possible loss of data.
  • Due to the nature of our website builders the database is also used for adding images to the site which are not hardcoded into the original theme. Even if a small image change is added, we are unable to push that change without overwriting the entire database with potential loss of any orders within the timeframe of the last staging reset. Therefore we advise copying your work onto the live database after testing first on the staging. Alternatively and recommended, you can simply push to “preview” in the live site first and test changes before publishing live.
  • Staging sites also have “blocks” on them to prevent such things as subscription orders triggering. Therefore some functionality may be limited for testing purposes.
  • Staging environments do not have the same server resources as Live environments and will have limited speed/performance. CRU cannot increase these resources as these are set. 
If you are interested in utilising a staging environment, please submit a ticket to support.

    • Related Articles

    • User Switching - Features

      View Guide Links at the bottom of the page Installation 1 CRU CREDIT Setup (optional) 1 CRU CREDIT Ease Of Use Easy Want this feature? Request Here Purchase CREDITS  Here This plugin allows you to quickly swap between user accounts in WordPress at ...

    • FooEvents PDF Tickets - Troubleshooting Guide

      How to scan ticket barcodes and QR codes using FooEvents and WooCommerce One of the biggest challenges experienced by most event organizers is managing attendee access. Ensuring an organized and steady flow of attendee check-ins is critical, and if ...

    • CRU CONCIERGE

      CRU CONCIERGE is our full set and forget management service that passes all aspects of website management and responsibility onto the CRU TEAM. CRU CONCIERGE is only for clients on our CRU 360 plans.  For more details on plan inclusions see the CRU ...

    • Guide to purchasing CRU Features

      Clients may want to add new features to their website to extend its functionality from time to time. CRU is building out our feature list to ensure our clients have access to extend their stores based on their specific requirements. Plugin Features ...

    • Xero Integration - User Guide

      For pricing and how to add to your website see at the bottom of the page. Setup and Configuration To set up the connection between your WooCommerce store and Xero account, there are two steps: You will need to create a private Xero application in ...