I just found out that the search function built into FlatPress does not look at the text of the entries but only at the titles (and possibly the tags; I’ll have to check on that one).
I know this because I was searching for an entry, and it wouldn’t come up when searching for a word I knew was in the body of the entry but not necessarily the title.
It’s not a FlatPress deal-breaker, but bloggers might want to explore the alternatives. I’ve been using the Google Custom Search box on some of my other blogs, and that works very well.
That's especially the case right now as forum member pierovdfn has released a patch to one of the PHP files in FlatPress that eliminates a potential exploit in the authentication code.
For existing FlatPress installations, applying the patch is as easy as swapping in 21 lines of PHP code. I did it this morning, and everything is working fine.
I wondered why the official FlatPress blog shows the number of views per post, and mine did not.
The “xx views” at the end of every post is enabled by the PostViews plugin.
To enable the PostViews plugin, go to the Admin Area, click on plugins, then go down to PostViews and click enable.
The per-post counter starts when you enable the plugin.
Both Blosxom and Ode are based on Perl scripts, while FlatPress is written in PHP.
Ode has in its favor an excellent default design/theme, its mission of teaching the user Perl (since it was developed with the now-classic “Learning Perl” O’Reilly book in mind and includes two extensively annotated extra versions of the main Perl script), good documentation and an enthusiastic and inclusive lead developer in Rob Reed (Ode has its own Twitter feed as well).
Sweet! You CAN call in a photo from the menu after you’ve uploaded it. FlatPress uses BBCode to drop it in. I’m starting to think I need to learn a whole lot more BBCode than I do, even though FlatPress responds very well to straight-up HTML.
Look at the wiki for FlatPress themes. I’m overwhelmed a bit by how many themes there are to choose from, many of which have been ported from WordPress.
I’ve made a few changes here and there, but thus far I haven’t started hacking into the CSS and the templates for this FlatPress blog.
But I will.
After writing my entry on CMS and blog software that doesn’t require a database, one of the commenters recommended FlatPress.
It’s not just the name (a play on WordPress, on the off-off-off chance that you missed that particular bit of wordplay). OK, a lot of it is the name. By way of explanation, it’s called FlatPress because it stores its data in “flat” files and not in a database, such as the MySQL that powers the back end of WordPress and innumerable other content-management platforms.
But it turns out that FlatPress is a very easy-to-install blogging platform that uses PHP, stores the entries in the aforementioned flat files, runs extremely fast, takes up very little disk space (1.9 MB after the files are uncompressed, 508 KB before you unpack it) and is refreshingly simple.
Part of that simplicity at the level this particular blog is at includes entering a lot of HTML (or BBCode) tags, and it’s not as easy to bring images into the system as it is with something like WordPress. But there is an uploader in the FlatPress software, and once you know where the files go, it’s easy enough to call them into the blog with the proper tags.
I took the offset off of the UTC so this blog reflects when the entries were created in Universal Time.
Edoardo Vacchi is the coder behind FlatPress, which is under the GNU GPLv2 License.
Edoardo does request donations, with a PayPal link on the FlatPress home page. I did make a donation — the first screen is in Italian, and the currency is euros. But once you enter the amount in euros you wish to donate and the enter your PayPal password, things magically turn into your own language (English in my case).
Thanks, Edoardo, for hacking on such a cool project.
When I get the time I’m going to start hacking into the code and customizing this particular FlatPress blog. I’ve tentatively decided to offer
one entry three entries per page, and that works quite well both in WordPress and FlatPress because there are links at the bottom of the entry to easily go from one page worth of entries to the other. Kind of like paging through a book, no?
I’m always torn about how many entries to include in a blog index. Most, including my own, seem to go on much too long.