The second beta version of Projectfork is now available for public testing. We've added a few new features, fixed many bugs found in the first beta and worked around some installation problems on shared hosts/slow servers.
Seems like the previous patch caused some problems with the comments function and the task list. 2.0.12 should clean up the mess, sorry guys! On a side-note: A new 2.1 beta version will be available soon for testing :)
Finally, the first Projectfork 2.1 beta is now ready for download! Kyle and I spent lots of time improving and adding features to the new version and we think that we are now ready for further community input.
This is a pure security release and probably the last patch for the Projectfork 2.0.x series. Everyone should make sure to update to this version as soon as possible.
There was a simple exploit which allowed viewing and editing of other projects tasks and eventually critical information. However, this was only possible under certain curcumstances.
I haven't really reported any progress so far. And I guess everyone is wondering about what is going on behind the scenes. Well, I've made some very good progress and added a lot of new features and minor improvements. Kyle and I are currently struggling with the new design and we're still experimenting with that, collecting ideas etc.
I hope to present to you a first test release this weekend, stay tuned :)
And another small update to address the following issues:
- Fixed: missing Itemid when selecting project workspace
- Fixed: board notification being sent also to replying person
- Fixed: possible SQL error in cp events panel
- Fixed: file upload not sanitized, causing download problems
- Fixed: File downloads corrupted
As you probably know by now, Projectfork 2.1 is in development and I have all sorts of new features and enhancements planned. Having all this is new stuff is certainly nice, but what I really want to achieve is a "better" Projectfork in terms of usability. So I might have to turn a few things into another direction, tweak features here and there to get it right. And this is where I ask you: What is the worst part about Projectfork?
Please take a moment to place your vote and leave an additional comment about what you dislike about the current system. I am prepared for heavy (productive) criticism :-)
I've made a huge database cheat sheet for everyone who is trying to figure out where all his data is actually stored in the database. I hope you find it useful :)
So, here it is...the anticipated feature list for the next version of Projectfork! I'm not listing every minor detail that will be adjusted/added, like: "Move button from x to postion y" etc. Tons of suggestions have been made and you'll find many of them in the list, more or less exact as they were suggested.
There are also some suggestions and ideas in the list that would be nice to have, but are not given any priority and may not make it into the release. Suggestions that are not in the list may come in a later version or will not pursued at all because they may not fit into the big picture.
I am estimating about 2 months of development for Projectfork 2.1 with frequent test-releases for you to check out. In fact, development has already started and the first test-version will be available next month!
I have published a new developer tutorial with basic code snippets and examples on how to work with the Projectfork framework. I hope you'll find it useful and create some new extensions with that knowledge :)
If you have any questions regarding the code or need further explanation, please ask in the forum and I will try to explain more in-depth.