I’ve since realized that Typo’s development activity has gone way up, and Mephisto’s has gone way down. I have been using Typo on another blog venture of mine and am in love with it. Actually, I’m loving it much more than Mephisto these days for several reasons, most of which pertain to user friendliness. I did run into an issue with trackback spam on Typo, which I’ve read as a big complaint about it. But trackbacks aren’t even an option on Mephisto, so what’s the big deal?

The point I’m trying to make here is this. If there’s anyone out there with experience migrating from Mephisto to Typo I’d like to hear from you. There’s plenty of google hits about going from Typo to Mephisto, but nothing in the opposite direction. I’m interested in converting this blog, Tongue and Groove (once again).

Without having enough time to really look into it, I believe Mephisto is using TZinfo Gem to convert the database timestamp to whatever you set your timezone to be in the Settings and Lucid is reading that as UTC anyway and attempting to convert it to the users current time.

So rather that fudging the JavaScript, I decided to reformat the date that Lucid sees and let it do it’s thing. In other words, I plugged the following into the home.liquid, index.liquid, and single.liquid templates:

from

<p class="auth">Posted
<span class="typo_date" title="{{ article.published_at }}">
{{ article.published_at }}
</span></p>

to

<p class="auth">Posted
<span class="typo_date" title="{{ article.published_at | date: "%a %b %d %H:%M:%S MST %Y" }}">
{{ article.published_at | date: "%a %b %d %H:%M:%S MST %Y" }}
</span></p>

where MST is my own time zone.

Hope this helps others, as I wasn’t able to find any other info about it.

Then, as I was browsing through the Mephisto Wiki I stumbled upon the answer. The problem was stemming from the fact that I’m running Mephisto on Apache. According to the wiki entry I found, it’s because Apache likes to add a trailing slash (/) to anything without an extension (stuff that follows the dot “.” in a filename) thinking that it must be a directory. Rails urls (and therefore Mephisto urls) use Pretty Urls instead of extensions and the like.

Apparently, however Mephisto is handling comments is being cached weird in Apache because of it. The easiest, and highly effective, solution is to plug the following in your public/.htaccess file somewhere (I put it at the bottom):
DirectorySlash Off
Since it took me 4 hours to find that post with the answer, I thought I’d post it here as well and hopefully those looking for a solution can find it in one of the two places quicker.

I’ve been working on migrating this old blog to Mephisto blogging system. Mephisto runs on Rails which I have blogged about before and still continue to love and swear by.

The old blog I wrote in PHP a few years ago. I was just getting sick of re-inventing the wheel every time I wanted to add and maintain a new feature. I wanted a new system that I didn’t have to build and maintain so that I could focus more on the actual content. Mephisto also allows you to use Akismet for spam defense. Akismet is typically used with WordPress and does a great job of keeping comment spam out of your blog. I was spending way too much time removing spam from the old blog, so Akismet is a welcome change!

Also, for the sake of time, I decided to download a theme for Mephisto rather than design one myself. I chose the Lucid theme which is actually a port of the Lucid Typo theme (Typo is another Rails based blogging system). I have tweaked the default theme quite a bit to be better suited for SEO as well as handle my google ads. I also changed the default color from Ruby to Mint. But if you like the Ruby better you can change it in the upper right corner. You can also change the layout from static to liquid. These options are a few of the reasons I chose the Lucid theme.

Last but not least, I’ve finally made the transition from using Webalizer as my tracking software, to using Google Analytics instead. Google Analytics is a robust tracking application that is comparable to expensive tracking apps like Omniture but is offered as a free service. I’m extremely impressed with Google Analytics’ capabilities and how easy it is to implement. I’d recommend it for any website, big or small!

Let me know what you think of the new do.

It’s not my intention to drone on about my personal life or useless information, but rather it is my intention to document my frustrations as a web developer/designer. Any time I am having problems with anything I’m working on, I plan to write it here along with the solution. More often than not, I’ll try to post things that I’m having a hard time finding the solution to on the internet. The idea is to get the solution out there for others who may be having the same questions. It will also give myself a place to go when I know I’ve worked on a problem before, but I can’t remember how to fix it.

Your feedback via email is welcome. Enjoy!