Setting up a separate machine (recommended)

  • Install the latest version of Cascade CMS.
  • Create a backup of the production database and import it as a new database. Organizations using MySQL should verify that the collation of the new database is configured properly according to step 5 here.
  • Configure the test instance to point to the test database created in the previous step.

Disable publishing to destinations

Issue the following query to the database to prevent test assets from being published to your production web servers:

UPDATE cxml_destination SET isEnabled=0;

If you are testing the software using your production database and looking to test publishing, you are encouraged to set up a test Destination that points to a test/staging server.

Disable email notifications

Issuing the following query to the database to prevent Workflow emails and LDAP synchronization emails from being sent from the test instance:

DELETE FROM cxml_preferences WHERE fieldName LIKE '%smtp%';

Disable all 3rd-party Connectors

Issue the following query to prevent Connectors such as Google Analytics, Wordpress, and Twitter from syncing or being published to:

UPDATE cxml_connector SET isVerified =0;

These can be selectively re-enabled by re-verifying these connectors in the Connectors area of the software.

Disable the Siteimprove Plugin

Issue the following queries to prevent the Siteimprove plugin from running checks on pages in the test instance.

UPDATE cxml_preferences SET fieldValue = 'off' WHERE fieldName = 'system_pref_siteimprove_enabled';
UPDATE cxml_preferences SET fieldValue = null WHERE fieldName = 'system_pref_siteimprove_token';

Wrapping things up

  • Start Cascade CMS.
  • Enter a valid license for the test/dev server (since the database was copied from production, the license for the production machine is stored in this database. It will not work as it has a different internal host name/IP). If this is your first time setting up the test instance and you need a license, contact Hannon Hill support and be sure to provide us with the internal host name of the machine on which you have installed Cascade CMS.
  • Navigate to Administration > Preferences > System > General and change the System URL field to reflect the URL at which your instance of Cascade CMS is hosted. Change the Organization Name to indicate that the instance is a Test or Development instance (so that Users are aware of what instance they are working in).

Using the Production Machine (not recommended)

Follow the same steps listed above. You will not be prompted to enter a new license on startup (since the new instance of Cascade CMS is running on the same machine which has the same internal host name/IP). 

Prior to starting Cascade CMS,  modify the port settings such that they do not interfere with the running Production instance of Cascade CMS.

Did this answer your question?