kjarrett

I’ve got this same problem since the upgrade to WP 2.8.

x2…help appreciated!

-kj-

Holy mother of GOD!!!!!!!!!

Otto, thank you so much. FIXED. How do I mark this RESOLVED?

All of you – thanks.

I am going to smash my head into the nearest large, immovable object. ??

-kj-

Thanks Justin. I will check tonight. Are you saying you think the malformed URL is hardcoded there? Or I should be using a different function call?

MichaelH,

Nope. Vanilla wp-config. Thanks for trying.

Justin,

I’ll add you as a subscriber in a sec. Thanks!

-kj-

Ok guys I’m sorry but I’m confused.

First, I don’t see what’s incorrect about the URL in Justin’s earlier query. Looks totally right to me.

Second, I don’t see

‘https://server302.tchmachines.com/~xicjilzj/blog/’

anywhere in the DB, and the ‘home’ variable’s ‘option value’ is https://www.sshrmanj.org/.

Finally, I am looking at options-general.php in Dreamweaver and though I see where the code appears to be calling the variable as directed, I certainly don’t see anything hardcoded, and so I am reluctant to edit it…

Thanks for continuing to help,

-kj-

THANKS GUYS…

Dossy, I get: https://www.sshrmanj.org/blog/ which is the correct folder where the blog is installed.

Justin, the results DO NOT match, ‘home’ is the site root.

Exactly where do I make the change?

-kj-

Sure do…do I need to change this in a DB table somewhere?

I’ve built and run dozens of WP blogs and have never seen this before…

Thanks, kj

Same issue here, anyone submitted a bug for this yet?

Resolved via reinstall and another manual DB import.

Thanks Michael. I can easily lock out the blogs but I guess the question I have really relates more to security vulnerabilities. I’m fine with leaving the blogs as is as long as doing so doesn’t leave code out there that can be exploited. We’ve got several 2.0x blogs out there and I’m just now migrating our active ones to 2.1. I saw Brian’s script and it scared me a bit. I guess I should play with it in a test instance and see how it works with my host. Thanks again. -kj-

I do have registration enabled and did check, there are no bogus user accounts.

You are right vkaryl, I too suspect trackback spam, it’s odd that it’s never been a problem until now for us.

Looks like our base install will need to include Akismet, SK for Akismet, and BB. I have those running on one of my “open” blogs and they do a FANTASTIC job together.

-kj-

Interesting. How can this be prevented? I run Akismet, Spam Karma 2 and Bad Behavior on my ‘open’ blogs, and have never had this happen. SK2 and BB are awesome. I never really bothered with these plugins on other blogs because I thought requiring login was enough. I guess I’ll need to install and configure those as well…

Hmmm. I was getting the same error, but now I’m not … however the SC is inoperative … it runs and finds ‘no errors’ in this text:

fencs fasfdsafa sdfg adsf z zxdf asdfasd

Odd. Is the SC working for others?

-kj-

This can be marked resolved.

The problem was Bad Behavior.

https://www.homelandstupidity.us/software/bad-behavior/

Got the new version and whitelisted the IPs, and it’s basically working now.

Peace…

-kj-

Just started having this problem but only on ONE of my blogs. It was working perfectly in mid-December. I just upgraded both blogs to 2.0.6; one blog is in a folder, the other is in the root. The one in the folder DOES NOT WORK, the other does. I’ve verified the path and presence of xmlrpc.php, I’ve added .htaccess as dailyfoot mentions, I’ve chmodded the file, tried IE, IP addressing, nothing works, but it did two weeks ago. Whiskey Tango Foxtrot…anyone?