Custom Permalink Conflict with Cornerstone... since 2017

[cpennetier]

Hello,
The conflict between “Custom Permalink” and “Cornerstone” is known since 2017 and I don’t find a real solution on the forum (except disable temporaly the plugin).
The BIG problem with the desactivation of the plugin is, in same time, all these internal links are broken so the site is unuseable

Thanks for your answer.

[friech]

Hi Cedric,

Thank you for writing in, can we see your custom permalink structure? Or are you referring to a plugin? Please note that we can not provide support for 3rd party plugins, you need to contact the plugin author instead.

Cheers!

[cpennetier]

Hi Friech, I refer to the plugin “custom permalink” [https://wordpress.org/plugins/custom-permalinks/].
And my structure is for all pages mywebsite.com/[custom_permalink], without .com/…/…/[custom_permalink]

Thanks

[cpennetier]

Or have you got a recommanded custom permalink plugin without cornerstone conflict?

[ruenel]

Hello Cedric,

What custom permalink are you using? Do you know that you can also set a custom URL for the X/Cornerstone in the settings? Kindly go to X > Settings > Custom Path to prevent any conflict. If nothing is helping, provide us access to your site so that we can check your settings. Please create a secure note with the following info:
– Link to your site
– WordPress Admin username / password
​
To know how to create a secure note, please check this out: https://theme.co/docs/getting-support

Regards.

[cpennetier]

Hi Ruenel, Custom path doesn’t work.
Find my access in the secure note.

[cpennetier]

[rad]

Hi @cpennetier,

Unfortunately, there is no solution to this issue as of the moment. It’s just that cornerstone and any other plugin has no capability to predict what custom path is being added by another. The permalink always need a cue that separates it from each other else there will be conflicts, and it’s something registered to the system instead of just changed by another plugin. That’s why even custom post type requires rewrite declaration upon its creation, and not by after creation. Based on my personal experience, it can happen anywhere and it’s not just cornerstone related. For the stability of the builder, any permalink rewrite should be avoided, I’m not saying we just stop there, we’ll continue investigating this but this is a complex one that needs further checking given the Wordpress itself has its own limitation for permalinks.

Thanks!

[cpennetier]

Thank you.
I cannot ignore rewriting because it is an essential request made by the SEO agency. For them, the url rewiting is essential for a well referenced site.
Tell me when you have a solution, created by you or a plugin that avoids this problem

[christopher]

Hi Cedric,

To make sure that we are on the same page, this is happening because you use a third-party plugin that changes the original permalink structure of WordPress. This is a conflict with a third-party plugin and outside of our support scope.

As my colleague mentioned we will do our best to improve upon the possibilities of supporting such changes in the URL structure but there is no guarantee and no ETA and we do not recommend you rely upon the prospect of that for your project.

The suggestion that we have is to use the original WordPress Permalink structure or find a way to force the third party plugin to avoid changing the structure for the whole website and exempt the URLs that Cornerstone uses.

Thank you for your understanding.