Blog / General / Only human
Image does not exist: images/agent-smith.jpg
Even though I’m pretty pleased, I still lack the superhuman powers you probably sometimes believe I’m blessed with (but, hey, thank you for that), and therefore I can’t always match your expectations.
The major obstacle is that I have a life as you do, and even though I love FP, I really don’t want to spend all my spare time on it ;)
I’m not saying I’m not going to work on FP anymore, but if all my free time is spent by helping you out on the forum, there won’t be any time left for actually doing the work :D
So you have to bear with me ;)
PS: It’s ten years since The Matrix was released. Too bad they never made any sequels.
Blog / General / Just sayin’…
I’m not saying this will make it in the next release, but I just want to show it off :p
Image does not exist: images/just-sayin.jpg
(Live Writer works and so any other MetaWeblog API enabled editor, like ScribeFire, or whatever is your favorite)
Blog / General / News / What’s new in SVN
New fancy GUIs for plugins and…
Image does not exist: images/comment-editor.jpg
guess what? :)
Blog / General / News / 2PL? In my FP? It’s more likely than you think!
With SVN revision 241 I’ve added a new functionality to FlatPress along with a bunch of fixes to some inconsistencies of the backend.
For the latter, I’ve just removed the old ugly array_change_key_case by setting to lowercase array strings at a lower level; not really awesome news here :D
What’s really cool (in my obviously not-so-humble opinion) it’s a new mechanism I’ve implemented to store your entries.
What was wrong with the old? Nothing much really, apart from the fact that a failure in the index backend would have prevented your entry to be saved.
Artist’s Rendition:
Image does not exist: images/FUUUUpress.jpg
The new system is a little bit more cumbersome, but should be safer.
In short, before the entry is added to the indices it is stored in the draft area (fp-content/content/drafts/); once each index has been updated the draft is then MOVED to the correct place (fp-content/content/YY/MM/).
This might result sometimes in a duplicate draft/published entry when a failure occurs in the middle of the process, but it is not really a defect.
No, it’s not a 2-Phase Locking :D, but it’s still something.
If you know you usually edit a few times your entry before it’s really definitive, as I do, in order to work better, I suggest to always save as DRAFT, and only FINALLY publish.
In rev.241 there are other fancy additions; the error message connected with write failure is now more descriptive in the panel; also you’ll get a nice yellow notice when you’re editing a draft, remembering you the entry is not published.
I’ve also added a few classes to the <body> tag of the panel; in this case .draft will dim your background to a darker shaede of grey to remember you visually the editing is ’safer’.
I hope you’ll like it!
bye
Blog / General / News / FlatPress 0.812.1 Fortissimo Bugfix Release
ChangeLog
+ Made BPlusTree completely PHP4 compatible
+ Fixed many ULONG issues in BPT
+ Fixed loose search edge case in BPT (now back/next links should always work)
+ Fixed many (safe) notices
+ Fixed PrettyURLs/global $post
This is SVN rev235
Updating from Fortissimo Final
1) do a backup (just in case, shouldn’t be needed ;))
2) drop your fp-content to the new flatpress/ dir you unpacked
(for the most, only fp-includes/core/ files are really affected so you might upload only that)
3) login; if you can’t, empty the fp-content/index/ directory, then login
4) go to the maintenance tab and choose to rebuild the index
5) wait for the page to load completely
6) scroll down, you should see a message saying the process has finished: you’re done!
Upgrading from Vivace
1) do a backup
2) drop your fp-content to the new flatpress/ dir you unpacked
3) login
4) go to the maintenance tab and choose to rebuild the index
5) wait for the page to load completely
6) scroll down, you should see a message saying the process has finished: you’re done!
