Mar 30
WordPress 2.5 issues
on March 30th, 2008 - FAQs -TutorialsAdd comments
Besides my earlier post where I complained about the Widget/Sidebar interface, I have also found three people now who did not have their upgrades complete for some reason. It appears some files, specifically in the wp-admin folder, are NOT getting copied over on the first attempt.
If you see something flaky in the Admin Section (missing buttons, garbled screens, etc) then download WP 2.5 again (to make sure you had a “good” copy of the files) and then re-copy the files to your blog.
Also, Windows Live Writer, which was working fine before the upgrade, now gives me an error when I post. My post IS published to my blog, but WLW makes it appear as if it hasn’t been. I’ll look into this more later.
*** Random Post ***
March 30th, 2008 at 14:31
FYI - the Windows Live Writer error only shows if there is an image in my post. Still looking into this one.
March 31st, 2008 at 16:09
It’s good to know my issue wasn’t user error for a change!
kaylyn’s last blog post..What are people searching today??
April 1st, 2008 at 09:34
I also get the error when publishing with Live Writer using WP 2.5. The error is:
Error attempting to connect to weblog at:
http://www.rr.cx/xmlrpc.php
The underlying connection was closed: The connection was closed unexpectedly.
It doesn’t matter if there is an image or not. Strange.
Robert’s last blog post..Upgraded to WordPress to 2.5..
April 7th, 2008 at 21:36
I hate to bring this issue up yet again…(problems that is)
I’m getting a 500 internal server error when trying to post an entry from WLW. This seems to be all of a sudden. The specific error message is:
The server reported an error with the following error
http://kaylynsplace.com/xmlrpc.php
Does this mean anything to anyone? Last time I had a problem posting it was a problem with my plugins. I tried deactivating all my plugins and uploading again…still nothing. My post has photos in it if that matters.
This is driving me crazy! Ugh!!! Nothing on this dumb 2.5 is working. I want to go back to the way it was. lol Thank you!
kaylyn’s last blog post..The Power of One
April 7th, 2008 at 21:37
@Kaylyn - I can’t upload images larger than 640×480 now. I used to be able to upload MUCH larger images. Not sure what is going on.
April 7th, 2008 at 21:42
Thanks, Rob. I bet anything that’s exactly what the problem is. I’m used to being able to upload much larger images as well. As uaual, a BIG thank you!!
K.
kaylyn’s last blog post..The Power of One
April 7th, 2008 at 21:45
It worked, of COURSE it worked.
One day, I’ll be able to figure these things out for myself. Until then, sure glad you’re around!
kaylyn’s last blog post..The Power of One
April 7th, 2008 at 21:47
@Kaylyn - I just get lucky now and then
I am an old Quality Assurance guy though - so finding work-arounds to bugs is something I am trained to do.
May 28th, 2008 at 13:49
@kaylyn
There is a work around for this if you have FTP access to your blog, you can specify to upload the images via FTP to a location and then when you go to post you don’t get these errors and you aren’t limited by the size of the image.
in livewriter this setting can be found under:
weblog/ Weblog Settings
on the sidebar, click on images and then click the “upload images to an FTP server” and click on the Configure FTP button.
your ftp settings should be fairly straightforward. That’s how I fixed my problem. It seems in the latest version of WP they sure lowered the threshold for image size.
Anyway, I don’t know if this response is too late for you, but this is what i did to fix it.
Now if i coudl figure out how to keep it from converting my .gif to a .jpg i’ll be in business.
May 28th, 2008 at 16:45
@kgranson-It’s never too late. Thank you for the tip! I’ve actually been using Word 2007 lately to post blog entries and it’s been working really well for me. I’m going to give your suggestion a try next time though.
Wish I could help with the .gif/.jpg issue…It seems WP has a mind of it’s own sometimes, that’s for sure!
Thanks again!
May 29th, 2008 at 06:38
Just caught this: ” I am an old Quality Assurance guy though - so finding work-arounds to bugs is something I am trained to do”
As a QA guy, whether old or not, working around bugs is the very last thing to do!
Your job is to make sure there are no bugs.
If you find one, you kick the whole thing back to a developer.
(Which you did)
May 29th, 2008 at 13:25
While I waited for development to fix the bug, I was forced to develop work-arounds