Skip Navigation

[Resolved] AJAX filter not working properly

This support ticket is created 7 years, 1 month 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.

Our next available supporter will start replying to tickets in about 5.11 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 80 replies, has 3 voices.

Last updated by nadavR 6 years, 8 months ago.

Assisted by: Beda.

Author
Posts
#575192

Hello,

Please see hidden link

The dropdown filter stopped working as expected after last toolset plugin update. Up until then everything worked fine - and have been working fine for about two years.

Changing "Instrument" or "Genre" changes the output but does not filter according to the selected choices. For example, Try changing "Genre" to Jazz and you'll notice that most artists are Classical and not jazz.
It seems that changing the Country and Type does work properly, but Instrument and Genre don't work.

A similar problem happens in the other Artform pages:
hidden link
hidden link
hidden link
hidden link

(all of these pages work off the Artists Display view, ID# 19847)

For contrast, please see the events page hidden link - which is working 100% fine.

I have provided wp-admin access. If you need FTP access let me know, as I will have to create an invite on Flywheel for that.

Thanks,
Nadav

#575209

Okay that's unusual. Can you try the following troubleshooting steps to help narrow down the issue?
- Temporarily deactivate all plugins except Types and Views, and activate a default theme like Twenty Seventeen. If you need to activate a plugin like Maintenance Mode to hide the site while you're doing these tests, that's fine.
- If the search results are correct now, activate your theme and plugins one by one until the conflict is revealed.
- If the search results are not correct, activate debug mode by going to Toolset > Settings > Front-end content and choosing "Enable Views debug mode". Then reload the artists/music page. You may be prompted to temporarily deactivate your popup blocker. A popup should appear with some debug information. Please toggle open all the sections of this popup and copy the information. Paste that information into your reply here. Then you can disable debug mode.

#575224

Hi Christian,

Thanks for your quick reply. I created a staging copy so I can make all these changes safely. You can access the page here: hidden link
(if you get a privacy warning on chrome, hit Advanced and then Proceed Anyway)

The problem is still there even after changing the theme to Twenty Seventeen and disabling all plugins (except for the Toolset suite).

Instead of copying all the debug information (not sure exactly what part of it you need), I left this mode turned on so you can take a look at the popup. Let me know if it's ok.

Thanks,
Nadav

#575229

I can see from the debug information that the filters for Instrument and Genre are looking for the wrong information, though I'm not quite sure why. In order to escalate this to my 2nd tier support team for additional investigation, I would like to create a clone from the original site that we can install locally for troubleshooting. If you agree, I will install the Duplicator plugin to create that clone and we can begin testing.

I'd also like to know what versions of our plugins you were using before updating, if you have that information.

#575230

Hi Christian,

Will you be able to use duplicator on the staging site? Same user/pass as the live site.

Also, maybe this could be helpful: I just noticed that the URL parameters look a little funny:

music-genres%5B%5D=Jazz

Notice the %5B%5D - not sure what that means. On the other hand, this string also appears on the parameters that do work (such as country), so not sure if that's related or not.

Another thing that may be helpful: the parameters that work are shared among all artforms (the 5 different links I shared in the first message). The ones that seem not to work are the ones that are specific to each of the pages. Again - all of this used to work 100% fine for a long time, and been used by a lot of visitors without any problem so this was programmed correctly.

I am not sure what version I upgraded from, unfortunately. There was indeed a long time without upgrades, but when we got back to working on the site about two months ago, one of the main things we did was to upgrade Toolset, and since then you came out with even newer versions - and we updated immediately as they were released. The issue at hand is very recent though, I suppose.

Thanks,
Nadav

#575235

Yes, I can use Duplicator on the staging site. I would prefer to work on an exact duplicate of the production site, and I've made some changes on staging during testing. So if it's possible to update staging to match the production site again, I'll be glad to run Duplicator there. Please let me know once that's done and I'll begin.

#575236

Done, you may go ahead. When you deactivate the plugins/change theme, I suggest to change the theme first, otherwise you'll run into some blank screens etc.

Keep me posted, thanks!

Nadav

#575238

Well, I'm glad we tried this on staging instead of production. I started a build in Duplicator and it hung the site. 502 Gateway errors are now showing, and I can't access wp-admin. This isn't normal, I've never known this plugin to cause a problem like this. Do you have FTP or Control Panel access? Can we revert the site, or rename the Duplicator plugin folder to see if that fixes the gateway issues?

#575239

Oh, standby I was just able to log in. I'll disable Duplicator and do some more research.

#575240

Maybe the reason you're having trouble is that sites hosted on Flywheel are slightly modified. Maybe, i'm not sure. I know that's the case with some of the root folder files (such as wp-config), so maybe you should simply grab the wp-content folder?

#575242

Hmm okay yes it appears that Duplicator does not support Flywheel sites. I'll have to reach out to my 2nd tier support team to determine the best course here. It appears that Flywheel offers its own standalone app that allows you to create a local development environment:
hidden link
However, I'm not sure if this is something we'll be able to use. Otherwise, I'll need another method to create a clone of your staging site. I'm not sure what the best solution is there, so hopefully I'll get some needed information from 2nd tier. Please stand by and I will update you when I receive more information.

#575243

Ok, I'll standby, thanks.

#575457

Following up about site duplication. I can't leave the staging site turned on for much longer as it's slowing down the speed of the live site. Please let me know once I can turn it off, thanks!

#575459

I'm trying a different cloning plugin now, please hold and I'll update you shortly.

#575463

All-in-One WP Migration seemed to be working well, but it failed because the staging site was out of disk space and it couldn't save all the cloned files. Is it possible to increase the disk space on the staging site? If not, a manual backup will be necessary:
hidden link