Editing Pages with Cornerstone - Outputted page has Duplicated Content and Strange Short-codes

Support
#1

Hey Guys,

I’m currently trying to edit a page using Cornerstone. Any update or change I make, I end up with the content I saw in the editor twice on the final page and the shortcode: [cs_content_seo].

This wasn’t happening before the latest update and seems really strange, I’ve tried disabling all my plugins but cornerstone and still get the same duplicate content. I think this might be related to Cornerstone and/or one of the editors.

Here’s a more specific screenshot of what I’m seeing with the same content area twice:

image
image459×789 33.6 KB

VS. what I see in the Editor:

image
image1425×669 210 KB

I’ve also tried clearing the X / Cornerstone theme cache and using a diff browser / clearing cache cookies on current browser.

Any help!

Thank you,
C

#2

Hello @clovisd,

Thank you for the very detailed post information. I can confirm that the issue is happening in your page. Could you please update to the latest versions?
Our latest versions are:
- X theme 7.2.0
- Cornerstone 4.2.0

This latest release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/).

After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

Please let us know how it goes.

#3

Hey there,

I am running both of the above stated versions.

I’ve also included User/Pass in the Secure Notes in case you want to take a look.

Thank you,
Clovis

#4

Hello Clovis,

In the backend, I can see that the theme is updated to 7.2.0 already. When I check your site, it is still displaying 7.1.2.

NGWgyZ06SoCBIQEutBhdxg
NGWgyZ06SoCBIQEutBhdxg790×493 100 KB

I found out that you are using CloudFlare. Right after your updates, please log in to your CloudFlare account and purge your site cache. You also need to regenerate the minified CSS and JS files in CloudFlare.

#5

Hey there,

I flushed out / purged everything on the CloudFlare end.

None of my CSS or JS where minified through CloudFlare, I went ahead and checked, then unchecked the Autominify section just as a precaution.

I’m still seeing double of what I should be seeing on the page I’m editing.

Thanks,
Clovis

#6

Hey Clovis,

It looks like your setup allows for the old version of the theme to run even you already updated in the backend. Please temporarily disconnect your site from Cloudflare so we’re sure no optimization is causing this issue.

If that can’t be done, please copy your site to a staging server.

After you’ve disconnected Cloudflare or copied to staging, give us FTP access.

Thanks.

#7

Hey there,

I’ve disabled CloudFlare optimizations across the entire site (unchecked the little Orange cloud).

The server the site runs on doesn’t have an FTP server installed / access available.

You should be able to install a File Management plugin in the Admin area to navigate the files?

Thank you,
Clovis

#8

Hello Clovis,

We recommend that you provide us your CPanel settings. We need to check if there are other caching methods that you server have because in the backend, the theme is updated but then when we view the live page, it only displays 7.1.2. There might be Varnish or other cache mechanism in the server. Please provide the CloudFlare access to so that we can simultaneously purge your caches and test the site.

Thank you in advance.

#9

Hey @ruenel ,

This website is running on its own VPS with a pretty web hosting stack running Nginx, PHP, & MySQL on a Linux Ubuntu 18.04x. I don’t have a CPanel or any sort of hosting panel.

This should be the relevant info I could get from the Wordpress status page.

This is the PHP Sysinfo Page: https://drive.google.com/file/d/
Thank you for all the help,
Clovis

#10

Hey there,

I just restarted Nginx and it seems to have updated and fixed my problem.

I’m sorry for wasting you time, I hadn’t realized it was that simple. I’ll have to do some digging into my Nginx install to figure out what Caching mechanisms it might be using to make sure this doesn’t happen again.

Thank you for all your help,

  • C
#11

We’re glad that you’ve found the cause of the issue, C.

#12

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