Cannot replace a page with one of the same name that will open in Cornerstone (Ep.2)

Support
#1

In regard to my earlier post that was closed before I could finish troubleshooting the issue:

I have tried rebuilding the page in Cornerstone (as suggested by one of you support team members) making sure that the content was not edited somewhere else and this failed. I believe there is a conflict with Cornerstone reading an older database file that is not allowing a page to be rebuilt with a page of the same name. After rebuilding the page I was able and can open it in Cornerstone as a Draft but not as a Published page.

#2

Hi @colink,

Thanks for reaching out.

I replied to your other thread, but to make it clean, please provide your site’s URL and admin login credentials in the secure note.

Page name is not required for the builder to work and it has no direct access to the database. All features and codes are running on top of the API’s provided by Wordpress. It could be cache or host-related issue since it only happens on the page with the same name.

Thanks!

#3

Hi @Rad

I’ve tried a number of ways to troubleshoot this (including cache dumping, and contacting our host) but have not been able to resolve it. The only page in our site that has been affected is https;//reportsnow.com/downloads. The only way I can open it in Cornerstone to edit the page is by changing it to a Draft. Opening it directly in Cornerstone produces a Preview Error. I’ve also tried opening it in other browsers as well as Incognito in Chrome which all give me the same results.

Credentials in a Secure Note.

Thanks!

#4

Hello @colink,

Yes, I can confirmed that you can only see the preview when the page is in draft mode. As soon as you published the page, you will see an error. When I checked the page in the editor, it is resulting to an error 404 as if the page does not exist. Do you have any other page redirects, slug og maybe ID conflicts? This could be caused by a 3rd party plugin. You could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Please let us know how it goes.

#5

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