In a continuing series, I bring you more news on the site's progression to the new Geeklog engine. Here's what's new, changed, or different today:
- Thanks to a recommendation from osxpounder, you can now easily see your posting history -- just click on your username in the 'Welcome to macosxhints' line in the header. I've also added some text boxes pointing to that link on the Account Information and Preferences screens. This isn't an ideal solution, but it was the easiest to implement quickly. Longer term, look for the actual link on those two pages, as well as in the header.
- If you haven't tried it yet, the new comment feed is really working well. The author of the plug-in has made some improvements to it, and you can now see the comment author's name (along with the link to the hint) in the feed. It's a great way to keep current with the new comments added throughout the day.
- I'm still working on the "backslashes in comments" glitch. The database is now the same as it was pre-upgrade, but the slashes are showing. The next step is a mass-replace, but I'm taking time with that one, as I don't want to break any older code snippets which do need slashes.
- Important! On the subject of backslashes, the new version of Geeklog doesn't like them! Yes, even in [code] tags (even though backslashes will look right in preview, they will not be written to the database). This is due to a change in the way Geeklog's parser works. That's the bad news. The good news is that a fix is in the works, and we'll have it in place before the weekend's out. For now, if you're submitting code that contains backslashes, or any other special characters, please email me a copy of your code!. Send it to robg at this site's domain, and let me know which submission it goes with. This is really the only way I can be certain that the code is handled correctly. I realize how important this is to everyone (myself included), and we're trying to get it fixed as quickly as possible.
-rob.