Login or Register

RSS IconRecent posts in this topic

avatar Pro
gseto on Jun 20. 2008. 9:41 am
Hi Ilija,

Yeah, I have actually added the custom fields to the $project_data array within the edit_status() action. This worked for me with version 1.0.6 but now doesn't work with 1.1.2. I did a diff on that action as well and there doesn't seem to be any significant chance in the versions that I can see affecting this behavior. Is there any other way I can make it so these fields are not ignored if the status is unchanged?

Thanks,
Garry
avatar Pro
gseto on Jun 20. 2008. 9:43 am
Oh, I also forgot to mention that after the call to db_begin_work();, I added the following line to save the custom fields:

$this->active_project->setAttributes($project_data);

But it still doesn't seem to be saving the values.

Thanks,
Garry
avatar Staff
Ilija Studen on Jun 20. 2008. 11:37 am
Can you send me FTP parameters to support@a51dev.com and create me an account that I can use for testing? Is that an option?
activeCollab Team Member
avatar Pro
gseto on Jun 23. 2008. 8:11 am
Hi Ilija,

Sorry, unfortunately I don't think I can give out that access. Not sure if there's anything else we can try.

Thanks,
Garry
avatar Pro
gseto on Jun 23. 2008. 8:28 am
Hi Ilija,

Actually, I just found out a way to trigger the update. I noticed a $save variable that seems to rely on several status related methods. I'm not sure if this will have an adverse affect on anything else but adding the following line after the switch statement seems to work:

$save = $this->active_project->save();

I'll let you know if I run into any other problems as a result of this.

Thanks!
Garry

RSS IconRecent posts in this topic