25/12: Merry Christmas
A very Merry Christmas to everybody out there reading this!
14/12: Maintenance & Bug Fixing
I've spent a bit of time this evening doing general maintenance and tweaking some of the NucleusCMS plug-ins that I use.
Firstly, I discovered that if I used the tag cloud on the right to bring up a list of posts with a specific tag, then the links on the navigation menu were all broken on either the tag search page, or any subsequent post linked from the tag search page. They were all prefixed with "tag". It turns out that the problem is between the TechnoratiTags plugin and the Fancy URLs plugin (which isn't actually a plugin, and now appears deprecated...). The end result is that you also need to reference the Fancy URLs config file in tags.php (and tags, which you need to work with Fancy URLs) by adding the following before including the standard config file:
I've also tweaked the Action Log entry created by Technorati Tags. I keep finding the following in the Action Log, which I suspect is a result of spammers trying to post comments directly:
I've changed the ACTIONLOG::add statement (in the doSkinVar function) to be as follows:
which should record the IP address of whoever is triggering the error. I can't test it, because I can't replicate the error (well, I can't be bothered to try), but I'll keep an eye on the Action Log to see whether it continues to occur, and whether I can tie up the IP addresses with other known spam attempts.
Meanwhile, I keep wondering about changing the skin, or developing my own. The only problem is I've now tweaked so many things, I'm not sure I want to risk such a drastic change. Maybe I'll just stick to migrating to a more up-to-date version of Fancy URLs...
Firstly, I discovered that if I used the tag cloud on the right to bring up a list of posts with a specific tag, then the links on the navigation menu were all broken on either the tag search page, or any subsequent post linked from the tag search page. They were all prefixed with "tag". It turns out that the problem is between the TechnoratiTags plugin and the Fancy URLs plugin (which isn't actually a plugin, and now appears deprecated...). The end result is that you also need to reference the Fancy URLs config file in tags.php (and tags, which you need to work with Fancy URLs) by adding the following before including the standard config file:
include('./fancyurls.config.php');
I've also tweaked the Action Log entry created by Technorati Tags. I keep finding the following in the Action Log, which I suspect is a result of spammers trying to post comments directly:
TechnoratiTags Error:http://www.jacurutu.org.uk/item/#nucleus_cf
I've changed the ACTIONLOG::add statement (in the doSkinVar function) to be as follows:
ACTIONLOG::add(WARNING, 'TechnoratiTags Error. URI: ' . serverVar("REQUEST_URI") . 'IP: ' . getenv('REMOTE_ADDR'));
which should record the IP address of whoever is triggering the error. I can't test it, because I can't replicate the error (well, I can't be bothered to try), but I'll keep an eye on the Action Log to see whether it continues to occur, and whether I can tie up the IP addresses with other known spam attempts.
Meanwhile, I keep wondering about changing the skin, or developing my own. The only problem is I've now tweaked so many things, I'm not sure I want to risk such a drastic change. Maybe I'll just stick to migrating to a more up-to-date version of Fancy URLs...
