404 errors after plugin update to iThemes Security (4.0.5)

Looks like this is still an issue.

We are currently developing a new theme using the roots framework and activating this plugin results in multiple 404 errors and us being locked out of our own site NOT to mention that its hogged ALL the resources on our new dedicated server. Very disappointing at this and unfortunately going to turn off this plugin however GOOD it was previously until its fixed properly.

For information here is a ample of URLs that come back as 404:

https://www.sitename.no/wp/home/USER/public_html/app/plugins/better-wp-security/modules/free/file-change/js/admin-file-change-warning.js?ver=4028

https://www.sitename.no/wp/home/USER/public_html/app/plugins/better-wp-security/modules/free/strong-passwords/js/strong-passwords.js?ver=4028

As you can see its calling wrong somewhere.. The old plugin worked flawlesly..This one doesnt ?? hope the devs can fix quickly…

Hey All,

Could you update to the most current version of 4.1.5 and let me know if that helps? If it doesn’t help could you please file a bug report?

iThemes Bug Report

Thanks,

Gerroald

Hello Gerroald,

I should have indicated that we are using the latest version4.1.5.

Previously we had the old plugin running with no issues. Saw the update and naturally updated the plugin. That’s when the issues started, so we have deactivated.

New ithemes version seems to want to use ALL the servers resources..even a Magento site we have on an identical server doesnt use as much as this plugin does…

Want do I need to include in the bug report?

just completed a report on your site WITh screenshots. Here is what I sent:

As per the post here: https://www.ads-software.com/support/topic/404-errors-after-plugin-update-to-ithemes-security-405?replies=2#post-5526613

We are seeing multiple 404 errors that then in turn locks out of our wordpress system.

Its call to your own files that’s causing the issue.

Used the old version previously and it worked flawless.

Also the amount of resources this takes up is pretty high, maybe that’s due to its incorrect (corrupted) way its picking up the 404;s at the moment. The old plugin was super fast. This is really slow and hogs server resources.

Screenshots attached of the 404’s…

Also, the hide login function. Again it was great in the old version this one not so much. Although it does what it states it still add /wp/ before the URL chosen.

We use Roots theme as a framework and out of the box there rewrites place all wp file in the WP folder..

So to totally hide the login url it would be ideal if it was coming from root e.g: https://somename.com/chosen url NOT https://somename.com/wp/chosen url/

Loved the old plugin.

Shame about this one ?? not having a good experience with it..

Yep, I can confirm that this happens when you move WordPress core into its own directory and split out the wp-content folder.

I pushed a fix to this earlier today. It was how folks were installing that wasn’t accounted for in my tests. My apologies for the inconvenience.

Chris,

The update does fix it for me, but I think the icon-fonts.css file still needs to be fixed up as well. ??

I was able to use the $itsec_globals['plugin_url'] value as was done with the other enqueues.