Rarely a new or modified page is activated, the changes are not visible to all users on the published website.
Published June 8, 2017
Normally page activations go through a process called replication, and are syndicated to all of our publisher servers. Rarely, a page activation does not make it to all of the servers, so depending on which server an individual is viewing, they may not see the changes. A user is temporarily assigned one of the publisher servers and during that session, all pages they view are loaded from that server. Another user may be assigned the same publisher, or a different one, depending on the load.
Which Publisher Am I On?
You can determine which publisher you are on by looking at the HTML source. Often this is through right-clicking your page, the choosing 'View Page Source' (Firefox or Chrome), or 'View source' (IE). A new tab will open, showing HTML code. The very first l;ine of that code will include this text: '<!-- cmspub04 0608-142940 -->' (where the cmspub number will be 01 to 04).
If you can see your changes on cmspub04 but your colleague cannot on cmspub01, you now know that cmspub01 is not in synch.
We are investigating this issue. Please let us know if you believe it has happened to you.
There is no ideal workaround, but you can try activating the page again so the replication process has another chance to work.
When you do notify us, please let us know that you observed different behavior by the publishers, and which publisher was wrong.
And if it is not urgent, please record these details and notify us BEFORE reactivating your page.
Requests submitted by the online forms will be triaged quickly by the UBCMS Help Desk.
Expect UBCMS outages Wednesday mornings from 4:30 to 6:30 during routine updates.
Also, the footer links to documentation provided by our vendor, Adobe AEM. But please note that not all vendor instructions apply to our installation. Some features may not be available, as the UBCMS has been modified to suit the needs of our community.