Submitting a change is the equivalent of saving the information to the Cascade CMS system. However, changes made in Cascade CMS are not visible on the live site until the asset(s) are published.
- How do I publish?
- Why do I get a red error message when I try to publish?
- Why do I get a yellow error message when I try to publish?
- How much time does it take an asset to publish?
- How can I see the progress of my asset being published?
- Why has my change not shown up on the live site?
1. How do I publish?
Follow our tutorials on publishing pages/sections and files.
2. Why do I get a red error message when I try to publish?
If you receive the above message, it means that the asset is not set to publish. Learn how to adjust this setting.
3. Why do I get a yellow error message when I try to publish?
The yellow error message, “This asset has already been queued for publish,” occurs when an asset is already waiting to publish.
When you publish an asset, you can still make changes to it up until it actually publishes, and those changes will be published with the initial publish job. An additional publish request is not required.
4. How much time does it take an asset to publish?
Depending on the size of the asset or folder being published, it can take just a few seconds or several minutes. If a folder contains multiple assets, it can take longer for the publisher to process them.
5. How can I see the progress of my asset being published?
Learn how to view the publisher's active jobs.
6. Why has my change not shown up on the live site?
There can be a number of reasons why the asset is not being seen. The primary reason may be that the publish simply has not gone through yet, but is pending due to other assets being published. Learn more about the publishing queue.
If the publish has successfully gone through, but still is not visible on the live site, try:
- Refreshing the browser page (F5)
- Clearing the browser history
- Restarting the web browser