SwiftNinjaPro

Just added an option to disable the plugin on 404 pages

If you update to version 3.1 or later, there should be an option to “disable on mobile”, which should prevent the 404 redirect on mobile devices.

Thank you for the feedback. I just released version 3.0 to fix most of the issues.

It is possible for this plugin to have a negitive impact on SEO. There is an option in the plugin settings to disable the dev tools block if it detects a common search engine. The check box “Allow Search Engines”, is made to help with SEO issues. Keep in mind, this is Not a perfect solution, just an attempt to fix the issue.

I assume you mean SEO, not CEO. SEO means Search Engine Optimization. CEO means Chief Executive Officer.

Were you logged in as an admin, or a user with manage options privileges? This plugin does not block admins from dev tools on purpose.

Also, in this plugins settings, you need to check a box to enable the plugin.

If you enabled the plugin, checked that box, and logged out to test it, please let me know so I can try to fix it.

Thank you.

I notice this url redirects me to /404-2
The plugin does use the builtin is_404() wordpress function to detect a 404 page. is /404-2 a wordpress builtin page?

If your 404 page is not built into wordpress, then the plugin does not see it as a 404 page unless wordpress does.

I also get redirected a second time to google.com

is this intended? if not, I would recommend running a wordfence scan.

• This reply was modified 4 years ago by SwiftNinjaPro.

The plugin should remove the scripts it runs on completely, if your logged in as an admin (or with manage options permission).

could be a cache issue. does the admin receive cached pages?

In a recent update “2.0.1” I added an option to disable the plugin script on admin and login pages.
This includes the lost password page as a login page.

In a recent update “2.0.1” I added an option to disable the plugin script on admin and login pages.
This includes the lost password page as a login page.
Hope this helps.

Just fixed it in version 2.0

Can you log into your site through FTP (cpanel or filezilla) (if cpanel, go to file manager) then go to /wp-content/plugins and rename the folder “swiftninjapro-inspect-element-console-blocker” to disable the plugin?

marking this as resolved

have you tried unchecking the setting: “Secure 404 Page by stopping it early”?

Found out what may have went wrong.

I accidentally put the recovery page under the same if statement, that checks if the plugin should be admin only access. If that was not checked, the page would not be added.

Before finding this issue, I rebuilt the recovery page, and it now runs on the front end (using admin email vitrifaction, and a password protected page).

If you update the plugin to 1.10, under FAQ you will see updated instructions.

To reactivate the plugin: (requires version 1.10 or later)
1. on your site, go to: /admin-login-whitelist-recovery
2. enter the page password “gHxXeVwvuz6Cez3” (You will still need to verify disabling the plugin through an admin email)
3. follow the directions on that page

After that, the plugins “Enabled” setting will be disabled, and the plugin will not run, and settings will still be accessible.

Note: The email must be an admin users email. The email will also be rejected if the account is less than a week old.

Also, if the page does not exist, deactivate, and reactivate the plugin.

if that fails, add the below shortcode to any password protected page, then go to it.
[wp-login-recovery-page]

Hope this helps.

• This reply was modified 4 years, 5 months ago by SwiftNinjaPro.

It seems an update to firefox has caused the method this plugin uses to detect if the console is open on their browser, to no longer work properly. The detection was based on the slight increase in lag when opening console, and it seems firefox removed that small bit of lag from their console.

• This reply was modified 4 years, 6 months ago by SwiftNinjaPro.
• This reply was modified 4 years, 6 months ago by SwiftNinjaPro.
• This reply was modified 4 years, 6 months ago by SwiftNinjaPro.
• This reply was modified 4 years, 6 months ago by SwiftNinjaPro.