truncatus

I have it working correctly on a wordpress I have installed on a subdomain but it gets the same parse error when I ‘blog this’ on my installation of wordpress residing at https://www.domain.com (sure, ok, www is a subdomain too).

I’ve noticed it gives the same error if I give it an incorrect password.

Hmmm. Tried giving it an incorrect URL (added wp to the end of the URL and that doesn’t exist) and it says it blogged it correctly. (it didn’t though).

Odd. I went back to check my profile and it appears to have stripped the wp off the end of the URL. I retyped the user/pass and am getting the parse error again.

Changed profile to use movable type instead. Failed. (kinda expected that though)

Changed it back to what look to be correct settings….same error.

Tried in both Firefox and Opera…doesn’t appear to be a browser issue. Haven’t tried it in IE but I also haven’t tried jumping in front of a speeding train.

I’ve got two logins to digg. I changed my profile to use the URL based on another subdomain. I ‘blog this’d and it has published the article correctly. I assume it isn’t a difference between my two digg logins.

Dang. Changed the settings back and I’m back to the parse error.

D’oh. Dropped the www off the URL and still getting the error.

Can anyone think of possible differences between two wordpress installs that may do this? Both are WordPress 1.5.2 running in a shared environment, virtually hosted, safe mode on (no issues with that as long as the permissions are correct).