Guy Scharf

We just upgraded to WP 5.0 last night and we’ve just encountered the same problem when uploading a .png file. .jpg files upload fine.

The error message refers to …/wp-content/gallery/clip-art/letsSwim1.png. Directory and file permissions are as usual 755 and 644 respectively.

That file and its accompanying .png_backup are both present in the directory and both have 644 permissions. The file does show up in the Gallery/Manage… page for the Clip Art gallery. However, no image is shown.

When we try to place the image in a post, the name of the image is shown as a link rather than the image; the link works and will show the image.

Guy

I am having a similar problem but getting only about 10 spams per day, with the number apparently increasing.

I want to set up a test environment and that is taking a little time to do.

Still not working with recursive lock off. I have a group named Administrator. After running the update, all posts but one have the Administrator flag set (which restricts viewing to admins). When I edit such a post, the Administrator group is dimmed and will not let me change it.

Another oddity I see is that when I show posts/categories, the counts for almost all categories is 1. Yet if I click on the ‘1’, I do see all the posts in that category. A few categories show the proper number of posts but most just say 1.

You ask why update of the database is such a big deal? Because of problems like this that break the whole site. I’ve been burned several times by database updates by various plugins, so am intensely cautious when one is requested.

@cais – Thank you, you are correct. The problem was related to another plugin, Easy Fancybox, that had been deactivated at the same time as upgrading to WordPress 4.4.

I have resolved these issues by writing my own logout shortcode. I am now using clean-login only for its login capabilities.

Not using any other login/member plugin.

I use the [clean-login] shortcode on a page. I am using Suffusion theme.

The problem wasn’t the shortcodes — they were absolutely uniform. When I looked at the web page source, I saw that the src= statements were different for some. After some experimentation, I found the problem seemed related to the lightbox effects option setting at the time the image was uploaded vs when the page containing the shortcode was viewed. For example, if images were uploaded when effect=fancybox but page viewed when effect=none, the fancybox still appeared for the previously uploaded images. But for new images, the images appeared in a separate window (as expected for lightbox effect=none). At one point in my testing, with lightbox effect set to thickbox, clicking on the image resulted in a thickbox appearing on top of a fancybox for the same image.

I have now gotten it settled down where fancybox works everywhere. I’ve reuploaded a few images and am not trying other lightbox effect settings. I did not do any further debugging to try to isolate the behavior.

I see no AJAX option in FSCM. It’s probably easier for me to switch to Contact Form 7, which works fine.

In my testing I can view PDFs less than 2 MB in size but get the “whoops!” message for larger files. Fortunately, I’ve been able to compress my larger files to less than 2 MB and they now view properly.

It’s working again for me today. Looks like Google fixed something overnight!

Looks like Google has now broken the PDF viewer completely. I cannot view documents that worked yesterday.

What other options are available for embedding a PDF viewer in WordPress?

Ouch, that got garbled. I was referring to the page but must have messed up the formatting.

I have a similar desire. My site will have perhaps 30 pages, only one of which contains audio and will be frequently accessed. I’d rather not load the script for most users who won’t be looking at the audio-containing page.

The CFORMS II plugin has this same issue and handles it with an optional Settings field. It allows you to specify which post id’s the plugin is to be loaded for. If you don’t specify any, then it loads the script for all pages. If you specify some ids, then the script is loaded only for those pages.

Good detective work there. The error message goes away when I deactivate W3TC. I’ll have to do some testing to see what the impact of that is (we weren’t using the page caching feature anyway).

However, the lightbox is still not working. Maybe that’s an incompatibility with some other plugin?