cynwulfdesign

Well I finally resolved the problem.. the hard way.

I figure it was something to do with either the content folder or the database. I blew away those two things and installed 3.3 clean. No issues on the same host server. Go Figure!

I really hate, as a developer, leaving bugs behind. But I’ve spun my tires long enough on this one.

Hey esmi!
I am still having the image uploader issue. I’ve tested some things out and oddly enough my other wordpress site at version 3.2 is working just fine on another server. So I contacted my host and had the one site that wasn’t working properly moved over to the same server and asked them to verify the security on the folders was exactly the same as the wordpress site that was working. (both are now at version 3.2)

But no change. The freshly moved site that has had all of it’s code reloaded at the 3.2 version still doesn’t upload images properly.

Now what it DOES do is something I wanted to ask you about. Perhaps this will shed some light on the reason why it fails.
– It does upload the original to the proper Upload subfolder.
– What it doesn’t do is create any thumbnails.

Now if the database metadata on the images is stored after the thumbnails get created that might be the reason this never gets done.

I would like to know “in what order does the upload.php process the images?”
And “what could be causing the thumbnail creation code (wherever that is) to fail?”

Thanks!

I tried that and it uploads the image, starts “crunching” the image and that message stays on the upload screen. I click on “save all changes” and check the Media Library. There are no new images present.

I took the time to investigate the database version and I noticed that it was still showing it’s version as “17056” (WP31). So I went and downloaded and manually installed version 3.1.1, 3.2, 3.3 and 3.3.1. Then I proceeded to allow the database to be “upgraded” after each install when I logged in . But for some reason even after going through all that the database version still displays “17056” even though the install process says it upgraded the database each time.

I tried the image loader again after all that was done and it still is failing to upload images. I really can’t imagine what could be the issue here. Next step is the blow away the database and start from scratch but that is not appealing.

What is the correct folder in wp-content? The images are currently being uploaded to the wp-content/uploads/2012/01 folder.

The GD Library information is as follows…
GD Support enabled
GD Version bundled (2.0.34 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.1.3
GIF Read Support enabled
GIF Create Support enabled
JPEG Support enabled
libJPEG Version 6b
PNG Support enabled
libPNG Version 1.2.5
WBMP Support enabled
XBM Support enabled

Nothing has appeared relating to this in the error or access logs. Even the host is stumped.

Esmi,
I cleaned out the root folder for WordPress, the wp-admin and wp-includes folders (including all subfolder content) and then uploaded the files from the wordpress3.3.1 zip file for those folders. And I emptied my browser cache and restarted the browser.

I am still having the same issue…
I try to upload a file and the wp-admin/upload.php just continues to run and run with the “crunching” message sitting up on the screen. I’ve tried different file types, sizes and names. The host says, the files get on the server, but the metadata does not get entered into the database for the Media Library to know its there.

Now the question is “how” do I determine what the upload.php code module is stuck on? Which line of code? Or even see the error it’s running into?

Thanks,
John
[sig moderated as per the Forum Rules]

This is a fix for version 2.5 from 3 years ago.

I’ll try the underlying corrective measures described here. But I think a 3.3.1 version of this support topic is clearly in order. Why would someone follow a remedy for 2.5 when they are running a much later version.

Also, it would be very good to figure out why this occurs through using the established automatic upgrade process. In my case, no errors are being posted so I haven’t a clue what code inside WordPress is causing the problem.

Issue still not resolved.