Web pages are created as Navigation Page.
The navigation page is consisted of Referenced Entities:
- Navigation Carrousel Section
- Navigation Section
- With various display options
- Having items
CMS editor can edit a section within a Page referencing it Or modified it separately.
- You can find a section in Section & Items
- You can find your section by CMS title, Content type, Language
- Click Edit to open the edit form and update your content.
- Save and Publish it
When you open a page to edit, you may see the message:
" This content is being edited by the user "xxx", and is therefore locked to prevent other user changes....."
That means someone is editing the page and you cannot edit the page until the other user finished and unlocked the content.
Meanwhile, you can select another to edit.
On the content list page, you can see if the content is locked or not and for how long already.
If "No", you can open the edit form to lock and start working on it.
The status of the content is still Locked if you are the one who locked it before. The lock is kept max of 15 minutes for a user to edit.
If you need to work on that page and see that the lock is over 15 minutes. You can click on edit and break the stale lock.
The content will be unlocked after saving the content.
You can keep the lock maximum 15 minutes.
After 15 minutes, another user can break the stale lock and work on that page.
In case you need more time to work on this page, you can save the page, then edit it again. You will renew the lock in 15 minutes more.
Please remember to unlock the content when you are done on this page.
You can unlock the content after saving your changes. However, please keep in mind that you continue keeping the lock if you are opening the edit form and navigating away.
If you don't want to edit the page, please click Unlock button below to release the lock.
In case you see any issue with unlocking the content, please send an email to email@example.com or send mail to Havas team.
PLI website has several cache layers. A request will hit cache layer(s) before it reaches out the application in order
- CloudFront cache:
- Lifetime: 24 hours. it can be managed in Drupal Configuration.
- Content and Expire time: vary on region, URL. 1 edge for each region.
- Varnish cache: similar to Cloudfront cache
- Lifetime: 24h
- There is 1 edge for all regions.
- Expire time: vary on URL
- Drupal cache
From CMS admin ( Connected as CMS Power User), normally, your request won't hit Cloudfront cache.
On Front, if you want to bypass CloudFront cache, you can add a dummy parameter on your URL to access the same page, which URL is not yet cached on Cloudfront yet. Next time, you need to change the parameters.
For drupal cache:
- You could be logged as the administrator and click on "Flush all caches" at the top of the admin navigation bar.
For CloudFront and Varnish caches:
- You have to request support to clear caches from the dev-ops team via email: firstname.lastname@example.org
Other caches (For Admin):
- Clear metadata cache: admin/config/media/s3fs/actions
How to view my updates on front
When you access PLI Website CMS as a Power User, and update a page/section, from CMS you will see immediately your changes.
Update a page/section will create a new revision of the page/section.
How to preview changes on CMS?
- View => display the current version on Front
- Latest revision: This tab is displayed when the latest revision is not the current revision and displayed on Front=> display the latest revision that you are updating on CMS
- If the latest revision sate is Draft|Waiting For Approval => your changes are not published yet and not visible on front, for the visitor
- Once the updates are reviewed and published, your updates will be visible on front, for the visitor.
How to test the final display on Front:
However, we have several cache layers mentioned in the "Cache" section. If the visitor's request hit Cloudfront, the latest changes in not rendered to the visitor as they are accessing the old revision.
For some case, from different regions, the user missed Cloudfrong cache and will be the latest revision. The Cloudfront cache will be expire within 24h (max). Since, the cloudfront cache is rebuilt with the latest revision.
- You can test by using dummy parameters to bypass the cloudfront email@example.com
- In case you need to rebuild the Cloudfront cache to ensure that everyone will be see the latest revision, please send email with list of Page URL that you want to rebuild Cloudfront Cache to the Dev team at firstname.lastname@example.org