Problem with cs_content_seo

Hello guys,

I noticed on one of our page that the content was duplicated / broken at the bottom of the page and it seems to be related to the cs_content_seo shortcode.

I re-saved the page multiple time without luck.

Details in secure note.

Please advise!

Thank you

Hi @thisisbbc,

Would you please kindly make sure that the post in question does not have any customization? I see that there is a Javascript code added as a custom JS.

I suggest that you duplicate the post and try to remove and JS or CSS code that is added and also try to remove the sections one by one and see if it fixes the issue.

That way you will find the problem cause.

Thank you.

Hey @christopher ,

Thanks for the suggestion.

Note that the JS is added in a global block (the left side menu) and is injected on many different pages of our Legal section without this happening.

The page in itself has no custom JS or CSS applied.

It seems to have something to do with an update because when I went to our ToS page and made no change but just re-saved the page, the problem started to appear also on this page.

So we have made no changes to the pages but now if we save them in Cornerstone we have this weird bug appearing.

I tried to create a new page for our Return Policy but had the same issue, then deleted everything but the issue persisted. Then I came back to our Return Policy page and it was fine? But now our ToS page has this problem and I have no idea how I fixed it on the Return page…

There’s definitely something weird going on.

I deleted everything in our ToS page and there was still this bit of cs_content_seo.

I deleted everything in our global block, but still the issue persisted.

I then re-saved the empty ToS page and it was rendered blank, phiew…

I added everything back in the Global Block, saved it, added everything back in the ToS page, saved it and now the problem went away.

I literally haven’t made any change to the page except delete/re-create content. Not sure what happened.

It seems the issue is resolved for now!

Thank you

Glad it fixed now, it could be an internal or external caching related issue.

Cheers!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.