Dave McHale

Appreciate the fast response! We’re just trying to go from 6.5.3 back to the 6.4 build in order to test whether upgrading recently was the cause of another issue we’re seeing on the site. Here’s a pic from the main page and then what we see when it sends us to the updates page. (client-specific info has been redacted but I wanted to be sure to include the URLs in the screenshots).

Let me know the best place to send you the Test Report – since it is for a client I’d rather not post the report publicly here, but am happy to send it your way. Cheers!

cheers! and thanks for the shout-out in the release notes ?? Marking this thread resolved ??

Thank you @shafayat-alam ! I was able to upgrade that plugin and it solved our issue. Re-marking this thread as resolved ?? Cheers!

Hello @humayonk , I see this thread was marked as resolved but never received a followup. Can you please let me know if there is an upcoming patch that addresses this issue? The version of the plugin currently available still has this issue on our site.

@qwik3r I think at this point taking @bryceadams up on his offer to look would be ideal, since nothing about DRA should be blocking anything if you’ve tried adjusting your settings to “allow full”. Since you’re unable to debug what I sent above, with luck Bryce and team can either find out what else is not working properly or at least help provide more information that I could run with on my end.

Good luck, and keep me in the loop if you find more information!

Glad it’s working @qwik3r !

I can’t speak to the actual Metorik issue since I’m not sure how their endpoints work, but I can say that often it helps to look and see if the error talking to the endpoint has the “DRA” messaging in the response or not. And sometimes even if you’re logged in as a particular user/role, endpoints are sometimes accessed without authentication. I’d recommend looking at that as a starting point.

Since we’ve confirmed the plugin no longer causes fatal errors on your site I’m going to close this ticket now, but feel free to let me know if you have any continued issues in a new ticket! Cheers

hi @qwik3r

I believe I’ve tracked down the issue! ?? Unfortunately I’m troubleshooting a UX update for the next version of this plugin that is holding up my next release, but this change WILL be included in the next version.

If you would like to make an update now for yourself you can edit Line 32 of \disable-json-api\classes\disable-rest-api.php and change the init action to wp_loaded – in my local environment that seems to work without any negative side effects that I have noticed. But please let me know if you see any issues, if you decide to try this update!

Thanks again for the report, and hope this helps you use the plugin without issue!

hi @qwik3r Sorry you’re having issues, but thanks for the report! I may have an idea on how to fix, and sent you a message on Slack to follow up. Hope to talk to you soon and see if we can get this fixed for you!

hi @hendrik57 never fear, a new release is coming soon! And will come with updated compatibility information. Thanks for reaching out, and for using the plugin!

Hi again @sadesades

Just wanted to let you know I’ve added a new dra_error_message filter to the upcoming v1.8 plugin version, which I *hope* to have out in the repository later this week.

Cheers!

Hi @t0t0r0555 hello and thanks for using the plugin! I have typically only been releasing a new version of the plugin every ~2 versions of Core, due to work and personal life commitments. Also, Core typically is not changing much (if anything) related to how this plugin functions – so just because a new release is not out asserting compatibility with a more recent release does not mean it does NOT work with a newer release. As far as I know, the latest version of the plugin works well on 5.9 as well as 6.0.

That said, I am looking to release a new update to the plugin in the next week or two so you can expect a new version soon tagged up to 6.0. Cheers!

Thanks for the suggestion @dade88 and I hope you’re enjoying the plugin. I will look into what would be necessary to document some common endpoints for people, but honestly the concern would be what happens when other plugin authors change their plugins moving forward in the future. If admins wish to whitelist endpoints on their site, the hope is that they understand the functionality of plugins installed on their site enough to the point that they are able to whitelist desired routes appropriately.

I’m going to close this thread as “resolved” but again, look to future releases for some more info in the FAQ’s. Cheers!

Hi @sadesades

Good suggestion! I’ll see what I can do to add a filter in the next release ??

Hi @sadesades yes please make a new topic for that request, and I’ll close this one for now (and I’m happy to hear you’re no longer having any issues!). When you make your new thread, please provide me with more info about which part of that response you’re looking to filter… just the message portion, or something else? Cheers!

since I haven’t heard back I’m going to mark this ticket as resolved, but if you have any other questions/suggestions please feel free to make a new one. thanks!