Dave McHale

Hi @2f4u

Thanks for using the plugin!

I have to start by asking the obvious… have you tried this without Disable REST API running? What you are describing sounds entirely like issues with their plugin not properly enabling CORS support using that JWT_AUTH_CORS_ENABLE variable. If Disable REST API was blocking you, you’d see the custom messaging indicating that.

I’d recommend starting with a post to their support area https://www.ads-software.com/support/plugin/jwt-authentication-for-wp-rest-api/ But if there’s something I can do on this side based on their recommendations, or if I’m missing something, I’m happy to take another look! Good luck

Hi @nzukay

Thanks for the 5* review! If there’s anything I can assist with please feel free to make a post on the support forum here https://www.ads-software.com/support/plugin/disable-json-api/

Cheers!

Hi @tips4gamers

Yes, this plugin will certainly interfere with those plugins “out of the box”. By default, this plugin will disable ALL access to the WP REST API for unauthenticated users.

By using the settings page you can choose to whitelist the endpoints that you wish. See the “screenshots” on the main plugin page for an example of the interface https://www.ads-software.com/plugins/disable-json-api/#description

I’m going to mark this thread as closed/resolved but let me know if you have any other questions!

@laurendean @njones35 I wouldn’t say “full support” since Formidable still only supports v2 keys and doesn’t formally support v3 even though it came out nearly 3 years ago. It SEEMS to work but that’s more of a “happy accident” thanks to Google, and Formidable still does not OFFICIALLY support it which is a shame.

I’ve been waiting for Formidable to allow you to view an entry’s submission score, and being able to adjust score thresholds on a form by form basis for what should/shouldn’t be allowed through myself – all of which is possible with v3, but v2 only returns a simple success/failure on whether the visitor successfully passed the recpatcha test or not.

Hi @ipajen

Unfortunately yes, it works as “set it and forget it” if you use it the way the name says… you want to Disable the REST API, period. If you want to customize the controls (like ONLY turning off access to the users routes) then the current rules default to “disallow” since you need to manually approve only those routes you wish to allow.

Per the info on the admin page, NOTE: New routes may be added in the future by plugins, themes, or WordPress itself. If you choose to manage access for a user role, you will have to come back and add permissions for any new routes later.

An override to this behavior is on my roadmap but unfortunately just not something I’ve had time to add yet. I’ll see what I can do to get this in the next release though. ?? Cheers!

Hello @carlamannino

I haven’t heard from you in 5+ weeks so I’m going to mark this thread as resolved since I assume you solved the issue on your end. Please let me know if I can help you with anything though! Cheers

Hello @erizo37

Since I haven’t heard from you again in 3 weeks I’m going to mark this topic as resolved, but let me know if you are still having trouble that I can help with. cheers!

Hi again @msp1974

v1.7 is out in the repo, should take care of this issue for you. https://www.ads-software.com/plugins/disable-json-api/ A lot of refactoring went into getting 1.6 implemented and out the door, but it’s still unfortunate that this bug made it out into the wild. Fortunately I believe most users only use one setting or the other and don’t go back and forth too much. Thanks again for the report though, great catch and definitely not intended behavior.

I’m going to mark this as resolved, but let me know if you still have any trouble and I’m happy to look again. Cheers!

Hi @msp1974

Sorry to hear you’re having issues, but thanks for the post and the detailed information! I’ll try and confirm this report tonight or tomorrow to see what I can find on my side & get back to you.

Hello @neoseeyou

Your best bet is probably to check the Disable REST API admin settings page after installing the other plugin(s), and investigate the full list of discovered endpoints. In most cases if a plugin does utilize the REST API, you should see its registered endpoints there and can whitelist them as necessary. Unfortunately, it is possible for some plugins to register their endpoints in ways that they are not visible on that page – with luck a future update will be able to improve the discovery process.

Dave

Hello @erizo37

Based on what you posted above, it seems your only issue is that the REST endpoint required by that other plugin is unavailable. Have you ensured that you whitelisted the required route in the Disable REST API admin settings? What is the actual message returned when something attempts to access the endpoint in question, can you confirm if the DRA plugin is blocking access or is something else?

Dave

Hi @ibrahimsayedahmad

I’m going to mark this ticket as resolved since we did not hear back from you in over 3 weeks.

I’m not aware of any conflicts with any woocommerce extensions, but if you can provide more information we can try to take a look. Cheers

Dave

Hi @carlamannino

Sorry to hear you’re having trouble, but unfortunately it’s very difficult to troubleshoot paid plugins since I don’t have a license key to run & test their plugin.

Can you explain more about the error you’re getting? A 403 is a general permissions forbidden issue, but what does the actual response look like?

I’m not sure if the extension management is on the frontend or admin area… have you ensured that you whitelisted all of the WPML endpoints necessary for the plugin to do what it needs to do for normal operations?

Let me know what information you can provide. Thanks!

Dave

You’re welcome! Looks great, tested on my client site and the extra list is gone. Thanks very much for the quick update, and I’ll mark this thread as resolved. Take care!

Cheers @tai ! ??