AJAX posts not working consistantly

Just in JavaScript. When we fire the new function you made available (on AJAX page load) we need to be able to tell what page the user just loaded.

• This reply was modified 4 years, 12 months ago by Exavior.

I understand, hopefully in upcoming versions i will push the page number in object and also improve the settings page layout.

It looks like your plugin breaks if the article URL has query string parameters. That is REALLY bad since that’s a requirement of almost all professional sites.

For example. https://www.somesite.com/article/?a=123&b=456

If there are query string parameters the article just loops back to page 1 if you try and navigate.

How soon do you think you could have that fixed?

@exavior please send me the actual URL where you are facing this problem. I have tried it on 2 different websites with Ajax option and both are working as expected. I am sharing one of these with you.

https://demo.guavapattern.com/?page_id=443

Please check and give your feedback.

Your example functions differently than what I have. You have no /#2 at the end of the URL for your 2nd page.

I can’t post the URL here as it is for a campaign that is not yet live (due to this issue)

Your example has the page number as a query string parameter. Are you sure you are using AJAX for that? It looks to me like the entire page is reloading in your example, which is not AJAX.

@exavior please check this video

Your query string is updating with new parameters. Are you sure you are not overwriting your method from AJAX to something else at the post level? I’m also seeing a loading animation and the whole page getting darker, which don’t appear to be standard features of your plugin. Are you testing with the same plugin people like me are using?

Either way, what you are showing does not match what I’m experiencing.

Why do I have site.com/article/#2 for page 2 and you do not? Your example has a query string parameter for the page, which suggests the page has been reloaded.

Step 1 for you should be to make sure you have the same experience I do, with the #, then try adding custom query string parameters and see how it breaks.

@exavior please send me a screenshot of your settings page and also confirm if you are using basic version or premium version?

As we talked about here on this very page, we are using premium.

Here are my settings on 2 screenshots.

https://snipboard.io/X5tcBs.jpg
https://snipboard.io/783l1X.jpg

Again, we’re using AJAX and your plugin uses #2, #3, #4, etc for the pages, your example did not.

@exavior please again check your post, are you using nextpart or nextpage as a separator? Secondly, latest version is 2.6.7, you are using 2.6.3. Can you please update it?

The code, as created by your plugin when it translates WordPress’ standard page break is as follows:

<!-- wp:nextpage -->
<!--nextpart-->
<!-- /wp:nextpage -->

The above code also shows as invalid in the WordPress default visual editor, which is not good. It would be nice if it could function with a standard element like the normal WordPress page break.

I can update it, but since you’ve chosen to make the “premium” version so it can’t be updated locally from WordPress, doing these manual updates is quite a headache, and not something I look forward to doing often… and clicking the link for updating the “premium” version takes you to a page for installing some 3rd party update plugin with NO links to download the actual update…

To make matters worse the official plugin page is a 404 error… https://androidbubble.com/blog/wordpress/plugins/jquery-post-splitter

So how exactly am I expected to update this? I’m for sure not planning on installing some random 3rd party auto-updater for this.

I’m sure you can see how upsetting this all is. This plugin has potential, but so far all we are getting is headaches and disappointment.

• This reply was modified 4 years, 11 months ago by Exavior.
• This reply was modified 4 years, 11 months ago by Exavior.

@exavior

You are talking about this page break

Page Break Block

Give me a little time to work on it, i will update you soon. The blog post you are referring to, was having some slug update issue, it has been resolved. And about 3rd party plugin and and premium update, that is not compulsory, that is just an option, kindly ignore that.

And about making changes in local, you can make for sure and share with me if you want and i will improve the script. Your contribution will be acknowledged in changelog.

I am sorry, this page-break method is upsetting you and i can understand that you are not comfortable with it. But it is not a bug, you can consider it an alternative method. Or actually older method which was in practice in previous WordPress versions. I will surely update it soon with the blocks functionality.

Kindly be in touch with me through e-mail regarding premium version concerns, this support forum is about basic version and bug reports in free features.

I am working on it and will update you soon, please wait.

@exavior i am releasing another version with this improvement. Meanwhile you can test it on the following url.

https://demo.guavapattern.com/?page_id=447

I am using blocks and WordPress default page break.

I used WordPress default page break when I first installed the plugin, but a message popped up saying that page break was not supported by the plugin and it asked me if I would like the plugin to automatically convert them for me, so it did, and it converted them to the code I showed in the previous post.

Has that changed since I set this up a month ago with the non “premium” version?

The example URL still shows your page number as query string and not as #2, #3, #4, etc. Why is that? Is that related to it being a newer version than last one you gave me?

@exavior, earlier it was not working with default page break and a message was popped to convert all “nextpage” tags to “nextpart”. The reason was, jQuery splits. Because WordPress automatically splits and inserts numeric pagination if we use “nextpage” so in earlier versions, i was using “nextpart” to avoid conflicts. But now, it should not matter, either you convert or not, posts should work.

Why that message still pops up?
For a couple of versions, i have to wait so existing users can report if they faced any problem after recent updates. Backward compatibility is important, that’s why i am updating it gradually. You may ignore that message.

The example URL still shows your page number as query string and not as #2, #3, #4, etc. Why is that? Is that related to it being a newer version than last one you gave me?
Query string is the default behavior of WordPress pagination. I was using # earlier but that was refreshing the complete page. This change has been made a few versions ago that only specific part should load, not the complete page.

Thanks