Why 3.0 and not 2.2?
When we began our work on the new version early this year, we didn't have as many framework changes in mind as we see them today. This release was initially planned as a minor upgrade. But the more we worked on it, the more core changes were made and we eventually ended up rewriting most parts of the system for multiple reasons. One beeing the development of Joomla 1.6 with it's updated ACL and the change over to PHP 5. Other reasons were performance issues on large sites and the difficult maintenance of Projectfork extensions.
We didn't realize - until now - that all these changes are pretty significant and that this isn't a simple minor upgrade. None of the Projectfork 2.1 extensions are compatible with this new version and a "2.2" would suggest that the extensions should be compatible - at least to a degree. A "3.0" version however, does the massive changes we've done justice and makes it clear for everyone that extensions from older versions aren't compatible.
It's usable!
For starters - You may use the RC on production sites. Support, patches and updates will be provided for this release :) If you plan on upgrading your 2.1 install, please wait until the actual stable release next week! We'll have a full upgrade guide and Projectfork 3.0 extension updates ready by that time.
Changelog
- Fixed: Group permissions not taking child permissions into account upon saving/updating
- Fixed: Access check not working properly when permission requires author parameter
- Fixed: "Force join" not working in users section
- Fixed: Project accept/deny invitation links in email body not working
- Fixed: Empty or disabled profile fields are now hidden
- Fixed: Dashboard tasks panel now visibile only when logged in
- Fixed: All links in the cp_welcome panel now adhere to permission settings
- Fixed: "Score" field in section permission settings was too large. Set size to 5
- Fixed: Updating/deleting note comment caused fatal error
- Fixed: Calendar prev/next buttons not working when SEF enabled
- Fixed: "Back"-link on calendar edit form had a bad date, causing error messages on the overview page
- Fixed: Possible SQL error when viewing task list
- Fixed: JCE content editor padding and width
- Added: Install panel to dashboard
- Added: Installer now supports update sequences for both extensions and core updates
- Added: Projectfork updates can now be installed using the Projectfork installer
- Added: "Core" info box to core extensions in the config
- Added: Core extensions can no longer be removed (only disabled)
- Added: Language example package to dev examples
- Updated: Weblinks panel with new links
- Updated: Moved all theme icons to sprite(s) for improved performance
- Updated: Theme icon positions
- Updated: Theme CSS
- Updated: Language files with new strings for installer feedback messages
- Updated: Projectfork example data option re-added for the install
- Updated: Wizards have been slightly adjusted
- Updated: Adjusted permission access behavior: Project admins now ignore the Author parameter
- Removed: Deprecated theme icons
A Shiny New Icon
In celebration of this milestone, we had a brand new web application icon design for Projecfork. It brings together all the elements of Projectfork all in one unique statement. You'll be seeing this on the homepage soon. Now go ahead and check out the RC. [Download Projectfork 3.0 RC 2]
