New fancy GUIs for plugins and…
Image does not exist: images/comment-editor.jpg
guess what? :)
Friday, February 27, 2009
Tuesday, February 3, 2009
Blog / General / News / 2PL? In my FP? It’s more likely than you think!
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
Saturday, January 24, 2009
Blog / General / News / FlatPress 0.812.1 Fortissimo Bugfix Release
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!
Thursday, January 1, 2009
Wednesday, December 24, 2008
Blog / General / News / FlatPress 0.812 Fortissimo
FlatPress 0.812 Fortissimo
HO! HO! HO! MERRY XMAS!
Image does not exist: images/xmas-reindeer.jpg
ChangeLog
+ Brand new indexing system + Many bug fixes (drafts, validation errors, etc.) + Cosmetic changes in default admin panel
How to upgrade from Vivace
That’ll be surprisingly easy, even though there is a brand new indexing engine!
1) do a backup (just in case ;) )
2) Download the package from SourceForge
2) unpack the file you downloaded
3) drop your old fp-content/ to the new flatpress/ dir you unpacked
3) login as usual; if anything doesn’t work here (it should, don’t worry), reinstall
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!
6/b) you might need to empty the fp-content/cache/ dir if you had prettyurls enabled
Note: This is SVN rev227
Have fun!
UPDATE: if you’re experiencing a “syntax error”, try using these patched files. And tell your host they suck :D