Gillian

+1 – today’s update killed two of my sites with a 500 error WSOD, but other of my sites are fine (so far, anyway).

Go to the Basic Google Maps Placemarks Settings (under Settings in the Dashboard) and set the Map Center Address to your preferred location.

It is always worthwhile reading through the documentation provided – start here
https://www.ads-software.com/plugins/basic-google-maps-placemarks/faq/

A little bit of patience, especially at this time of year, doesn’t hurt – particularly since this is a free plugin.

The featured image still works fine on all my placemarks, so you may have a plugin or theme conflict. What troubleshooting have you done (apart from assuming the problem is with the BGMP plugin)?

This is the modified filter you need (in a child theme or functionality plugin):

function set_bgmp_map_options( $options ) {
$options[‘viewOnMapScroll’] = true;
return $options;
}
add_filter( ‘bgmp_map-options’, ‘set_bgmp_map_options’ );

Hi Par

Thank you very much ?? The WP User Avatars are now showing for all users on all sites.

On one site, in the history list the avatar circle is cut off at the right (as if the avatar column is too narrow) but this doesn’t happen on the other sites so I don’t know what is going on – maybe I have an unexpected plugin interaction on that one site.

I have noticed another little problem (I don’t know how long it’s been there). When I try to select a user to search for their activities in the history, the user name comes up okay when I type in a few letters but when I click on the user name to select it, it just disappears from view. It is actually there, though, but is squashed up the right-hand-end of the user name bar (near the drop-down arrow) so you can’t see it. Clicking the search button returns the entries from that user so this confirms the filter is being used. Would this issue be related to my screen resolution (1024×768)?

I’m definitely still looking forward to a fix ??

Hi Par

Thanks for looking into this issue.

No, it’s not possible – see the FAQ.

Thanks for that, mulch – it’s one of my favourite plugins too ??

In one spot the server reports php version 5.3.28 and in another it reports 5.2.17 so something weird is going on!

I’ll take it up with my host – thanks for your help ??

The same thing happened on one of my sites – what is the minimum supported php version?

Many thanks for your quick reply, Jacob. All fixed ??

I’ve now updated all my sites to .51.3, so I’m adding to this thread with a bit more info …

After updating the first site (which I had the difficulty with discussed in this thread) I did some experiments. First, I reverted the custom code to the version that was working with .51.1 and logged out. There was a 403 error which locked me out – I removed the .htaccess file and logged back in. Next I tried just changing the “Order” directive from Allow,Deny to Deny,Allow while leaving the SetEnvIf X-FORWARDED-FOR inside the FilesMatch section of code. I logged out again – no 403 error, no lock out, and I was able to log back in. I decided to quit while I was ahead and left the custom code like that.

I then updated all the other sites, one by one, from .51.1 to .51.3, and tested each site in turn. What I found was that without changing the existing custom code in any of them I had no problem logging in and out – no 403 errors appeared. The only difference between the custom code in all these sites and the first site is the order directive: these sites have Allow,Deny whereas, as noted above, the first site now has Deny,Allow.

So, from my experiments it appears:

1) there is some interaction going on in the first site, be it a plugin or custom code or something else – the problem is fixed by making one change: using Deny,Allow instead of Allow,Deny

2) having the SetEnvIf X-FORWARDED-FOR inside the FilesMatch section of code works fine

I thought it was worth documenting this because other people using CloudFlare (or another CDN) in conjunction with BPS will need to use SetEnvIf X-FORWARDED-FOR in their custom code – for my sites it doesn’t matter whether this is inside or outside the FilesMatch section of code.

Nice try, but not correct ?? In addition, the custom code as I originally posted it in this thread exists exactly as written in the root .htaccess file on 3 other of my websites which I did not update BPS on once I discovered the issue with 51.2 – those sites are still all using 51.1 at the moment, and I have no problem logging in and out of them.

I suspect there’s some code interaction going on which only became apparent with the changes introduced in 51.2. In any event, I’ve got the code working on 51.2 now thanks to your help ??

My point was that with the SetEnvIf X-FORWARDED-FOR inside the FilesMatch section of code, the code worked perfectly for 12 months – it worked, in fact, until I installed BPS .51.2 ??

Thanks, those changes did the trick.

Any idea why the original code I used, which was described by you in this post, stopped working when BPS .51.2 was installed? For example, in your original post, you said the correct order was allow,deny and also that “You can use SetEnvIf X-FORWARDED-FOR inside or outside of the FilesMatch section of code”.