Recent posts in this topic
tylerhall:Sares,
Before you do any of this, make sure you backup your activeCollab directory and database. That said, adding time tracking to your existing install shouldn't be too difficult.
1) Assuming you haven't made any changes to your existing activeCollab code, just copy the code from the SVN branch over your existing install.
2) Next, you need to update your database by creating the table that stores the time tracking info and adding an extra field to one other table. Here's the SQL to create the table and make the modification:
http://basejumpr.com/activecollab/time.sql
You can paste that into a tool like phpMyAdmin or run it in MySQL directly. Once you do that, I *think* that should take care of things. Let me know if you run into any problems. You can email me at tyler AT sitening DOT com
Tyler, did you make any other improvements regarding the time tracking part, if so, are you willing to share your code?
I'll send you an email later today.
attiks:Tyler, did you make any other improvements regarding the time tracking part, if so, are you willing to share your code?
I'll send you an email later today.
I haven't committed any new time tracking changes since revision 344 on 1/22/07 at 14:00:17.
You can reach me at tyler@sitening.com
TylerHall,
With all thats going on at the moment (RE: aC going closed source) i was wondering what you guys were doing? Are you going to take over the 0.X branch and run with it perhaps as openCollab? As i think you are in a very good position to do so.
I am yet to try your code but will be doing so over the weekend. I'm hesitant to get too embedded with a app i know is about to die, but if i knew you were taking over the project i would go with it for sure (and donate + get my clients to donate).
Regards,
Drayen
With all thats going on at the moment (RE: aC going closed source) i was wondering what you guys were doing? Are you going to take over the 0.X branch and run with it perhaps as openCollab? As i think you are in a very good position to do so.
I am yet to try your code but will be doing so over the weekend. I'm hesitant to get too embedded with a app i know is about to die, but if i knew you were taking over the project i would go with it for sure (and donate + get my clients to donate).
Regards,
Drayen
Drayen,
We worked on Tyler's version and we just released a beta, see http://www.activecollab.com/forums/topic/1458/4/
We worked on Tyler's version and we just released a beta, see http://www.activecollab.com/forums/topic/1458/4/
conraddecker
on Mar 22. 2007. 1:25 pm
I've fallen in love with active collab and hate to see it taking such a drastic change. If anyone is looking to keep an open version of aC running I would be happy to be a part of it and donate what I can.
Just a thought.
Just a thought.
I also get the error mention above.
It doesn't seem to have any negative effect though. I can still see entered times and can still enter times. No idea what is going on.
The last big thing that happened is a corruption of the InnoDB tables (meaning all activeCollab data). Had to delete the DB and recreate it from a backup. Since then everything is working fine, but I get that warning/error message.
Notice: Undefined property: Project::$all_times in /home/babykuc7/public_html/activecollab/application/models/projects/Project.class.php on line 492
It doesn't seem to have any negative effect though. I can still see entered times and can still enter times. No idea what is going on.
The last big thing that happened is a corruption of the InnoDB tables (meaning all activeCollab data). Had to delete the DB and recreate it from a backup. Since then everything is working fine, but I get that warning/error message.
I can confirm the warning, the problem is the variable isn't declared, you can solve it by adding
private $all_times;
to the top of the class.
I'll add it to my todo list
Peter
private $all_times;
to the top of the class.
I'll add it to my todo list
Peter
private $all_times; was already in my Project.class.php. Must already be in your instructions somewhere because i didn't add that on my own.
Yep, with that variable added it works fine again without error message.
What I don't understand is why it worked before. I didn't change anything in the code.
What I don't understand is why it worked before. I didn't change anything in the code.
