If you're seeing discrepancies between your asset in Cascade CMS and on your live website, see the steps below for possible resolutions:
Verify that you’ve submitted the job for publishing.
After creating or editing an existing asset in Cascade CMS, you must publish your asset in order to see your changes on the live website.
Your organization may have the system configured to send you through a Workflow which will automatically publish your changes. If it does not, however, you will need to publish the asset to one or more Destinations manually.
If you don’t see the Publish option on screen while viewing your asset, you may be viewing a Draft of your asset (in which case you’ll first need to Submit your changes) or your Role in the system may not allow for you to publish assets (in which case you’ll need to contact your CMS administrator for assistance).
Verify that the job has been processed.
The next step in determining what might be happening with a publish job is to see if it has been processed at all yet. When publishing an asset (or assets), the job is sent to the Publish Queue prior to being physically transferred to your web server(s). Your Site Role in the system will determine whether or not you can view the Publish Queue.
If your publish job is still in the queue behind other assets waiting to be published, you’ll need to wait for those jobs to be processed before your changes will appear on the web server.
If you do not have the ability to view the queue, you will need to contact your CMS administrator to have them check the queue for you (or to give you the ability to view the queue yourself).
If you don’t see your publish job in the queue at all, there is a chance it may have been processed already. In the event that a publish job has been processed, it will trigger a publish message that will be sent to your Notifications (at which point you can see if it resulted in any errors).
Check your Publish Notifications for completed publish jobs.
Once your publish completes, you will receive a Notification containing more information regarding the status of that job. You can view your Notifications by clicking on your avatar (top right) and selecting Notifications. The Subject line for a publish job will look something like the following:
Publish of <asset> "<asset-name>" completed (# issue(s))
Clicking on the Notification will show you more details including the number of successful jobs, errors, and skipped jobs pertaining to your publish. You’ll also be able to see to which Destinations (web servers) your publish job was transmitted.
If you’ve received a publish message showing that your job was successful, but still don’t see the changes on your website...
Verify that you’ve published to the correct Destination (web server).
The publish message you received in your Notifications will outline to which Destination(s) your files and/or pages were published. Under Successful Jobs, you’ll see the Destination listed first for each item that was published. For example:
[Destination: My Web Server] Main Website: files/images/banner.png
If you don’t see the Destination listed to which you intended to publish, you’ll want to try publishing your asset(s) once again and be sure to select the proper Destination(s). If you don’t see the Destination available when you click to publish it, you may not have access to it. In this case, you’ll need to contact your CMS administrator to have them include you in one of the Applicable Groups for that Destination.
Clear your browser cache and/or try a different browser.
Occasionally, your browser will load a cached version of the page or file that you’re attempting to access on your web server(s). To verify whether or not this may be the case, try clearing your browser cache or use a different browser (one you don’t normally use) to see if the problem persists.
If you’ve received a successful publish message, cleared your browser cache, tried a different browser, but still don’t see the changes on your website...
Check the timestamp of the file on the web server’s file system.
Unless you happen to have direct access to the web server, this step will require that you contact your web server administrator for assistance. The goal here is to see if the timestamp (last modified date) of the file in question matches the approximate time when you attempted to publish from Cascade CMS.
If the timestamp of the file in question does not match the approximate time of the publish window, the file is either never reaching this web server or it is ending up in a location that you’re not expecting (in which case a search of the file system for the name of the file you’re publishing may point you to the location of the published file).
Verify that your Transport/Destination are publishing to the proper location on your web server.
Depending on your role, this step may require that you contact your CMS administrator as well as your web server administrator for assistance.
Cascade CMS determines where to place files using a combination of the following values:
- The Transport Server Directory (if blank, the FTP/FTPS/SFTP user’s home directory)
- The Destination Directory
- The folder path of your asset in your Site
For example, consider the following setup:
DestinationAhas a Directory value of prod
www.example.organd is using
TransportAhas a Server Directory value of
- A file in the same Site as
DestinationAis located in
By combining the Transport’s Server Directory (
/var/web ) with the Destination’s Directory (
www.example.org ), we end up with the path
/var/web/www.example.org as the Site’s root directory. Then, we append the location of the file itself as it resides in the Site. The final publish path of this sample file will be
Using this logic, you can figure out the location on the web server file system to which your file(s) should be publishing.
**WARNING**: Changing Transport and/or Destination directories can have serious consequences for your live web sites. DO NOT make any changes to these areas of the system without consulting with your CMS and web server administrators.
Find out whether or not your web server is caching.
Some web servers are configured to cache files. You’ll need to reach out to your web server administrator to see if the web server in question has this setting enabled. In the event that it does, you may notice that the changes eventually show up (after a particular interval of time). Your web server may also have an option to bypass the server cache by appending certain characters to the target URL (
?resetcache=1 , for example), but your web server administrator should be able to confirm the proper parameters for your organization.
If you’re still having trouble...
In the event that you’re still having trouble or you’re seeing an error message somewhere that you need assistance with, reach out to our support team here and we’ll be happy to help troubleshoot further!