Some readers may have noticed a recent bug with the comments framework this blog is using from the Django project. I have concluded that this bug is due to the site-wide caching I have enabled. The comments which were added over the past weeks were posted after the cache expired for the page which a reader was commenting on.
In this event, I will be building the caching from the ground-up, using Django's caching framework. This will include manually specifying which parts of the site to actually cache. My main concern and why I have caching enabled is database queries from the blog content sections. Since I use some custom templatetags to render links to bookmarks and packages, and soon reviews, I needed to cache these results to limit the database queries, to allow the site to perform quicker.
My idea would be to enable caching directly in these template tags, where all the heavy database queries are. I chose to create the blog using this method for my personal ease of use. I found other formatting languages such as markdown and BBcode too limiting. I really enjoy the power and freedom which Django templates provide me. It allows me to create links which absolutely cannot break. I personally hate visiting a website which has tons of broken links due to the the posts having static links to the external websites. To remedy this, I created a packages list, and a bookmark system. If I change the link for a package or bookmark, all pages which reference them will automatically reflect that change.
This is the main reason I wanted to create a custom blog platform. I saw a major flaw in other blogging software on the market, and wanted my blog to avoid the broken link flaw. The only draw back, is that the site does need to use extensive caching in order to limit the hits on the database, and to keep the site running smoothly for all visitors.
Originally today, there was suppose to be a different blog post published, but I postponed it until Monday. This post will be published in it's place to address a recent bug in my blogging software. This bug will be resolved over the weekend, and you should see less glitches on the site as a result.