nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with publishing to production

Meimei

Hi,

I have a problem with page publishing. Everything is ok when I make a page and publish it to production. But if i change something on the page and publish it again, i cannot see the new version of the page. I still see the first one. What may be the reason for this?

Thanks...

Find more posts tagged with

Comments

tanguyr

Hi,

I have a problem with page publishing. Everything is ok when I make a page and publish it to production. But if i change something on the page and publish it again, i cannot see the new version of the page. I still see the first one. What may be the reason for this?

Thanks...

Have you tried clearing the cache? In CCPro, after changing and publishing the page, check the checkbox next to the .page file and then select "Invalidate Runtime Cache" from the SitePublisher menu.

/t

Meimei

Thanks but yes, i tried that before and nothing changes...

tanguyr

Thanks but yes, i tried that before and nothing changes...

Are you sure your changes are being deployed? If you look on the livesite runtime server(s), do you see your changes in the page files on the disk? Have you tried stopping and starting the livesite runtime server(s)? Have you tried emptying the livesite.cache folder and restarting the runtime(s)?

/t

Meimei

Are you sure your changes are being deployed? If you look on the livesite runtime server(s), do you see your changes in the page files on the disk? Have you tried stopping and starting the livesite runtime server(s)? Have you tried emptying the livesite.cache folder and restarting the runtime(s)?

/t

Yes we look on the livesite runtime server and our pages are deployed. Do we have to clear the cache or restart the server every time we want to see the new version of the page? It will start caching again...
Isn't there a way to give cache time to the pages like the components? Because the component based caching is ok but the problem is with the pages we think. Or how does the 'Invalidate Runtime Cache' works?

tanguyr

Isn't there a way to give cache time to the pages like the components?

I can't think of anything off the top of my head, at least not via the web interface.

/t

tanguyr

One more question: are you publishing pages using the default workflow or did you write your own workflow?

Meimei

One more question: are you publishing pages using the default workflow or did you write your own workflow?

Sorry, it is a late answer but we use the default workflow...

vpatel

Sorry, it is a late answer but we use the default workflow...

Default WF as in PLC workflow? Also on the Runtime side, are you seeing any errors related to refreshing cache in the LS Runtime log?

tanguyr

Sorry, it is a late answer but we use the default workflow...

Sorry for the even later reply Smiley Wink

The reason i asked if you were using the "default" workflow is that the default workflow ("Publish LiveSite Content" - so PLC as vpatel calls it below) has some magic to flush pages from the cache when they are published.

Another thing to check: are you using templates? If you are, take a second to double-check the properties of the components in the template (ie click the "edit" link next to the component name when the template is open in design view) - specifically, in the layout tab, the value of the "Cache Time" dropdown.