Odd error, I’ve been running 3.1 since it came out and don’t have that issue.
It might be your server, who’s hosting it?
It’s webhostinghub.
Hasn’t changed.
I was using them before, I did a domain change.
That caused me to lose my blog due to other problems.
I deleted everything and the database, did a complete fresh reinstall and started manually retyping my blog entries (I keep records for stupid reasons)
When I got to some blogs that had photos I noticed the problem.
I’m reinstalling “again” and I’m going to test it without loading my theme and wootumblog to see if maybe that’s the problem.
Figure if it still happens on the default theme and package install then it’s something else.
I just don’t know where to look. 🙁
Stupid question I know, but what Browser are you using?
If its not a weird browser issue I can’t imagine what would be stopping it. I’d try the twenty ten theme without any plugins active and see what happens.
I’m using Firefox 4 mostly, but I’ve tried with IE, Chrome, and even on Safari with my laptop.
It appears the bugs still persist without any plugins or themes.
You can see for yourself;
http://www.calai.me
That post has a picture of what Texans call “a lot” of snow. No matter what I do it doesn’t show.
I see the file on the server (through FTP), but you try to go to it and it doesn’t exist.
Full path is http://www.calai.me/wp-images/2011/03/snow.jpg
Wait, there shouldn’t be a wp-images? Where did you get WP-images?
I created it under media option.
I’ve used that folder name for the past year without problems.
AND
I FOUND IT!
Stupid me .. I forgot to set the wp-images folder to 755 permission
I figured out why I can’t bulk delete either– wootumblog
Once I disabled it I was able to do bulk things. It doesn’t kill me, I just have to manually delete things one-at-time.
Great that you figured it out – for me its always better to know what’s going on rather than be in the dark.
Also, if this topic is resolved be sure to mark it as such. Thanks!
Yep, it’s marked resolved.
I saw on the authors page that people were reporting the same issues, so I added on that I am experiencing it too. Hopefully an update will come soon to address that issue.
