activeCollab 2.2.1 Beta is Available for Download

1, 2, 3
This topic is locked, no new messages can be posted
avatar Ilija Studen Staff Jul 20. 2009. 3:27 pm #1
After first activeCollab 2.2 beta, here is the second one. It brings improved core stability, better authentication system and some fixes to Invoicing and Source modules. For details, please check release notes.

This version is available to everyone with valid upgrade and support package and you can download it from your activeCollab.com profile:



Resources:

* Installation instructions
* Upgrade instructions

Thank you for helping us test activeCollab 2.2!
Follow @activecollab and activeCollab on Facebook.
avatar michelangelo Pro Jul 21. 2009. 3:13 am #2
still got errors on adding a svn repo with over 500 revisions. finally went through and changed all the commit logs to not mention the word "ticket" and it finally imported. i've emailed you guys the crash reports
avatar michelangelo Pro Jul 21. 2009. 3:14 am #3
oh yeah, i was able to link users to the svn user names and the email updates when a commit is made is so much better. great update guys!
avatar Ilija Studen Staff Jul 21. 2009. 3:54 am #4
Hi michelangelo,

Thanks, we are glad to hear that you like the improvements. We'll check the crash report and see to have the problem fixed by the time final version is released.
Follow @activecollab and activeCollab on Facebook.
avatar Marc Pro Jul 23. 2009. 3:34 pm #5
Hello Ilija ::

Can the aC team forecast a date for when 2.2 will complete beta?

Thanks!
avatar andrewkol Pro Jul 23. 2009. 10:17 pm #6
I really love this beta, I just have one thing that I would really love to see in the near future: mercurial support. Yes, subversion is an awesome version control system, but Mercurial (hg) is just more awesome.

Also, regarding what Matt Robenolt said in a earlier forum post, why not make a commit hook that runs every time a commit is made, marking a repository to be polled in the next update, and not just polling all repos every x minutes
avatar Ilija Studen Staff Jul 24. 2009. 6:38 am #7
Hi Marc,

Sorry, we never post launch dates because we usually don't know them. Releases are launched when we feel they are ready to be used by everyone - rushing things or releasing earlier because of a post you made on the forum does not benefit anyone. It just creates stress and may result in poor and buggy release.

andrewkol:
Also, regarding what Matt Robenolt said in a earlier forum post, why not make a commit hook that runs every time a commit is made, marking a repository to be polled in the next update, and not just polling all repos every x minutes


Our goal is just to get SVN module out for people to use it. Commit hooks seamed like nice to have feature, but hardly essential, so we left it for the future.
Follow @activecollab and activeCollab on Facebook.
avatar fhagard Pro Aug 17. 2009. 11:40 am #8
The beta looks great except for one thing. It appears that the Safari bug with the traveling text box was reintroduced. Did I miss something?
avatar Ilija Studen Staff Aug 21. 2009. 5:48 am #9
Hi fhagard,

That bug is not present in the latest beta. If you still have, it's possible:

1. That you still have old JavaScript cached. Force refresh the page with Ctrl + F5 (on Windows) or Cmd + R (on Mac)
2. That some of the JavaScript and PHP files from upgrade instructions are not upgraded. Make sure that you have the latest files and force refresh the page (see #1)

Please let us know if that helped and if you need our assistance.
Follow @activecollab and activeCollab on Facebook.
avatar Tony Chilvers Aug 24. 2009. 9:35 am #10
Hi there,

Looking at the installation instructions it requires the file licence.php
This file is in use on our production site.
I have set up a sub domain that I was hoping to install this beta on so i could test the SVN module with a supplier of ours.
Can I just use the same licence file with the domain variable edited?

I didnt want to just go ahead and break our terms and conditions.

TC

Topic is locked

If you have something important to say about the issues discussed in this post please write at hi@a51dev.com.

or Go To Next Page