Cornerstone and Custom Permalinks conflict

Support
#1

Hi there,
got this error when trying to create a new page with cornerstone: “a conflict on the front end…”

i disabled wp-supercache
i eneabled “maintainence mode” on cloudflare
i purged all cache on cloudflare
i tried with chrome and firefox
i have this in my wp-config file:
define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘1024M’ );
in my WP general settings i have the correct path with https

i don’t know what else to look for. it was working fine before, with the very same plugins installed.
check my secure note for logins.
thanks!

#2

here you can see the rules i set up on Cloudflare, as suggested on various threads here:

also note, that i have a dev copy of the site; on that one, i have disabled cloudflare and other caching plugins and updated X and Cornerstone to latest version.
but i still have the same issue, only difference here is that when opening cornerstone, the big circle icon keeps spinning, instead of giving me the error “a conflict…”.

Please, I’m stuck on this!

#3

well, i found that the issue is a conflict with the Custom Permalinks plugin. This is a big problem as my website has many pages and so many urls are changed through this plugin so, disabling it is not really possible.
Is there any way to fix this without deleting Custom Permalinks?

i found out a very weird thing: on blog posts, cornerstone is loading fine, even for those that uses a custom url modified with “custom permalinks” plugin. On pages, that conflict error occurs.

don’t know if this is useful; on the page where i get the conflict error message by cornerstone, i see this in chrome console:
preview-frame::update-aborted {error: true, message: “incomplete”, response: "↵↵↵↵↵↵↵↵<html class=“no-js” lang=“e…↵} );↵↵} );↵↵ ↵↵ ↵ ↵↵”} cs.js:4446

#4

Why no one from staff has replied to this?

#5

Hello There,

Thanks for writing in! We apologize for the slow response because we have a huge number of tickets over these past several days. It may took as more than 24 hours to respond most of the tickets. By the way, just for future topics, self responding or bumping your post pushes it back in our Queue system so it takes a little longer to respond to.

I have checked your site and it appears that you are using an older version of X(5.1) and Cornerstone (2.0.5). Could you please update to the latest versions?
Our latest versions are:

  • X theme 5.2.2
  • Cornerstone 2.1.3

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.

#6

Hi,
i have a DEV copy of the site updated to the latest X and cornerstone and it makes no difference: if “custom permalinks” plugin is activated, cornerstone won’t load.
i have tried disabling Cloudflare after purging all cache, not using other caching plugin right now. Cleaned browser cache too and also tried with different browsers.
Please help! i can’t get rid of the custom permalinks plugin as i have so many custom urls on my site. At the moment, to work on a page with cornerstone i have to disable custom permalinks, meaning that i have to put the site in maintenance mode for hours, losing customers!

thank you

#7

Hi there,
what really makes me angry, is that i can actually see the page structure and add sections and rows on a with cornerstone, it’s just the preview that it’s not showing. This makes me think that there should be some simple workaround for this.
Check the screenshot (it is the DEV site):

#8

Hello There,

Thanks for updating in! Please keep in mind that Cornerstone is using the default, preset or custom WordPress permalink in Settings > Permalinks. Any changes of the permalink outside of this setting may break Cornerstone. 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.

We’ve added this as a feature request so that Cornerstone support for this plugin can be taken into consideration for future development. All of these items are discussed with our team internally and prioritized based on the amount of interest a particular feature might receive.

Thank you for your understanding.

#9

Hello,
I have this .htaccess to load the https version of my web:

RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*[^/])$ /$1/ [L,R=301] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://mysite.com/$1 [R=301,L] RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L]

And Cornerstone wont load until y resave permalinks (so until I reset my .htaccess to the wp standard one).

Not good.

#10

Hi,

I would like to check but the wordpress admin login no longer works.

Please navigate to Settings > General and make sure the urls are https.

No need to edit your htaccess after that.

Hope that helps.

#11

I know this is a really old thread, but the developer of the Custom Permalinks plug-in has posted a solution that can disable the redirection function, which is responsible for the Cornerstone conflict. Here’s the function you can use, that retains the Custom Permalink functionality, but prevents the 301 redirects it creates.

function yasglobal_avoid_redirect( $permalink ) {
  return true;
}
add_filter( 'custom_permalinks_avoid_redirect', 'yasglobal_avoid_redirect' );
1 Like
#12

Hey @instyletech,

Thank you for sharing your idea, we really appreciate it.

Cheers!