Conflict with Cornerstone

Hi @venenifer

I have heard first time about the conflict of this plugin with cornerstone. I don’t remember that anyone have reported this before. so, you can’t say that it’s a

well known issue

Anyways, would be check the issue if there it is.

Regards,
Sami

Hi Sami,
thanks for your reply!

i have been using your plugin for a long time on my website. it is built with X Theme and their Cornerstone page builder. It has worked for years but after some major update to cornerstone, it started giving the following error in some circumstances (eg: if Custom Permalink is activated):
“A conflict on the front end of your site has prevented the preview from loading”

you will find many threads in their support forums regarding this, but they have not provided a solution yet. I understand this is probably an issue on their end rather than yours, but after weeks trying to find a solution, i though i could try asking you for help.

Thanks for your time and for your very useful plugin!

kindly,
Val

Hi Val

Thanks for your detail reply. I’ll check the Cornerstone Plugin once i get time but as per your said that “it started giving the following error in some circumstances”. So, can you define any 1 circumstance of it.

Thanks,
Sami

Hi Sami,
sorry, i meant that this error in cornerstone can happen for various reasons such as caching issues, low wp-memory-cache in wp-confing, etc.
One of these reason is, when Custom Permalinks is activated. If so, the error occurs 100% of the times on every page that uses a url customized with your plugin.

Thank you,
Val

This is the latest response I got from Cornerstone (X theme) support team:

“The problem with Custom Permalink plugin is that it uses a redirect 301 which caused the issue. Since this plugin is not supported in Cornerstone, the only option is to disable the plugin when you edit or create a page.”

@venenifer Thanks for your feedback. I doesn’t know much about the cornerstone but tried to solve the conflicts.

I have found 1 conflict which has been solved. That conflict is related to the redirect 301.

I don’t know does it their some more conflicts or not. So, i request you to please test the latest version (v1.2.6) of the Custom Permalink with Cornerstone and provide your valuable feedback.

Thanks,
Sami

This issue is still there.

See this image for the error: https://ibb.co/mUrRQ7.

Resolving this issue as it is quite old thread. Let’s discuss this issue in the latest thread created by @djinnie

Regards,
Sami