asecondforever

Thanks, HandySolo!

Well, maybe upgrading will be the easiest way to be able to save it in an importable form. (since a later version will have an export feature) My goal, though, is to get it over to wordpress.com so I won’t have any hosting fees. No sense in continuing to pay for hosting for a blog that’s now just a static information archive.

Diane,

I spent some time in the codex, but wasn’t able to find out exactly how I should go about saving it. Versions after 1.5.2, I believe, began to come with an export feature which I think would save everything as an XML file (“WordPress eXtended RSS or WXR”). WordPress.com can import that. But 1.5.2, doesn’t seem to have any export feature.

Do I therefore need to make a backup of the database using the webhost’s control panel? Will it save it in a similar, importable format? (I’m rusty on this stuff. :-/)

Thanks. I guess I’d better start researching the process of saving and importing it.

Thanks macmanx. Actually, it seemed to have worked itself out anyway. After being away for a while, I came back to find a new log table had been started, and had a couple of entries. Just for the practice, though, I went ahead and stepped throught the procedures you outlined above. ??

I guess Blogdigger just isn’t responding to some pings. Overloaded, malfunctioning, or whatever…

As an update, I did export the log table and sent it to Michael. He found some pertinent info in it and informed Technorati so that they might make the needed changes in their bot.

I then emptied the log table. That seems to have Technorati now picking up my posts. So that’s some success. ?? However, Blogdigger still isn’t picking them up. (Neither is Blo.gs, but their service seems pretty limited right now, so I don’t make much of that.) I notice that now, approaching two hours after emptying the table, there still has been no new table created. i.e., having refreshed the Bad Behavior log, “Browse” is still not clickable. I don’t know how to interpret that, don’t know if a new table would appear as soon as anything is blocked or only at some other intervals. If the former, then it seems Blogdigger’s bot (not to mention spammers) hasn’t even come to the site yet.

I don’t need to do anything special to allow a new table to begin to be created, do I?

At any rate, thanks for the help. Looks like I’ve basically got it sorted out. ??

Oh, and I neglected to deactivate Bad Behavior before emptying the table. Hope that wasn’t an error. I did deactivate it and reactivate it afterward. (Can you tell I’m an expert at this stuff? :-/)

Okay Michael and macmanx, I will do as instructed tomorrow. (It’s too late for it tonight as I’ve never tried exporting anything from phpMyAdmin, and don’t want to get into something new when I’m not alert.) Thanks again.

Okay, thanks macmanx. I’ll try that. Can I assume that in phpMyAdmin, that means simply deleting those entries in the section under “Browse” where I found those entries. I don’t need to go into “SQL” or “Structure,” do I?

Thanks for sticking with this. I may actually get it solved. ?? (May need to come back to it in the a.m. though.)

[edit] Do I just click “Empty”?

http_user_agent is “Technoratibot/0.7”

“denied_reason” is “I know you and I don’t like you, dirty spammer,”

Unless something left over in the DB (or some such) is affecting things, then I’m running v1.2.4. I completely deleted the older version before installing v1.2.4 (not necessary, I don’t think, but…), and 1.2.4 is what it says on the admin plugin management page.

Hmmm, interesting. Yes Technorati is in there over and over — all the times I’ve tried to ping them I guess. Looks like it’s giving Technorati a 412 error code every time.

(Oddly, the date on all those entries is Dec. 11, though It’s still Dec 10 here… well I don’t know where Technorati is located.)

[Edit] Oh, I should add that I even tried applying the changeset above, but that didn’t seem to make a difference. So for now I’m back to the original WP code. I’ve retested with BB deactivated and, again, Technorati did pick up the post after about 10 minutes under those conditions.

Hmmm, well I’ve upgraded to Bad Behavior v1.2.4, but the problem persists. Posts aren’t being picked up by Technorati. FWIW, it seemed to begin a few days ago when I tried to “claim” my blog on Technorati. The claiming process failed and gave me a message saying my site was “unreachable.” That problem persists as well.

So Technorati (and it seems at least Blogdigger and blo.gs as well… IceRocket seems to pick up the posts, albeit with a delay of about a half hour) is having trouble working with my site’s pings. Now, as mentioned above, it does seem to involve Bad Behavior, as deactivating it seemed to solve the problem. Should I apply the changeset above, or does that not make any sense now that I’ve upgraded to the new version of Bad Behavior? Any other thoughts? Thanks for the help.

Thanks macmanx!

I noticed a few days ago that my posts seemed to stop showing up on Technorati and some other services. Pings were not getting through – or something. After much tinkering and researching here today, I finally deactivated Bad Behavior (version 1.2.2) and found that that fixed the problem (at least with Technorati… haven’t tried the others) So it seems to be the result of the bug/Bad Behavior issue mentioned here. Does that actually make sense?

The strange thing is that Technorati was picking up my posts with no problem prior to just a few days ago.

Anyway, as a non-coder, but one who can follow simple instructions (I hope), do I need to write in the changeset #2933 mentioned above (should be able to do that), or would deleting Bad Behavior and upgrading to the new version solve the problem? Do I do one, or both? Thanks.

(BTW, while my blog is only a few months old, I’m happy to say that Bad Behavior has not let one single piece of spam through since the say I launched the site. ?? )

That seems to have fixed it. Thanks again, Ryan, for your very prompt reply!

Thank you VERY much Ryan! I’ll give that a try and report back. ??