Maintenance Release of pLog available
This first maintenance release after version 1.0 of pLog comes with many little improvements and bugfixes.
Upgrading from version 1.0 is as easy as overwriting all the files with the new ones - no database upgrade is necessary for any maintenance releases of pLog (first DB upgrade will have to happen with version 1.1).
Besides all the very important bugfixes there are some nifty little features I'd like to point out here (pardon me if I miss one, though):
Upgrading from version 1.0 is as easy as overwriting all the files with the new ones - no database upgrade is necessary for any maintenance releases of pLog (first DB upgrade will have to happen with version 1.1).
Besides all the very important bugfixes there are some nifty little features I'd like to point out here (pardon me if I miss one, though):
- the summary page supports multilingual display, which is especially interesting for those using pLog as a community blogging software. By default you need to pass the parameter lang in the URL along with the required language code (e.g. summary.php?lang=de_DE) to switch language.
Additionally there is a hidden feature that tries to guess the most suitable language according to the languages the User Agent (i.e. Browser) sends in its http_accept_language string. If one of the languages of the visitor's browser is available, pLog will server the summary in the most prefered language.
This feature is hidden because we need to do a database and language file update to offer an enable/disable switch in the summary admin section. And this won't happen until version 1.1. But you may activate the feature in no time by opening the file summaryaction.class.php in /class/summary/action/ and set HTTP_ACCEPT_LANGUAGE_DETECTION to 1. (should then look like that: define('HTTP_ACCEPT_LANGUAGE_DETECTION', 1); ) - the Dashboard has now a logout button for more convenience
- native support for podcasting
Information and Links
Join the fray by commenting, tracking what others have to say, or linking to it from your blog.
Comments
Multilingual summary
oscar | 27/05/2005, 21:13
Multilingual summary
reto | 04/06/2005, 20:44
Hi Oscar,
You're right, this has to be documented in the wiki. But maybe we should first have a solution for multilingual content, too. It's not enough to change the summary "default" content from english to german, if all the custom site content is still in one language (as an example take the welcome message). There are several way to solve this, and it's not hard to do, but we should discuss this first. I'll soon start a thread on the mailinglist.
Oh, and thanks for reading ;)
Still need to find a way to document this feature in a better way... do you think we could put it somewhere in the wiki?