pwaara

After several hours of debugging, here is what I found. The problem is a combination of Photo Gallery 1.5.25, Really Simple SSL, and the use of the Photo Gallery widget that is set to display 12 random images out of a dozen galleries with hundreds of photos each. I did not have the time nor the resources to determine where the bug was introduced between 1.5.22 and 1.5.25.

If I let the website load uninterrupted, it would eventually display the page after more than four minutes. (This is on a 2 core 4GB SSD VPS,so reasonably fast.) It appears that forcing the page to use SSL (which the Really Simple SSL plugin does) and how Photo Gallery chooses the random photos is what is bogging down the site.

I cannot recommend my client updates to the latest version or the plugin until this problem is fixed. The issue does not exist in Photo Gallery 1.5.22.

Done.

Downgrading the plugin to 1.11.3 fixed the problem. I’m not sure what’s going on, but it is specific to 1.12.

I can’t see anything that might block the ajax call. I tried it with Twenty-Nineteen theme and all plugins deactivated except for Instagram Feed, and I still see the problem. I revoked access to the app in Instagram and reauthorized it, but still the same problem. I tried clearing my cache and files. Nothing seems to work. I use the plugin on several client sites, and they are all working fine, even those who use the same theme and similar plugins. I’m at a loss. Any other suggestions?

There were no errors in the error_log or in the apache error_log. What I ended up doing was installing the All PHP Options + OpCache profile in Easyapache4, and that fixed the problem. As I suspected, it must be a missing PHP or Apache extension. I couldn’t isolate which one, and I simply don’t have the time to debug which extension it was. The new profile seems to be working well, if not a little overkill since it is loading all PHP options.

No, admin-ajax works fine for uploading images to Media Library. It only fails when uploading using Photo Gallery. I’m fairly certain the problem is a missing PHP extension.

This is happening on all my client sites that use this plugin.
The server is running CentOS 7.6
cPanel 78.0.20

It seems to have started after upgrading the OS and cPanel. Could there be a missing extension?

There are no backslashes in any of the uploaded photo’s alt/titles nor in the photo being uploaded.

Yes, we are getting an error here.

Request URL: <<domain>>/wp-admin/admin-ajax.php?bwg_nonce=9f7c55ca98&action=bwg_UploadHandler&dir=/
Request Method: POST
Status Code: 500 Internal Server Error
Remote Address: <<ip address>>:443
Referrer Policy: strict-origin-when-cross-origin

I’m not sure how to interpret it.

I am having the same issue. WP_DEBUG is true. There are no errors reported either on the dashboard nor in the error_log. There was an error in the console “Failed to load resource: the server responded with a status of 500 (Internal Server Error) wp-admin/admin-ajax.php?bwg_nonce=b820b8beaf&action=bwg_UploadHandler&dir=/

I’m working this with a client. Not sure when the last time they tried to upload an image. They are running the latest version of the plugin 1.5.21.

Thanks for the excellent support. I look forward to the next update.

Hi Craig,

Yes, the CSS also works, so either changing SVG to Font File or using the custom CSS fixes the issue on Internet Explorer 11. Do you recommend one over the other?

~Pat

I use the plugin on four different sites, and they all have the same issue displaying the Follow button in Internet Explorer 11.

Did you mean Icon Method (and not Font Source)? Changing that from SVG to Font File did fix the issue. Thanks for that workaround. There is still an issue displaying the icon as SVG on Internet Explorer 11, but I’m satisfied with the workaround as long is still looks good in all the modern browsers.

I just ran into the same problem. The figure tag has default margins. Those need to be reset to 0 (e.g., figure { margin: 0px; } ) for the image to fill the space of the containing div.

I never solved it either. Like xilinxchic, I just dealt with it since the the changes were saved. Would still like a fix though.