Monday, October 24, 2011
Strict Standards: Non-static method StringParser_Node::destroyNode() should not be called statically, assuming $this from incompatible context in /home1/passjoe/public_html/debian/fp-plugins/bbcode/inc/stringparser.class.php on line 358
I’m in the process of moving the entries from this blog into my new site at http://stevenrosenberg.net/blog. Eventually I hope to have the Debian posts on that blog, running under the Ode platform, appearing with their own theme, something (i.e. different themes for different parts of the same site) that is very possible to do in Ode, a system developed by Rob Reed to use flat files like FlatPress, but in a less-WordPress-ish and more Blosxom-y way.
Today I turned off comments for all of these FlatPress blog entries because they have been attracting a significant amount of spam.
Turning off comments in FlatPress is not done globally. You (and most recently I) must go into each entry, one by one, and turn off comments for that particular entry. And hitting the “back” key in the browser sends you not to the page of entries you were working on but instead takes you back to the first page of entries. Opening up each entry in a new tab is the way I got around this.
I’m using Disqus comments on my new site, and for now I’ll keep them open on all entries. Some bloggers I know keep comments open on entries for a few weeks, then close them to discourage spam. I think this is a good practice, especially because most comments on old blog entries seem to point out that something in the entry is no longer correct now that the software/hardware/regime/world has changed.
I’ve got maybe a fifth of these entries at http://stevenrosenberg.net/blog/linux/debian/, and I’ll move the rest as time allows. Once they’re all moved, I’ll either post an entry saying that this particular blog (in FlatPress) is “frozen,” or I might just take the site down entirely since all the content will be available at the new site.
Since this is a “new” entry, I will leave comments turned on for now and see how the spam-related consequences manifest themselves.