I would have released the new functionality bundled with the new version, but I’m still not satisfied with the result, so in the meantime I’m releasing Remote Posting as a (hacky) plugin.
Image does not exist: images/remote-posting.jpg
I hope you’ll like it :)
bye
Fellow commenter Pandian is already crying FlatPress dead.
Image does not exist: images/istheprojectdead.jpg
I thought it wasn’t, yet.
New fancy GUIs for plugins and…
Image does not exist: images/comment-editor.jpg
guess what? :)
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
+ 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
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!
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!
