Work tracker for Open Atrium 2.0!

I worked with the maintainer of comment_alter and now it's no longer necessary to apply any patches!

Also, there has been an -alpha1 release of the Work tracker:

http://drupal.org/project/oa_worktracker

Please test it out and let me know what you think!

Regards,
David.

OK, I found the issue. Please disregard. I had altered the form_alter variables trying to upgrade from 6 to 7 and removed the ampersand from the &$form, &$form_state, $form_id arguments in the function.

Thanks

Hi I am working on customizing worktracker and have run into an issue with the drupal_form_alter. I seem to be unable to set the form options and am wondering the best method for doing so. The only place I see them in the $form is within the field array under und - #options.

In our previous casetracker custom module, we used the following code to do so:

unset($form['casetracker']['case_status_id']['#options']);
$form['casetracker']['case_status_id']['#options'][101] = 'Pending';
$form['casetracker']['case_status_id']['#options'][17] = 'Approved';
$form['casetracker']['case_status_id']['#options'][102] = 'Not Approved';
$form['casetracker']['case_status_id']['#options'][59] = 'Cancelled';

This worked well, however, when I use it on the field in the form, I am able to see the options when I dpm the form, but the actual select list only has the settings in the content field. I have heard that there is an issue with drupal_form_alter regarding the order in which the modules are called. Additionally, I have read that we now have split fields with a fieldbase (which your module uses) and an instance and I am not sure I am looking at the right thing. Do you know if one of these issues could be the problem, or am I missing something else? Any help would be appreciated.

Thanks David for the info. I am looking into using features_override. My main idea for doing everything in our module is to contain it so that I can see exactly what is going on. My background is in C and databases and I have a tendency to want everything in a neat compact package. I am relatively new to Drupal and am attempting to revise an existing custom module that overrode casetracker in Atrium 1.x. We also do considerable workflow manipulation within this module using the hook_form_alter and I am trying to expand on that a bit.

So, basically, if I use features_override, I can use the UI to make changes and then it will output code that will do it for us in the future. Is this correct? If so, this may be a better way about it than how I am doing it now. I would still need to use code to manage the workflow, but altering the options and fields in the UI is relatively simple.

Thanks

Hollye

David,

I have been successful so far with the override module and believe it will help immensely. However, I have encountered something that you may be able to help me with. I have searched and searched to find a method and all I get is how to do it in code. I need to do it in the interface first.

I am trying to use an entity reference view to limit selections in a field and am able to pass a verbose number to the contextual filter and have it return the correct nodes. I need to pass the value of an integer list field in the same add form to the view arguments and have tried almost every form that I can think of, ie. %node/add/oa_work_tracker/my_field_name, etc Do you have any idea how to pass a field value through content field view argument?

Thanks;
Hollye

EntityMetadataWrapperException: Unknown data property og_group_ref__og_membership. in EntityStructureWrapper->getPropertyInfo() (line 339 of C:\wamp\www\open\profiles\openatrium\modules\contrib\entity\includes\entity.wrapper.inc).

Tasks seem to only have a due date and no start date. I suspect that this was designed as a simple tracker and not a PM system.

Also there is no planned versus actual dates for start and end.

I suppose these can be added as fields but there is some inherent functionality that is implied when comparing actuals to planned.

Maybe i need another module?

Thanks
Steve