Fast AJAX gone after 1.3.8

Unfortunatelly, yes.

We were forced to do this by WordPress Plugin Review Team.

They don’t allow to include any WP files directly in the plugin which is required for this mode to work. In our opinion it is 100% ok to do so if you know exactly what you are doing.

This feature will be back however – we plan a PVC addon that will bring Fast Ajax back, and add some more goodies.

hmmm I see.

Okay I’ll try REST APi now. JavaScript doesn’t seem to be counting views right. It dropped to 1/3 of what I used to have before updating.

thanks.

It might take longer time to process the request, but 1/3 is too much of a difference.

Just us us know if you find any issues.

1/3 issue could be the problem that new version is buggy and does not work correctly with jquery as I wrote in the next topic. If you want to fix it, reroll to the previous version until this is fixed…

Yeah I downgraded to 1.3.8 in this site. It’s using Total Cache there.

Hm, we can’t even use javascript because the numbers are wrong and about a half lower. Even though we can see in our logs that the requests were send like 100% of visits just half of it is counted. Only fast ajax is working correctly…

Hi there,
Love your plugin, but with the recent version, we found that the heading in the sidebar is showing the HTML code eg. <h3> quick menu </h3>. Any thoughts on a fix?
Thanks so much.

v1.3.9 still no Fast AJAX option?

@inside83 The WordPress plugin review team has stated that the technique we invented for doing a Fast Ajax requests is not allowed according to their standards.

We were trying to explain that it is 100% safe, tested and working for years without any issues. But without success. So we were forced to remove it from the plugin.

As we are totally for this feature, we are going to develop a custom adddon that will bring this feature back, plus add some more goodies like counting term and author views, CSV/XML data export etc.

• This reply was modified 3 years ago by dFactory.
• This reply was modified 3 years ago by dFactory.
• This reply was modified 3 years ago by dFactory.

@dfactory Us users are totally for it too.

What are they saying? Why isn’t your way compliant with their standards?

I can’t speak for everyone but I’m totally willing to pay for that feature and the option to bypass LiteSpeed’s cache because having to clear all the cache just to update the views in frontend is a hassle and cache takes time to rebuild.

Do you have any ETA on that addon or can I get in touch with you regarding paying for the features explained above?

Or you just don’t update the plugin and use the older version…

@keengamer that still doesn’t solve the LSCache issue or some security fixes which could be resolved in the newer versions

@dfactory 2 weeks later, still waiting for a reply

I just use the old version, no other way around for us…

@keengamer which cache plugin do you use? How do you get around it caching the post view field in the frontend?