Can’t Upload Pics–Do the Devs Know?

Why? Because 2.3.3 worked just fine. If it stops working in 2.5 the problem does not lie with any servers, but only with WP2.5. Why? Because 2.3.3 worked just fine.

The problem with that idea is that 2.5 doesn’t “stop working”. The uploader *WORKS*. At least, it does on my test site, it does on my servers, it works when I set it up using XAMPP… What more do you want?

A “bug” is a bug everywhere. There has to be some reason it works for me and not for you. We need to find that reason, and claiming that 2.5 has a problem is not helpful towards that goal.

The goal is to find the problem, not place the blame. Placing the blame is useless and annoying. Calling it a “bug” before you’ve actually found it is the same thing. It shuts minds, closes doors, and makes it more difficult for us to help people.

So stop it.

But 2.5 just stopped working on my server, where 2.3.3 worked. And NOTHING else has changed, because it is MY server and MY navigator, and I’m 100% sure nothing has changed. So it is a regression.

A bug doesn’t need to be exist everywhere. A thing that doesn’t work in some systems where it worked before, is a bug.

If a new release of a program fails to work in a setting where the previous release worked, it is a bug, a regression bug. And if the system (navigator and server in WordPress case) hasn’t changed, you cannot say it’s a system problem.

WordPress 2.5 has several regression bugs in Image Gallery management. Saying that it has a bug is not bashing the software, it is accepting the truth.

Now, I understand perfectly that you haven’t got this problem in your system. And that you cannot correct it is you haven’t it. I don’t ask you to magically discern the answer to my problem. But please, don’t tell me that “it is not a bug”. Jedi mindtricks don’t work for me.

I’ve been using open source software for years. I’ve posted a lot of bug reports in many pieces of open source software, from Firefox to Inkscape, from Thunderbird to Open Office. And in my day job, I’m software engineer. I’m more a Java developper than a PHP one, but I think I can try to get the debugging info you need. If you tell me what you need.

And please, Otto, don’t take it bad. I know you and all WordPress dev team have been working a lot for this release, and I guess that everybody here (me for sure) find WordPress 2.5 really SUPERB. I do.

It has oly a little bug, that will be corrected soon. I’s normal we focalise in the thing that doesn’t work, but it doesn’t mean we cannot see all the great thing that work. You have done a WONDERFUL work with 2.5.

Well, I just upgraded my Flash version from 9 r45 to 9 r115 and the uploader works…

Not sure if that was the overall issue or not, or if restarting the browser had something to do with it, but I’ll test it on my home computer as well later.

OK, I understand that. But for us non-programmers and non-PHP experts, how exactly do we go about debugging a piece of software?

Probably, you don’t. You can weigh in and say you have the problem, and then either try to fix it or wait for a fix or revert back to a previous version or whatever. But simply posting that you have a problem over and over doesn’t help to get it solved. Quite the opposite, in fact.

If a new release of a program fails to work in a setting where the previous release worked, it is a bug, a regression bug.

WordPress 2.5 is not simply a “new release”. As far as the uploader goes, it is an entirely new piece of software. There’s no “regression bug” because there’s nothing to “regress” to. It is really, really, not an upgrade; it is wholly new software. WordPress 2.3.3 had no Flash in it, for example.

I think I can try to get the debugging info you need. If you tell me what you need.

What I need you to do is to go over to https://trac.www.ads-software.com and post the bug there, and follow up on it there. The main WordPress developers read that site. They generally do not read these forums. Mainly because of threads like these and problem reports like the ones I’ve been sorting through all day.

Well, it does not work completely on my live site and it does not on my local XAMPP. If it works for you: be happy.

XAMPP is no real criterium anyway as the configuration is quite different to those used by hosters, so you cannot really use that as a proof of “no bugs”.

The definition if something is a bug or not is a superfluous philosophical discussion. Again: In 2.3.3 it worked, in 2.5 it does not. If it is a coding bug or bad programming (technical not a bug) is not the point. Something that worked ceased to do so.

Most of the people would be happy to go back to 2.3.3, but with the statement that there will be no security updates anymore for that, this is not an option. So, if you like it or not, you have to rely all these problems to the developers, if they are bugs in your opinion or not.

I would really like to see what would happen, if each and everyone posts into trac, as you suggested above. That would render it inoperable. This forum is to filter bugs, design flaws and other problems and you should help with that and not bully people looking for help, because a perfectly working software turned into a heap of [censored].

Otto, I didn’t knew about the trac, going there now. I guessed that support forum was the right place to post bugs.

And I guess that having several dozens of similar threads about this bug can be rather irritating, but I guess it is very understandable. People just upgrade, they find a thing that doesn’t work, and wht do they do ? They post in the Troubleshooting forum. The forum name seems to indicate that it’s the right place to post about a problem, doesn’t it ?

Oh, and I just edited my last post, so I prefer saying it again here :

And please, Otto, don’t take it bad. I know you and all WordPress dev team have been working a lot for this release, and I guess that everybody here (me for sure) find WordPress 2.5 really SUPERB. I do.

It has oly a little bug, that will be corrected soon. I’s normal we focalise in the thing that doesn’t work, but it doesn’t mean we cannot see all the great thing that work. You have done a WONDERFUL work with 2.5.

The forum name seems to indicate that it’s the right place to post about a problem, doesn’t it ?

Oh, it is. However, it would be nice if people a) searched first and b) posted enough information for those of us in the know to actually be helpful. As it is, these sorts of threads are essentially useless. Not enough info to help anybody, not enough info to reproduce the issue, not enough info to debug with… It’s downright frustrating.

The definition if something is a bug or not is a superfluous philosophical discussion.

No, it really is not. I’m sorry that you think it is, but I assure you that it’s not. When people post here looking for help, and they read that “it’s a bug”, then they don’t attempt to solve it, they expect to be given a fix. A “bug” implies a “bugfix”, does it not? Trying to talk them into debugging is such a pain in the arse at that point.

Words matter. Especially here, where we have nothing but words.

Oh, it seems the bug has already been posted to trac :
https://trac.www.ads-software.com/ticket/6406

And they have accuratly guessed forum reaction :
Leave the option checked by default if you’re worried about catching errors with the core, but be sensible — the forums will be FLOODED with folks “screaming” about an inability to upload and if the “official” reaction is “Download this plugin, install it, activate it, then try uploading”, I think it’s going to be a rough ride. “Go to Settings->blah and unclick that ‘Use Flash Uploader’ setting” shows care, forethought and attention for users’ various settings and whims.

Huh. Didn’t know it had a disabler plugin. That will be handy as a temporary workaround.

Disable the flash uploader:
https://trac.www.ads-software.com/attachment/ticket/6406/no-flash-uploader.php?format=raw

Okay, I made a sticky post. I’ll update it as we find out new things. That make everybody feel better?

Rhanks a lot, Otto !

I guess that will help lots of people.

Okay, is there any fix for this yet? I see a lot of people are having issues with the image uploader in 2.5 when writing a post as it is totally gone! Where did it go?

I did write a post about it

https://www.ijohnw.com/2008/03/31/upgraded-to-wordpress-25/

See what we have to deal with?

See the sticky post:
https://www.ads-software.com/support/topic/164999

I am having pretty much the same problem i can click the media buttons, and the Ajax barber poll progress bar pops up and then i am kicked back out to the front page of my site.

I upgraded from 2.3.3, and i think that i copied all the files over correctly. i looked at the .htaccess file and it looks fairly standard

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

i am in a dreamhost shared hosting environment. I have also run through all of the check list in the stickyed post to no avail.

Are there any specific files i need to look at and make sure got copied over? What other data do we need to provide. i am willing to work through this as much as i can.

In case it helps anyone using Slackware 12. Here’s how I worked round the issue to upload images in FireFox 2.0.0.13

Upgrade Flash to the latest Linux version from Adobe – 9.0.115.0.
Extract the installer but don’t run it, it will only complain about the glibc version being too low. Edit the install bin to remove all references to glibc version checking and then run. Restart Firefox and you can now upload images.

So from my point of view, the issue is with WP using and expecting a particular version of Flash.

i did a fresh install as a test on dreamhost, which is the same host that i am using on my effected site. and it worked fine. so i think at least in my case i can rule out differences in host environments. i am going to copy my plugins folder over to my test site and try different combos of plugins on and off to see if that makes a difference. i am starting to think something went afoul during the upgrade process. i deleted the folders it recommended to delete first in the upgrade process and replaced them with the new folders. i will keep testing and post my results.