At last! Just before your holidays, when sun is hot and you really care about everything except posting on your blog (ha-ha), here it is, the new FlatPress has come, with a new logo, a new release and this brand new wonderful website.
I’m waiting for those who are of course going to say they liked the old logo and the old site better :D
Get it from SourceForge
As announced, now FP comes bundled with the only English language (so that nobody complains :P), but you can found here:
This list will be updated as soon as people sync their translations with the new version; diffs are in this post; of course you can also update the wiki on your own (if you prepare a package, please do it :D).
Yes, we have a wiki.
If you are lazy and you don’t want to start over, we have some packages for older versions listed on this older page.
Be sure to read the guidelines (for instance lang files should be in utf-8)
We still lack a forum… I’d like to use PunBB but the lack of utf-8 blocks me; utf-8 won’t be there until 1.3 (which is still under development — and which looks cool)
Installing a new language
To install a new language just get the contents of the lang/ dir of the compressed archive and overwrite when you’re (eventually) asked.
Then choose the new language from the config panel.
The complete changelog since 0.612 can be found here.
If you’re thinking this site looks a lot like my personal blog you’re right :D
An Italian spb user has ported an hack he did for SPB to a FP Plugin.
JNotify plugin notifies a predefined Jabber user whenever somebody comments your blog.
The plugin it is in fact a wrapper around Carlo Zottmann’s PHP Jabber.
I didn’t have time to test (I don’t usually log into jabber, really), but I think it’ll do the job :)
Well, kudos to fabrixxm (and kudos to Carlo :))
You can find both the hack and the plugin here
I’ll take this comment as a base for a simple roadmap, or “what’s in the future of FlatPress”.
First of all, friendly urls (prettyurls plugin) are *already* in the works! :)
Previous versions (pre-Crescendo) had that as an experimental plugin (which didn’t work really well, though), now I’ve played a little bit more with mod_rewrite and see how it works… and I saw PHP as such facilities that mod_rewrite is just a little “plus”.
I’ve studied more how other scripts work, and so I’m thinking that the best way to accomplish this is breaking a bit the now old URL-compatibility with SPB.
Yes, actually static.php and comments.php are there because I wanted plain URLs compatibility with SPB: I didn’t want my URLs to change because I didn’t want the links in my entries to break, but now I think that I would lose so little that this may be worth the price, what I’m asking is do you think the same?.
I would centralize all of the processing to index.php as is done in other well known and loved platforms such as WordPress itself or wiki systems (MediaWiki or Doku).
Remember that if you always linked ONLY permalinks (in your posts or all around the web) you won’t have any issues: you may have some little problems (but only with links) if you don’t have mod_rewrite (an .htaccess would otherwise send every URL to index.php, as it’s done with WordPress) enabled; in this case you may have receive a 404 error if you tried to browse to comments.php or static.php
I may still add a pair of dummy comments.php and static.php to redirect to index.php for systems which do not have mod_rewrite (cheap hosting and such).
I’ll probably take this occasion to do some rework on how the infrastructure currently works too.
Now we have some master classes which tell the system “which kind” of page (static, comments, etc) you’re viewing; if system will become centralized on index, this may need some rethinking, because it would be probably not as useful as now.
Plugins and widgets
This summer may be time to think about the way plugin will hook the control panel, a feature needed, but still not refined.
Moreover, I’d like to turn widget and plugin panels into something user-friendlier.
This is what we really lack, here… -__-’
All of this is not for now: Crescendo is now feature frozen which means that if you won’t find any bug in next two weeks or such, I’ll probably finally release it.
What really stops me is that I should open that damn forum and integrate it into the new website, together with the wiki.
Yes, there is a new website, and even a new domain, a new logo, and new designs (leggero docuit)… stay tuned, guys ;)
The release targets all of the issues listed before
FIXED: spaces in file names are escaped as dashes "-" when uploaded
FIXED: various bbcode issues
FIXED: scale/width bbcode/thumb issues
MDFD: now thumb creates a .thumb dir for each subdir of images/
FIXED: leggero CSS
FIXED: double entity encoding
ADDED: (since RC1): when loggedin trying to open a non-existent
static page will bring you to the "add new static" panel