Frog CMS

The expectation is that a beta version of Frog 0.9.5 will be made available before mid February. Due to the large number of big changes in the Frog core system, we are planning to release 0.9.5. in at least three steps: Release 0.9.5 Beta – ... [More] This will allow users to help test for bugs. Release 0.9.5 RC1 – A Release Candidate is planned to make sure we don’t encounter anymore severe issues. Release 0.9.5 Final We would like to invite our users to help us test the beta release when the time comes and to log the issues in the issue list . As you can see, the changelog has grown considerably since version 0.9.4. We’ve taken the liberty to highlight some interesting items: Added MySQL port to install screen. Thanks gilles.doge – issue 107 Added new events – issue 94 Added site identifiers to login screens (both login.php and forgot.php) based on Admin screen title setting. Added front-end login feature similar to layout selector. (login required, not required, inherit) Added drag-to-copy feature for better multi-language support. Thanks tuupola. Added a new core plugin called skeleton to help out new plugin developers. Added translation template generator to help out translators with translating Frog core and plugins. Added Norwegian and Swedish core translations. Added updated Chinese translation. Removed split between frontend and backend. Added an ID to the “view this page” link so it can be styled. Fixed issue with filename lowercasing during upload of files. Thanks david – issue 113 Fixed previous()/next() functions to work for all levels. Thanks rid – issue 109 Fixed “Add child” tooltip for browsers not picking up the alt value of the icon. Fixed broken View Site link for TLDs starting with ‘a’ – issue 116 Fixed XHTML compatibility problem with Comment plugin. Fixed issue where only the last addJavascript was accepted. Updated readme.txt with requirements detail for MySQL server. Updated file_manager plugin translations to conform to new template. Updated comments in preparation for PHPDoc documentation. Renamed root dir text files to avoid name conflicts and accommodate Windows users. Renamed style.css into screen.css for more consistency with print.css in Normal layout. [Less]

As Frog’s release manager, I’d like to give you an idea of where Frog is heading. Split Frog In our roadmap, which is mostly up-to-date, we talk about release 0.9.5 as being “Split Frog”. The reason for this is: Frog is currently split in a ... [More] frontend and backend area for performance reasons. However, this has been causing us more and more problems lately. As such, we want to remove the split. The main big idea for Frog 0.9.5 was to remove the split and perform bugfixing. Apart from fixing any problems related to removing the split, we also have a number of other ideas: Add a skeleton plugin to core to help out plugin developers. [done] Add a translation template generator to help out translators with translating Frog core and plugins. [done] Prepare the core with more in-code comments to provide for PHPDoc generated documention. [done] Add frontend login. [done] Expand the number of events. A mechanism for content in multiple languages. Provide detailed textual upgrade instructions. Bug fixing. Further afield There are lots of ideas for the future of Frog. Here’s a number of them: We need to check that we have complete end-to-end UTF-8 support. Frog is already good at languages, but lets make sure we have covered everything. We would like to expand and improve upon the plugin API to give plugin developers more tools to mess about with Frog. Part of this will be a consistent set of events. Another part of this will be to allow for expanding on certain core functionalities. An example would be OpenID support through the plugin API. Another serious idea is to allow for (semi) automated upgrades and (semi) automated plugin installations. Conclusion The current main drive and focus for Frog is to fix bugs and remove the frontend / backend split. Once that is done, we will be able to start working towards a 1.0 release for Frog. I hope this post has given you a reasonable idea of the things that are going on with the Frog core system. Apart from all this, things are lively on the user contributed plugins side so lots going on there too! If you want to keep track of the goings-on in Frog, there are a couple of good resources: The Project Roadmap The Issue Tracker The Forum Yours sincerely, Martijn van der Kleijn, Frog release manager [Less]

It's great to see more and more Frog CMS powered sites popping up around the web. (We hope to have a gallery up-and-running in the not too distant future!) One thing that must help is the kind of notice Frog has received in articles like this one, where Frog heads the list of “top CMS alternatives”. Word is getting around! HT: band-x

The Frog development team is pleased to announce that we’ve released Frog 0.9.4 stable Please see the download page. List of changes in 0.9.4 stable Added updating.txt file Added function to allow plugin devs to add one or more javascript ... [More] file to the backend html for their plugin. (issue 35) Added auto-detected link to a plugin’s documentation page. Checks for existence of documentation() function in plugin’s controller (issue 33) Added auto-detected link to a plugin’s settings page. Checks for existence of settings() function in plugin’s controller (issue 32) Added Indonesian translation Added “View this page” link in the Edit page screen Added “Tag to use this snippet” in the Snippets tab Added en-messages.php.template to i18n directory of core to assist translators Added admin section option to choose default tab after login (issue 29) Added display of latest plugin version in Frog admin section Added option to admin screen: allow html in page title. (default: false) (issue 66) Added favicon Added option to Plugin::addController to allow for controller without displaying a tab Fixed lacking PNG support for IE6 (issue 64) Fixed bug allowing HTML code in page title, now filtered with Kses $values => $value in Page.childrenCount() Fixed security issue with DB username password in index.php Fixed incorrect return and if statement in DoPgsql.php Fixed accidental assignment bug in Framework.php (issue 43) Fixed bug where “Files” tab was accessible to users without roles. Now restricted to “administrator,developer,editor” (issue 42) Fixed bug where using permissions string as parameter to addController had no effect (issue 41) Fixed “s” echo for count in comment-each snippet of comment plugin Fixed Gravatar bug to display default user image. Updated all languages files to move file manager plugin translations to file manager plugin i18n directory Updated core plugin index.php files to make use of the new “latest” functionality Updated the comments plugin Updated Dutch translation Updated default Layout to find metadata from Edit.Page.Metadata tab Updated default Normal Layout to check for existence of keywords, otherwise use default strings Corrected the default RSS Feed, should now validate. Also added RSS subscription link tag to default Normal template. Modified the place of the “filter” input in Snippets Removed comments css code from admin.css Changed default footer snippet to read copyright Madebyfrog.com instead of Philworks.com Changed plugin list “from …” wording to “by …”. Updated Russian translation Typo corrections on dummy text for default installation Updating from version 0.9.3 For full details, please see the updating.txt file included in the download! Updating consists of a few seperate steps. When executed correctly, this method of upgrading will keep downtime to a minimum. Please READ CAREFULLY: Make a backup of your current Frog installation. Make a backup of your current Frog database. Create a temporary directory. We’ll use this to prepare the upgrade in. Unzip the Frog package into the temporary directory as if you would install into it. Remove the “public” directory and everything in it from the temporary directory. Remove the config.php and _.htaccess files from the temporary directory. Copy all the non-core plugin directories from ../frog/plugins to your temporary location’s ../frog/plugins directory. Execute the following two SQL statements on your database: INSERT INTO setting (name, value) VALUES ('default_tab', ''); INSERT INTO setting (name, value) VALUES ('allow_html_title', 'off'); Finally, execute the following steps (these actually upgrade the site): Copy all the files from the temporary directory to your installation’s root, replacing the old files. Check your site to see if the upgrade didn’t break anything. You’re done! For full details, please see the updating.txt file included in the download! [Less]

Today, the release date for Frog v0.9.4 has been set: September 29th, 2008 by 23:00 UTC 2 at the latest. (23:00 UTC 2 is the Europe/Amsterdam timezone)

The Frog development team is pleased to announce that we've released Frog 0.9.4 RC1 Please see the download page if you want to help us test RC1. About Release Candidates Most if not all stable releases of Frog will be preceded by one or more ... [More] "Release Candidates". A release candidate is a version of Frog which we feel could be stable enough for normal use, but which we want to keep testing first. Once any issues that came up during testing of an RC release have been corrected, a stable release will be made available. The intention of the RC releases is to give you, the user, a chance to help us test an upcoming release. List of changes in 0.9.4 RC1 Updated the comments plugin Added Indonesian translation Added "View this page" link in the Edit page screen Added "Tag to use this snippet" in the Snippets tab Fixed security issue with DB username password in index.php Removed comments css code from admin.css Updated default Layout to find metadata from Edit.Page.Metadata tab Changed default footer snippet to read copyright Madebyfrog.com instead of Philworks.com Fixed incorrect return and if statement in DoPgsql.php Fixed accidental assignment bug in Framework.php (issue 43) Corrected the default RSS Feed, should now validate. Also added RSS subscription link tag to default Normal template. Fixed bug where "Files" tab was accessible to users without roles. Now restricted to "administrator,developer,editor" (issue 42) Fixed bug where using permissions string as parameter to addController had no effect (issue 41) Added admin section option to choose default tab after login (issue 29) Added display of latest plugin version in Frog admin section Updated dutch translation Added en-messages.php.template to i18n directory of core to assist translators Fixed bug allowing HTML code in page title, now filtered with Kses [Less]

The new forum is up and running! You can now edit your post and have more control about monitoring. Hope everyone will like it!

The Frog development team is pleased to announce that we've decided Frog is nearing a new release: Frog version 0.9.4 Release Candidate 1 on Sunday 7th of September at the latest. About Release Candidates Starting with this release, most if not ... [More] all stable releases of Frog will be preceded by one or more "Release Candidates". A release candidate is a version of Frog which we feel could be stable enough for normal use, but which we want to keep testing first. Once any issues that came up during testing of an RC release have been corrected, a stable release will be made available. The intention of the RC releases is to give you, the user, a chance to help us test an upcoming release. About Release Schedules The Frog development team does not pre-plan new Frog releases. No release schedule will be made available. Once the development team feels a release is nearing completion, we will decide on a release date and announce it. This is the first of those announcements. [Less]

A security related patch has been made available for Frog version 0.9.3. Please find more details at the security patches page.

The major alteration to Frog CMS 0.9.3 was the removal of comments from the core to a plugin. With that complete, bugs stomped, and other enhancements and fixes in place, this has now been made the current release. As always, you can grab it from the ... [More] download page. With this release, Frog CMS is now available under the GNU Affero General Public License, which replaces the previous MIT license. See the license.txt file for further details. Thanks to all those who have helped with feedback, requests, encouragement, and most of all — by using Frog! [Less]