IainPurdie

Thanks, Esmi. I’ve also posted on the Atahualpa forum and the first response I received (from one of the mods) was “image handling is core code and nothing to do with themes”.

I’m tempted to agree with him in that it makes more sense, but in that case why would changing themes make a difference? It’s a strange one!

Yes, I am now. Just updated to 3.7.7 and retried. Same issue.

Looking like you’re right. I changed to Twenty Eleven and the problem went away, re-enabled Atahualpa and it’s back again.

Gah. Time to start trawling for any solutions!

Thanks for prodding me in a direction I should have been looking anyway!

At the risk of sounding all AOL – “me too”. It’s been happening for some weeks now, though my problem sounds more like beanneu’s.

Files I’ve used plenty of times in the past are all of a sudden multiplying. When I use an archived image, the system seems to create a new copy (sometimes several) and use one of the instead of the original.

Getting rather annoying, and filling my media library up with a significant number of duplicates.

I’d just like to say “thanks” to cmadriles. I just went to add a new blog post to a blog that’s been sat there on 3.2.1 since the day the version was released… and got the error message about PHP being wrong.

What’s nuts is that I have three 3.2.1 WordPress installations using the same webspace. Their .htaccess files are (allowing for site-specific details) identical, their layouts are the same, etc. And yet for some reason only this one blog was affected – and some time after I had updated to 3.2.1.

Whatever the reason, at least it’s now fixed. Thank you!

vtroia’s solution worked a treat for me upgrading to 2.8.

HOWEVER – afterwards, it’s worth commenting out (add a “#” before) the lines. I’ve noticed some flaws in 2.8 if you don’t.

Details on blog post:

https://www.moshblog.me.uk/2009/06/11/wordpress-automatic-upgrade-problem/

Jimtron – just a quick “thank you” as I’d just spotted the same problem and that fixed it perfectly!

Mitch,

I auto-upgraded to 2.0.4 and everything now seems to work perfectly. Thanks so much for all the work and effort! Sorry I didn’t reply sooner, but I’m backpacking through Cambodia and internet access hasn’t been as frequent as I’d hoped ??

Iain (https://www.moshtour.me.uk)

It *was* a plug-in. Must have skipped it when I was testing them. SPS-Suite to be precise, which on checking does mentions that it improves searches.

Well, in my case it didn’t…

Same query – anyone got any hints? Or perhaps something worth adding to the “wishlist” as an option in the Admin area?

Just done my first major post after upgrading to 2.5.1 – and the left/right align in the image editor seems to do just what I want. I can now ditch the old imgl/imgr. Could mean a large editing session at some point to “correct” the old ones, bug looks like future posts will be a lot easier – and it gets rid of this problem (at least in this instance).

Yay! ??

Hey people.

Yeah, the tags thing was kind of the only way I could get the pictures to do what I wanted. They are part of the style sheet, and are an adaptation of the “IMG” tag within a certain style. Pardon my lack of the correct terms! I’m more the kind of person who delves into code and messes with it than reads books on how to do it properly ??

Ideally, I’d just use parameters in the standard img tags, but I found this to be the easiest way. You’re right, though – perhaps if I used a class within the img then the editor wouldn’t strip stuff out.

Thing is, I can’t avoid popping between the two tags as my spellchecker (Firefox) will only function in the WYSIWYG tab, while I need to manually alter HTML from time to time. I did have a glance around after I posted this and eventually did find a few people with similar problems with the visual editor “tidying” code when it wasn’t required.

I used to have nightmares with v2.3 and it’s wholesale destruction of “table” elements.

But, yeah. I should look more into using a “class” rather than a wholesale new “img” wrapper.

I must confess, I am now at somewhat of a loss. All I can suggest is to go back to basics. Have the blog set up wide open and gradually secure it bit by bit until you hit the problem (or – hopefully – bypass it).

Hmm… I’m not familiar with the plug-in (heard of it, but not used it) so I’m not sure of the effect it would have. As an experiment, try disabling the plug-in. From what I gather it only protects the *site* from prying eyes, not the ability to comment.

I’d suggest small steps – see if you/we can get it going without the plug-in first and *then* activate Private-WP.

I’ve had a dig around the web and I get mixed messages about restarts. The best reference seems to be here:

https://forums.devshed.com/iis-97/restart-iis-after-editing-php-ini-218884.html

Which straightforwardly says “yes – you do have to restart IIS after changing the php.ini file”.

Having said that, I found a few other sites that said the exact opposite! In personal experience using LAMPP (on Ubuntu) and XAMPP (under Windows), a restart is required to make the changes take effect.