Kevin Whitworth / Jacurutu

I've just tweaked NP_Ping (an update to NP_PingPong) because it doesn't seem to be pinging Technorati. I've added some tweaks I'd originally made to NP_PingPong to log stuff to the Nucleus Action Log (success, or failure with the error message), because although it appears there's code in there to do this, it doesn't seem to log anything. I've also got a feeling that the ping to Technorati is using the wrong URL (rpc.technorati.com:80/rpc/ping/ instead of rpc.technorati.com:80/rpc/ping - ie with a trailing slash instead of without).

Lets see if this works... (Perhaps I need a development environment, instead of testing on a live server?)

PS The result was inconclusive. When I started writing the post, Technorati hadn't picked up my last one. After I first posted this one, Technorati has picked up my previous post. I'm guessing they're running slow, so perhaps that was the problem? Still, I like my tweaks to NP_Ping. Plus - good new - Technorati's stopped displaying the raw HTML, so at least the Atom update worked! Hurray!

Update: I've posted the code in a separate article.

In my ongoing quest to get my entries on Technorati to display correctly, I found an upgraded Atom 1.0 skin for Nucleus courtesy of Rakaz. It upgrades the Atom 0.3 feed to Atom 1.0, and more importantly, my Atom feed now validates at FEED Validator. It needs tweaking slightly to insert the code from the Technorati Tags plugin - the feeds/atom/entries template changes the contents of the <content> element from:

Actually, at this point I think I realised what the problem was. There's far too many square brackets in the old Atom 0.3 template (which I dilligently backed up), so I suspect I made a cut-and-paste error at some point and corrupted it. Nevermind - hopefully when I post this, Technorati will get properly pinged (I'm not convinced that's working properly either now...) and it can then read the feed properly and render the content correctly, rather than as raw HTML.

You may ask why I bother? Well, mostly because I hate it when something isn't working! Fingers crossed... 

PS I've just discovered NP_GeSHI2 and NP_TinyMCE2 don't get along. In fact I'm thinking about taking TinyMCE off, as it doesn't do half the stuff I'd hoped, and doesn't look anywhere near as slick as the example on the Tiny MCE website. Fingers crossed this post will now display on my own site, let alone Technorati!

Well, I'm working through some of my New Year's resolutions. So far I've renewed my hosting and domain name, and I've just upgraded to NucleusCMS v3.31. All told it was a very painless process (to be fair, all previous upgrades have been too). All I had to remember was that index.php needed tweaking to support fancyurls. As far as I can tell, everything seems to be working fine.

Now I know Imran suggested that I should switch to Worldpress, but it wouldn't be as much fun. I'm trying to kid myself that I have some hands-on technical ability left (OK, that assumes I had some to start with...) by tweaking the off bit of PHP from time to time. Which reminds me, NP_Ping, which seems to replace NP_PingPong for Nucles v3.31, doesn't seem to log to the ActionLog anymore (or maybe NP_PingPong didn't either - that might have been one of my own tweaks), so there's something to do straight away! I've also added NP_TinyMCE2, a WYSIWYG editor for writing blog entries. Mostly this was because my own plugin to make external links open in new windows didn't really work how I wanted, but a quick look at the Tiny MCE website showed a few useful features like a spell checker (to save me cutting and pasting posts into Word), although some of these don't appear to have been implmented in the Nucleus plugin. Still, it looks good so far, and it may be possible to add those features with a bit more tweaking.

Well, that's it for now. Tomorrow I'm off to Ponds Forge to play Octopush in the Nautilus competition, so I'll post the results when I get back.