macbookandrew

Yes, it’s possible for caching plugins to affect it, especially if they’re not respecting the transient timeout for some reason.

It’s also possible that the plugin had the old, longer transient expiration time and was looking at that until you manually flushed the plugin cache.

Could you post a screenshot of your settings with your API key removed/blocked out?

Sorry, there’s currently no way to do this.

@wpcharitable I just sent you an email directly.

Thanks for your help!

Since this is part of Charitable core we wouldn’t also mind reaching out to you to ensure a possible fix in a future version works fine for your client. If you want to?share your contact information securely with us here?(and feel free if you want to include the above info we requested in that sharing), we would def. follow up. And, thank you!

I actually don’t have a login for that…but if you register on the demo site I can give you access to the settings and then email you directly.

1. What version of FacetWP you are using.

Currently 4.0.9, though I did also test with the most recent 4.2.8 as part of troubleshooting.

2. I know you saw you couldn’t provide a test case, but can you describe what settings/setup the site had with FacetWP, where you saw the 404 errors, etc. so we can duplicate the issue on our end to confirm the (eventual) fix?

I set up a demo site showing the behavior: https://charitable-facetwp-demo.luminfire.dev/facetwp/

It’s pretty basic…no special configuration or anything.

1. Installed Charitable and didn’t do anything else with it
2. Installed FacetWP and used the default facet for post categories
3. Added a couple of posts in different categories
4. Created a facet listing for blog posts and added it to the page

If you use the checkboxes and watch network requests, you’ll see the 404 Not Found response and nothing will happen on the page. If you perform a full page refresh, you’ll see the filters from the URL applied.

When both plugins are active, visiting https://charitable-facetwp-demo.luminfire.dev/wp-json/facetwp/v1 will produce rest_no_route error with the message “No route was found matching the URL and request method.”

If you disable Charitable, you’ll see two valid REST API endpoints at the same URL: GET /wp-json/facetwp/v1 and POST /wp-json/facetwp/v1/refresh

I’m still providing basic support as I’m able.

When you say it “doesn’t work on the new WP versions” do you mean something is actually broken, or just that the plugin “tested up to” version had not been updated in a while?

That sounds like the plugin is sending the data to Google Analytics but you may need to configure a view or dashboard there to show the overview.

Can you add a screenshot of the plugin settings, blocking out the API credentials?

@yasin84 do you see any other errors or descriptive text along with that?

@diegocanal 1.8.8 should fix that

@diegocanal v1.8.6 should fix this

So debugging information you’re seeing was actually just error output; there was additional debugging information in HTML script tags only when enabled.

The original intent was to display the errors if the plugin was not set up correctly to help people realize it, but I’ve had other people ask about it as well, so just moved it behind the debugging flag.

The size options is almost certainly because you’re using it in a page builder.

I’ll see what I can do about the debugging log.

@tashtush sorry, that sounds like a YouTube limitation, not anything specifically to do with this plugin.