Skip Navigation

[Resolved] 500 Error loading admin-ajax php file on archive loop with ajax pagination

This support ticket is created 2 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

This topic contains 3 replies, has 2 voices.

Last updated by Jamal 2 years, 9 months ago.

Assisted by: Jamal.

Author
Posts
#2118989

I am trying to:
Load and search archive loops using ajax

Link to a page where the issue can be seen:
hidden link
I expected to see:
Ajax functions working
Instead, I got: Just a spinning wheel and a console 500 error. On a testing clone site I was able to remove the console error when deactivating the toolset blocks plugin. The server host also informed me it was not an issue with the server but a plugin issue.

#2119047

Jamal
Supporter

Languages: English (English ) French (Français )

Timezone: Africa/Casablanca (GMT+01:00)

Hello and thank you for contacting Toolset support.

Actually, this issue has appeared after the last patch from WooCommerce 5.5.1. We have published a patch for it. And the fix will be released in the next version of Toolset Blocks.

Please check the patch details on this reply https://toolset.com/forums/topic/php-fatal-error-with-ajax-filtering/#post-2118845
The patched file can be downloaded from here hidden link

I hope this helps. Let me know if you have any questions.

#2119355

My issue is resolved now. Thank you!

#2125551

Jamal
Supporter

Languages: English (English ) French (Français )

Timezone: Africa/Casablanca (GMT+01:00)

Hello there!

I just want to let you know that the issue has been fixed in last week's update. ** Please make a full backup before updating your website. **

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.