Oh-kay, for people who aren’t reading the forums, the SVN trunk is now officially unstable.
Trunk is reachable using:
svn co http://flatpress.svn.sourceforge.net/flatpress/flatpress
The fixes for stable are in a branch:
svn co http://flatpress.svn.sourceforge.net/flatpress/branches/0.804-vivace
Being “unstable” means that if something is broken… ARGH a BUG HOW IN HELL AM I SUPPOSED TO GET A DEGREE BEFORE DECEMBER??????? ARRRRGH!!! erm, I mean, “…I’ll have to fix it”.
The first part it’s my usual reaction against bugs.
That one or “damn annoying n00b nobody ever complained about that one WTF do you want??”
Soooo, our new fancy indexing system will allow us to have a more reliable (?) storage, and have not to fear anymore PHP’s memory limits. Yes, that was my main concern, not “features”.
BTW, first the good news.
omg! OMG! OH-EM-GEE!!11! THAT IS TEH AWESOMEST!11! Post count near the categories!
Default: disabled. The reason it’s I have to open and load every single index (there is one index for each of your categories), and that’s not cheap (= slow). BTW if you don’t care, open your plugin.categories.php (in SVN of course), set the corresponding option to true and enjoy your truly new awesomeness.
Yes, there is an index for each category.
If you think of the FP’s storage as a DB, then the old index was a subset of the “Posts” table (the files on your disk); this subset - of course - contained the categories as well.
When you asked the system for a search filtered by category, a sequential scan (sloooooowww) took place.
This won’t happen anymore, since each category has its own sub-index (conceptually in DB-speech there is a secondary index for the category attribute).
Now, the “bad news” part.
As I said the focus here was in reliability/performances in the long distance, which doesn’t mean exactly “faster”, but always “acceptably fast” when the number of posts increases… and not failing with a white page of death, because the memory limit exceeds; theoretically we won’t have fear memory limits anymore, since the index is never loaded completely to memory.
…and - I know you’re going to hate me - that’s why some minor features might not be there anymore.
the current winner is…:
next/prev link in permalinks. So you won’t have anymore the title of the next/prev entry (when in permalink mode: next/prev page should still be there).
The reason it’s I’ve tried to keep the structure of the bplustree as clean as possible (I won’t bother you more on this subject, but believe me :p).
This does not mean that those features will never be back; there is a hack for instance to take that next/prev thingie back (scan through the tree), but it would make then the index thing a little pointless :p
I have a few ideas in mind to take it back, however, maybe not for this upcoming release, that’s all ;)
There is another winner, the admin panel, where, in order to take more advantage of the indices, I’ve killed the author column, since there is no official support for multiuser, yet, anyway.
I hope you’ll anyway like the efforts.