Ryan Duff

moshu: if he has a backup of his 1.5 db, he should be able to upload the 2.0 files and just run upgrade.php again.

Did you run upgrade.php? Sounds like it didn’t run correctly and the new capabilities didn’t migrate over from the prior user level system.

I get very good SEO from WordPress by default. I have a few posts that have quickly jumped up to the first page in Google and have gotten some positive and negative feedback because of it.

One outstanding is a review of a hosting company I did, comes up on the first page amongst the rest of their links and it tends to deter people from them. They (the hosting company) are always nagging me about it.

Don’t worry. Microsoft reportedly just bought Opera so it will probably never work. ??

I’ve changed contactsubmit from an id to a class in the 1.x branch and it will be a part of the next version.

I’ve also made an empty
.contactsubmit{
}

in the css so anybody can edit and add their styling.

Specifically… https://dev.plogger.org/wiki/WordPressPlugin

Did you try a search in the Plogger forums? I know anti was working on a plugin of sorts to make this work.

I also have a plogger integrator that sticks the required code in the correct places. Last time I checked though, plogger still threw errors when being called from a separate directory.

1.4.2 has been tested OK and I back ported all those changes to 1.3.1 for all users of WordPress 1.5.x

A few bugs have been rolled out and its now at 1.4.2 Please test and confirm it works. Use the link above to track changes.

Yes, anybody still running 1.5.x or earlier should continue to use WP Contact Form 1.3 This is for anybody testing WordPress 2.0 to try out and confirm that it works so when people upgrade, they have a plugin available that will continue to work.

Yes, and what about all those IE only websites? I’m a big fan of getting rid of IE. Hopefully this will add to more incompatible people and developers will stop making IE only sites. Amen!

Matt pretty much nailed what I was going to say. Does your host really know what is going on? Are they concerned at the ammount of dead process it generates or is there something else they claim to be loading down their servers. I suggest they figure out what they’re talking about or send you the correct error logs. If this is the best they can do, maybe its time for a more knowledgable host.

Plogger… https://plogger.org

If you’re on a shared/managed host, its something they need to install/enable on the server side. Put in a ticket with them if thats the case.

A non-current list of the feature set slated for 1.6/2.0