Hi rolfkrueger,
Thanks for your message.
Are you 100% sure that it is our plugin because I have tested the latest CJT version 6.1.2 and WP 3.8 and it all works fine. Can you please provide the webpage so that I can take a look.
Regards,
Damian
Hi Damian!
I now tested everything thoroughly on a fresh installation. The error seems to be connected to our theme “Enfold” (www.kriesi.at), a very popular theme. It occurs on pages built with the advanced layout editor. But it’s only with the latest versions of both.
I will post the problem in the support forum there.
Blessed holidays!
Rolf
Hi Rolf,
Thanks for letting me know.
Enjoy your holidays too.
Regards,
Damian
Hi Damian!
I checked back with Kriesi but they found nothing. So I tested again and found out, that CJT version 6.1.1 works fine on my installation!
So the problem must be something that changed between 6.1.1 and 6.1.2 – which I understand is virtually nothing (“Fix: Break WordPress frontend page pagination by issuing 301 redirect.”). But maybe you have introduced another change which didn’t make it into the changelog? Remember: It’s only broken on pages which are build by using the visual page editor of the theme. Could you have a look?
Regards,
Rolf
Hi Rolf,
Thanks for your investigations and feedback.
Ok, we need to study the case. We will keep you posted.
Regards,
Damian
Hi Damian,
is the issue resolved with the new 6.1.3?
Just for curiosity: Why have you removed so many features in 6.1.3? (Or do you mean something else by depreciated?)
Hello Rolf,
The “Break WordPress frontend page pagination by issuing 301 redirect” fix seems nothing but its very MAJOR change. CJT <= 6.1.1 prepare all blocks associated with the request within “wp” WordPress hook action while CJT > =6.1.2 is using “template_redirect” hook filter to do that. “template_redirect” hook filter is being fired and processed by WordPress for canonical URLs. So I believe that this filter is not being fired on your WordPress installation might be because of the theme or another Plugin.
Hope that helps.
Regards the deprecated features. Yes we’ll remove all those features from the FREE/Community edition within the next COMMUNITY releases. We just correcting the development path. CJT start by developing only the Community/FREE edition and was totally developed for appreciating WordPress community as the development required investigation to keep we just developed the PRO edition with some extra features. We just found that those features is classified as ‘EXTRA TOOLS’ and should be available only on the PRO edition. The FREE edition would still has all the main/core features so everyone would still use both however only PRO utilize from the EXTRA TOOLS.
Regards,
AHMeD
Hi AHMeD,
thanks for the info. So maybe using the “template_redirect” hook filter was not that perfect? Could you offer a choice via the settings?
Regards,
Rolf
Hello,
May be its not the perfect one however CJT Plugin trying to prepare the request blocks as early as possible, we just use the earliest HOOK that fired after the canonical URL has been processed.
We already studied the setting method. We just found it shouldn’t be a setting as most users doesn’t really know what it doesn’t mean and no one are going to change it as the template_redirect hook must be fired as its a WordPress built in hook!! However its internally developed as an ‘INTERNAL CONFIGURATION’, you can change it manually through FTP access: In the Plugin root folder there is a file named ‘configuration.inc.php’. On line No 10 you’ll find the following line:
‘core’ => (object) array(‘siteHook’ => ((object) array(‘tag’ => ‘template_redirect’, ‘priority’ => 11))),
Change ‘template_redirect’ to ‘wp’ and let mw know what happened.
NOTE: After doing that you just hacked the Plugin and you’ll lose those changes after upgrading to the next version. Its just a temporary solution and a way to debug.
We’ll investigate this case and let you know what we’re going to do.
Have that helps.
Regards,
AHMeD
Hi Ahmed,
I’m sure you saw this but in case not: http://www.kriesi.at/support/topic/advanced-layout-editor-crashes-with-css-javascript-toolbox-since-2-5/
Moving the priority in your config file to 5 makes it work.
Hello!
In fact, I didn’t saw it!
Glad they got it solved.
Definitely I’ll check this solution, I’m not sure if this is the case with all other Themes so I should study it first.
Thanks for the info.
I’ll consider it
Regards,
AHMeD
