Hello,
Thanks for reporting! We also apologize for the issuer you’ve facing!
Thanks for the explanation too! I understand the issue.
I hope you’ll be able to response on the questions below in order to know what really is causing the issue.
Do you’ve any CJT code Blocks created in the CJT Manager page? If yes could you please do the following:
1. Simply disable all those exists blocks.
2. Create new block.
3. Add any simple CSS code.
4. Assign the new block to the Blog-Index assignment option.
5. Test the pagination and let me know what happened.
Thanks in advance,
Ahmed
Hi Ahmed,
I didn’t have any code blocks, except the default one. I tried (if I did it correctly) your above steps, and it didn’t seem to make any difference with pagination.
Just a note: The theme I’m using uses the WordPress ‘static page’ for the front page, which uses the theme’s custom ‘Page Builder’ to layout and construct the front page using a WordPress ‘Page.’ I’m not sure if that would make a difference.
That said, I had been using a previous version of CJT, v0.8 without any problems on this site and another using a similar theme. The other site has a number of code-blocks, though I’ve left that one at 0.8 for now. This site, I had just installed the plugin in anticipation of using it, so I wouldn’t forget. When I upgraded to v6.0.13, that is when the pagination issue began.
Hello,
Thank you for reporting!
I appreciate you answer.
I’ll add this issue into the queue and start checking in there. I’ll let you know once we figured out what might cause the problem.
Thank you,
Ahmed
Hello,
I’ve tried to figure out what might cause this issue and I’ve a doubt regards few internal procedures that I’ve altered in version 6.0.14.
Version 6.0.14 is just released. Please try it and let us know if you got this issue fixed.
Thanks in advance.
Regards,
Ahmed
No, unfortunately 6.0.14 did not resolve the issue. The behavior is the same as with 6.0.13. Thanks for your effort on this!
Thank you!
Don’t worry I’ll get it fixed and let you know!
Regards,
Ahmed
Just FYI…. 6.0.15 did not resolve the issue either. (The notes didn’t seem to indicate it would, but just wanted to let you know.)
Hi Steve,
Thank you for this information.
We will look into this further.
Regards,
Damian
Just another update re: v6.1
The problem has actually become a bit more confusing with this update. The pagination will work fine, then when the plugin is enabled, will break like before. However, after deactivating the plugin, the problem will still persist for some unknown period of time… then pagination will begin working again. I’m guessing it might be some kind of browser caching thing, as while it’s not working in the browser which enabled/disabled the plugin… it works in another browser at that point.
Anyway, don’t worry about it for now. In a week or two, I’m hoping to have the site it really needs to be in-use on, moved to a new host (I’m just testing it on my site… their site is still using the old version). Once moved, I’ll have the easy ability to create a ‘sandbox’ version where we can update and troubleshoot non-live. If I have issues after update on that site, I’ll let you know. Thanks again.
Hello Steve!
Thank you for helping us discovering this issue! We appreciate the simplification you provided in order to get this issue solved.
It has been along time since you reported this issue. As its only happened with you and only one another user we were in doubt of what is causing it. The issue is solved in version 6.1.2.
Hope that helps.
Regards,
AHMeD
Awesome…. and thanks so much for your hard work and keeping going to finding the problem. That speaks very well to your support! I’m glad I finally had an environment available to help track it down. This kind of thing is understandably difficult if there is only a live site available to work with.
Also, just to fill in a bit more info for others that might be reading this… this problem only presented if the front-page of the site is static (using that WordPress option) AND pagination occurs on that front page. Most of the GoodLayers themes work this way, as they use a ‘Page Builder’ to construct the front page (or any page) of the site out of modules. For modules such as ‘blog’ or ‘portfolio,’ there will often be pagination involved, as there are too many items to fit on one ‘page.’
While I can see that this a rare thing through their experience, I’ve seen more themes doing this kind of thing lately, so I’m guessing more people would have run into this in the future. I’m glad it is fixed, as this is an insanely useful plugin. 🙂
