• Resolved sohodojojim

    (@sohodojojim)


    We have a clean WP2 install (piping fresh, did not exist before the 2.0 release) here:

    https://sohodojo.com/onetblog/

    which is being used to harvest and publish our posts at Omidyar.net.

    After getting everything humming, we went to Technorati and created an account. We then tried to claim our blog. Although we absolutely know that the uname/pword we are putting in is correct, Technorati Quick Claim does not work. We then tried the paste of the script snippet, no dice. We even resorted to the post the prescribed link method and just cannot get Technorati to recognize our blog.

    Are we just extremely unlucky? Has anyone else had this problem? And are there any tips or workarounds to help us get this blog claimed at Technorati?

    Any assistance is gratefully appreciated,
    –Sohodojo Jim–

Viewing 14 replies - 1 through 14 (of 14 total)
  • Only one point: This has nothing to do with version 2.0. My blog is running this version and all things with Technorati works fine (even plugin-tags and categorie-tags are recogniced by Technorati).

    Thread Starter sohodojojim

    (@sohodojojim)

    Hi Herb,

    So you have WP2 and were able to ‘claim’ your blog at Technorati?

    Or did you upgrade to WP2 on an existing blog that was already claimed?

    Our pings via Pingomatic are being registered at Technorati. We see our item listings when we do searches there. But we cannot for the life of us get the claiming process to work.

    We’ve put in a tech support ticket to Technorati but expect it will be some time before we hear back from them.

    –Sohodojo Jim–

    Moderator James Huff

    (@macmanx)

    The feed claim is probably not working because your feed is invalid.

    https://feedvalidator.org/check.cgi?url=http%3A%2F%2Fsohodojo.com%2Fonetblog%2Ffeed%2F

    Thread Starter sohodojojim

    (@sohodojojim)

    Hi MacManx,

    Thanks for pointing that out. I did develop my site on my intranet and then clone it out to my public server. So I did have a non-public top-level domain prefix on a bunch of posts in the DB, and one was empty (I think I reused a sample entry rather than delete it).

    So I corrected these and feedvalidator.org is now happy. But dern if Technorati still will not let me claim.

    I am wondering if my host’s community server config is so locked down that it won’t let Technorati talk to my blog server-to-server?

    I’ll check into that next as I just don’t see anything obvious why claiming won’t work.

    Thanks to you and Herby for helpful pointers.

    –Sohodojo Jim–

    Moderator James Huff

    (@macmanx)

    Check your server access logs and see if the Technorati bot accessed your blog after you submitted the claim.

    Thread Starter sohodojojim

    (@sohodojojim)

    Don’t ask me how, but I finally got my blog claimed. Although Technorati would not recognize my Quick Claim log on, I did the sidebar embed. After pressing the Claim button, the Technorati page showed the spinning logo as it went to “check my blog for Technorati goodness.” The logo just kept spinning away forever.

    I eventually clickec back to my account and lo and behold, my account showed one blog claimed by the embed technique!?

    Oh well, the process wasn’t smooth, but I did learn about GUIDs along the way and was able to tweak my post table to be correct.

    Thanks for the assistance,
    –Sohodojo Jim–

    same issue here, technorati quick claim doesnt work with my fresh install, and it when technorati embed finally allowed me to claim after about an hour of loading, it still has yet to index ANY of my blog posts!! I have another blog 1.5 hosted on this same server, so there is no reason why technorati would be getting blocked

    I used the embeded, and posting method to claim. When using the posting method, I did notice that the link was not rendering as a link in the post nor in the feeds. I disabled the rich editor, reposted the link and tried claiming again. While it was checking the site, I also clicked the link in the post. Finally, I checked the technorati window again and it was still spinning. I clicked the back to account buttion and it showed my blog as now being claimed.

    My only problem now is that I cannot get it to show on the site that technorati is embedded. The graphic will not show on the page.

    Hope this helps someone.

    Cheers!

    Hi all

    Me too has just claim my blog and followed as per the instructions for the embedded claim. After pasting the code and waited for 2 days, the graphic has yet to show on my sidebar… I was wondering if anyone has encountered the same problem, can anyone enlighten me?

    I have just sent a ticket for this.

    Alex

    LOL! It looks like it’s an epidemic!

    Mine isn’t claimed yet either. It shows as “pending” and I did manually ping it from the Tech manual ping page, and it shows as “updated” X hours ago. Embedded code is in the footer AND a link in a post, and still no joy.

    Worked just fine for me when I did it quite a while back. I just edited my sidebar, dropped in the code, and wa-la, was done.

    Worked for me, too, but my blog at the time was on 1.5. This new one is on 2.0.4.

    Mod-security is also a factor creeping into most shared hosting situations, and I’ve gotta wonder if that’s a factor in this technorati claim your blog thing, though I can’t say for sure. I’m currently switching hosts because my host of over 9 years has just added mod security, broken lots of stuff in the process, redefined path from root (oh yeah, THAT was fun!), and created filters SO RIDICULOUS that I can’t even have anything in the wordpress interface that calls a file with the letters “rpc” in the filename. Look at the ping list and you’ll see how frustrating that is!

    Who put this in as resolved? It isn’t.

    It’s up to the original poster. His issue IS resolved. Others should start new topics instead of tagging along on a resolved thread.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘WP2 failing on Technorati claiming’ is closed to new replies.