ditchmonkey

Update: this is related to srcset. It seems that srcset overrides any settings you choose for image resolution so I’m not sure what the point of having image resolution settings is. I wish there was some guide that describes how srcset works in detail.

This is not a css issue. This is related to the multiple copies of an image that WordPress creates upon upload. For reference:

https://www.hostinger.com/tutorials/wordpress-images-sizes

For example, if I upload an image 2500 pixels wide, then select “large” as the image resolution in the image block, it should show the version of the image with a file name like Goodsrpings_NV_Anchor_mine_01-1024×680.jpg that has a max width of 1024 pixels.

However, in most cases it is just showing the original high-resolution file on the front end (even when the correct image is displayed in the editor). What I said about this being a problem with the linked image seems not to be true, it happens under a range of circumstances that I can’t find a pattern to. I have also confirmed that it is not a theme issue and I have tested it on three different WP versions and all had the problem.

I realized that this issue only occurs when the image is linked to something.

What I discovered while looking into this is that PMP is incompatible with htaccess methods of moving the WP login. If that is what you are doing, you need to use a different move login plugin.

Update to my previous message – while discussing this with PMP we have determined that this problem is only related to plugins that move the login location via .htaccess. Some plugins move the logins via other methods and do work with PMP. However, it should be noted that moving the login using .htaccess is a superior method as it mitigates potential server load problems that result from brute force attacks on the login form. Solution with PMP still pending.

I have the same issue and have discovered that the move login plugin (changes the location of wp-login.php) is the culprit. I have found through a lot of logging and testing that moving the login is essential for mitigating the effects of brute force attacks on my server so hopefully PMP will fix this incompatibility.

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

1. Your response is at odds with the official security recommendations made by www.ads-software.com

When creating an administrative account, avoid easily guessed terms such as admin or webmaster as usernames because they are typically subject to attacks first

Hardening WordPress

Regarding your #3, as I mentioned people are following the official security instructions, not knowing they are being undermined by this user name issue.

I have looked at those plugins but it is unclear as to wether they are an appropriate solution as most seem to be focused on editing Mapbox maps, adding markers etc, not simply embedding maps that were created in Mapbox studio.

Thanks, I’ll check your other links.