yodathedark

That would probably work, and I can confirm that there wasn’t an issue with 2016, but given that there was an issue with 2013 which is the theme our child theme is based on, I’d prefer a solution that doesn’t require the user to known how to edit their functions.php file – security shouldn’t just be something available to the technically literate.

The problem, as I have stated, is that MWI can’t access the Magento files it needs to load the layout correctly. I suspect this actually happens with any plugin that hooks into the layout this way but most don’t return fatal errors as a consequence.

To counteract the issue, I think AIOWPS needs to actually replicate a page load instead of just grabbing the 404 template and calling it a day.

I know that. I’ve been using this plugin for a while. The problem is that instead of getting a 404 page when browsing to wp-admin, you get a fatal error because it’s not bringing in the WordPress elements that other plugins need.

The fact that unusual behaviour is happening on the typical WordPress login pages is likely to indicate that it is in fact a WordPress site.

Personally I find that such unusual behaviour goes against the purpose of the plugin when surely part of the reason to change the login URL is to disguise that it’s a WordPress site to begin with.

@gramirez68, I had the advantage of having the website stored in a git repo so I just rolled-back the change.

Same thing I found.