This is it, the final beta release for Projectfork 2.2! As I've mentioned in the·previous beta 2 announcement, beta 3 is mostly about Joomla 1.6 compatibility issues. I'd appreciate it if you take some to test this beta on the latest Joomla 1.6 release and leave your feedback in the forum.

Beta 3 changelog

  • Fixed: Unable to copy projects
  • Fixed: Fatal error when trying to comment on a task/note
  • Fixed: Avatar not displaying user names when profile images are disabled in the config
  • Fixed: Dashboard calendar date bug
  • Fixed: Theme performance issues in the backend (hover-shadow effects have been removed)
  • Fixed: Unable to select Projectfork as menu item in the Joomla 1.6 Menu manager
  • Fixed: Save/Cancel buttons not working properly in Joomla 1.6 modal windows (needs testing!)
  • Updated: Projectfork ACL is now compatible with the new Joomla 1.6 ACL
  • Updated: Theme adjustments for Joomla 1.6
  • Updated: Demo process now works again
  • Added: Database optimization process
  • Added: Option to show/hide empty milestones in the task list (See task config)
  • Added: Section example package for developers (see com_projectfork/_dev)
  • Added: Akeeba Backup recommendation to upgrade splash-screen
  • Removed: Active link relative positioning which was causing issues
  • Removed: Active hover CSS3 box-shadows which were causing performance issues

Joomla 1.6

Projectfork 2.2 is functioning properly in Joomla 1.6 but I recommend using it in Joomla 1.5 until 1.6 goes stable. I haven't been able to investigate the new Joomla 1.6 ACL long enough to make a nice and comfortable integration. The way it works now is that for every group you create in Joomla, Projectfork will automatically create an equivalent global group and global access level. In order to add users to those groups, you'll have to use the Joomla account/group manager. In order to give permissions to the users in this group, you'll have to use the Projectfork group manager...it's quirky I know. Fortunately, I don't think you'll have to use global groups that much unless you really need a very complex user infrastructure.

Developers and translators

Beta 3 comes with a Section example package, which was missing in beta 2. The package contains a basic example on how you can create and distribute your own section including code examples and documentation. If you're interested in making your own Projectfork extension - maybe even sharing it with the community you should check it out! You'll find the package along with all the others under: "<joomla root>/administrator/components/com_projectfork/_dev"

If you're interested in translating Projectfork, please wait until the stable release! Chances are that we'll do some changes before the release and it may be hard for you to track them down and update your translation accordingly, leading to unexpected errors.

Up next

The Beta phase has progressed extremely smoothly with less bugs and community reports than I've anticipated. Because of this we'll rapidly move through the RC phase right to the stable release in the coming two weeks. Until then there's still a lot of work to do - mainly upgrading the extensions and the documentation. And of course I'll take care of any bugs that you may find.

Last modified on Friday, 15 October 2010 22:22
eaxs

eaxs

Tobias Kuhn

Projectfork Founder and Lead Programmer

Follow me on Twitter