Adam Nowak

nevermind, watched the video

Any idea when the plugin will be patched? Google analytics only provides you with the new global site tag. They have moved on from all other analytics tracking at google.

Yes. AIOWPS pretty much is a mechanism to write rules to htaccess. I might be crazy, but it seems like that feature stopped writing the filesmatch rules all of a sudden.

I am doing some experiments. Latest version of the plugin. Now it seems like the Login Lockdown IP Whitelist Settings settings have no effect at all. htaccess is not changed to add the <FilesMatch “^(xxx)”> markup.

So when you check the ‘Check this if you want to enable the whitelisting of selected IP addresses specified in the settings below’, it has no effect on the site or htaccess any more.

Any progress or thoughts on this yet?

Any thoughts on this?

Its been a while. There’s a chance I just changed the email template on the network settings page.

We plan on taking the site live next week, I will probably try to fix this by attempting to fix the marketpress SQL queries.

Through experimentation I figured out what is going on. Once you add variations to a product, MP hides that meta box and forces you to use the image feature within the variation meta box. Thanks.

I tested this in 2017, my theme, with all plugins de-activated and get the same behavior.

On page load, the mp-product-images-metabox div shows on page load, then javascript applies a style=”display:none” after about half a second making it disappear.

If you open screen options, and uncheck, then check the box for ‘product images’ wordpress applies an inline style to hide, then show the div again. But on page load some other javascript in marketpress is hiding this div, as I said, just after pageload.

Any updates on this, we are holding off on taking the new version live because of the sort issues. It is definitely related to products variations vs ones with no variations.

Yes, all the IP addresses of the people using the site are in the list. And end up in the htaccess snippet pasted above. You get a 403 regardless of if your IP is on the list. As I said the server IP and the cloudflare IP were added as well, but 403’s across the board

I am having the same issue. When I remove htaccess rule with the IP’s I can login, otherwise I get a 403 at the rewritten login url. I am using cloudflare, and the generated htaccess rule seems to pick up and add the cloudflare IP. I tried adding the real IP of the webserver to the whitelist, but still get a 403

<FilesMatch “^(xxx)”>
Order Allow,Deny
Allow from xxx.com
Allow from xxx.xxx.xxx.xxx

</FilesMatch>
#AIOWPS_LOGIN_WHITELIST_END

Oh yeah, I am using remote login so the super admins can go site to site and make edits. The wordpress login url functions lead to the domain mapped login url, which is a 404, so I am in big trouble on this one.

I agree with your findings in general, but the issue is compatibility with the change you made in Updraftplus. Not wordpress. I just updated wordpress on a site to check the issue. It did not occur. When I updated to the latest updraftplus, it occurred.

Austin Matzko’s plugin only gets updated annually or so, but I have been using it for a decade, as do many folks I know in the development industry. It has been flawless for a decade.

I removed it and am using a different system, but it might be a good idea to see what change in updraft plus is causing this since the plugin is very widely used. The errors are occurring because of an update in updraft plus, not wordpress.