neville

Thanks for your helpful reply, appreciate it. Will look into it with my host (DreamHost), report back when I have news.

Just installed your plugin. Nice work! unfortunately, once the widget is added to the sidebar, I get this error text:

Fatal error: Class ‘SoapClient’ not found in /[…]/wp-content/plugins/google-plus-widget/googleCards.php on line 68

How do I fix that? Thanks.

I saw that text as well after upgrading the plugin to version 0.9.9. I already have the WP Mobile Edition installed so I followed option 2:

2. Delete the plugin mod_rewrite rules in /home/…/.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.

As soon as I refreshed the Supercache settings page, I got an immediate 500 server error. If I tried to load the live blog, I got a 500. Trying any page on the domain, a 500 error.

I deleted the htaccess file and restored the backup I’d made with no changes. 500 error gone, everything loads as normal.

Trying to figure out what I did wrong. I just deleted the text as noted in option 2.

Something else I should have (not) done?

Wow, I never expected to be writing this addition to this thread – I just upgraded one of my blogs from 2.5 (yes, I know, should have done that a long time ago) to 2.6.5 (the recent security fix) – and encountered this exact same problem when trying to log in.

@thomascim’s solution re plugin directories solved the problem.

Really can’t believe this is still an issue. Hope it doesn’t happen when 2.7 is out…

My experience in upgrading one of my blogs from 2.6 to 2.6.2 is similar although the circumstances don’t look the same.

It seems that my lock-out (the endless login loop) was due to a security exploit, according to the support folk at my hosting service, DreamHost.

I’ve written a post that explains the issue and the fix I implemented at DreamHost’s suggestion –

https://www.nevillehobson.com/next/2008/09/13/the-endless-wordpress-login-loop/

And here’s another situation and fix –

https://johnhawkinsunrated.com/fixing-the-wordpress-login-issue

Hope these are of some help.

If you’re referring to 2.6.2 (you don’t say which version and you’ve tagged your post as ‘2.6’), I had the same issue.

My situation may not be the problem you face, but I’ve posted about it and the solution that fixed it:

https://www.nevillehobson.com/next/2008/09/13/the-endless-wordpress-login-loop/

And here’s another situation and fix:

https://johnhawkinsunrated.com/fixing-the-wordpress-login-issue

Hope these help.

I’m been running local WP 2.6 on a Vista Home Premium SP1 setup for the past few months using Wampserver. (I ought to upgrade!)

I’m not a developer, just a blogger, so my focus is on trying out plugins and experimenting with design (eg, installing themes).

Works very well.

Jeff Chandler wrote a good tutorial:
https://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/

Oh, and here’s a link to the post I did from WLW to the 2.6 blog and which includes an image:

https://tinyurl.com/6gg4dr

Oops, hadn’t checked this thread for a bit. (And I subscribed to the RSS feed which I do check but missed this.)

I have WLW working just fine with the blog I upgraded to 2.6. @Ottyo42, I did precisely that: left the two settings checked.

@adir1, I’ve had no issues with images in a post written in WLW and then published to the 2.6 blog from WLW. Like you, I have the WLW settings to post images via XML-RPC and not FTP, which is its default. Always has worked and still does with 2.6. My image upload path is wp-content/uploads which it always has been. Unlike you, though, I don’t have uploads organized by date into separate folders.

Can’t say anything re image upload via the Dashboard as I’ve never done that, not even with earlier WP versions.

So FWIW, in my experience using WLW on a WP blog upgraded from 2.5.1 to 2.6 (so upgraded, not a fresh install) works fine, including a post with an image.

@rreynolds, if WLW doesn’t even recognize your blog, could that be re XML-RPC? Take a look at your settings in Settings > Writing – do you have the two check boxes against “Enable the Atom Publishing Protocol” and “Enable the WordPress, Movable Type, MetaWeblog and Blogger XML-RPC publishing protocols” both checked? If you’ve done an upgrade, they both should be checked by default.

If they’re unchecked, check them and then try connecting WLW again. If that doesn’t work, well, it’s probably something else ??

Thanks guys, appreciate your thoughts.

XML-RPC on or off doesn’t seem to be an issue if it’s easy to set it how you want. I wonder, though, how many people who will do new 2.6 installs will really know how significant it is, or not. I can imagine lots of frustrations if they’re using offline editors like WLW that hook into XML-RPC, and now don’t work, and they won’t really know why.

Anyway, re the post-editing features. I plan to go ahead and upgrade one of my blogs to 2.6 and then try it with WLW.

Thanks.

Yes, that makes sense.

Thanks.

Thanks.

Ok, I did that. Now it works! Not in a very elegant way, though, as when I click submit, nothing seems to happen. So I click it again ?? Still nothing. Did the form get submitted? No way to tell.

But it did as I then got the email. Twice ??

I would have thought that a successful click submit action should result in the dialog closing automatically. But it doesn’t.

If it’s simple to fix, I’ll have a go myself. PHP is not my area so any suggestion on what’s needed here?

Thanks again.

I have something that I think is related.

My blog has two sidebars, left and right. If I add a widget to one sidebar and then change my mind (yes, I did that) and wanted to add it to the other sidebar, I couldn’t.

I tried removing it first. It sort of did, ie, the widget appears in the list of unused widgets – but it also still shows in the sidebar where I’d first put it.

And I can’t add it to the other sidebar – the ‘add’ link isn’t there.

So how do I resolve this? What am I doing wrong?

FWIW, the widget editing page in WP 2.5 is the only bit of 2.5 that I really don’t like at all. Clumsy, drop-downs that require another click to make an action, and generally a messy interface.

Just saying ??

I upgraded to 2.3.1 today. One of the first things I did was implement this hack. It works perfectly on 2.3.1.

As noted above, the file to edit is widgets.php in /wp-includes (not the one in /wp-admin).

I followed agentsully’s great guide:
https://lifelearningtoday.com/2007/04/18/make-more-than-9-text-sidebar-widgets-in-wordpress-plugins/

Thanks for that connection, kingcool68. Looking at that thread, it’s talking about being unable to log in to Twitter from TT. I don’t have that problem: TT logs in fine. It just doesn’t update tweets.

Still, I bet there’s something related in all this and what’s happening at Twitter.