Components field doesn't save to database correctly

Confirmed here, too. It could be that the components aren't saving properly when a project is edited, as my existing projects' components load fine... but once edited, they are lost. The submit issue form after editing a project does not display any components, usually resulting in not being able to submit a new issue, as component is a required field.

Changing to correct version.

Haven't looked into this one any further yet...

Seems the _update hook isn't saving the components correctly. Attached patch seems to fix, but needs review and proper testing.

Nope - doesn't quite fix. Fields seem to be saved correctly, but aren't being represented in the option tag properly:

<option value="Content
">Content
</option><option value="User interface
">User interface
</option><option value="Hosting
">Hosting
</option><option value="Documentation
">Documentation
</option><option value="Financial
">Financial
</option><option value="Miscellaneous">Miscellaneous</option></select>
</div>

The line break breaks being able to submit to any of the above components bar 'Miscellaneous'.

Another shot. It seems to work here, but I'm curious as to why ...update needs this and ..._insert doesn't.

Still an issue with latest HEAD - can anyone confirm?

This is still an issue with 4.6.0 release. Is there a patch for 4.6.0 or do I need to start over from CVS and patch from there?

A new patch, adapted from this one from 'must'.

Ooops.

Fixes creation of new issues, but doesn't fix follow ups for current issues.

Patch works great, fixes all known issues when creating issues with project module, RTC!

Thanks for the patch, this issue definitely needs fixing.

I'm wondering if this complex handling is needed. How do we handle the question of converting multi-line lists into arrays in other cases? I'm thinking that we do this in the profile.module. Here are some potentially relevant lines:

        $values = split("[,\n\r]", $value);
        $fields = array();
        foreach ($values as $value) {
          if ($value = trim($value)) {
            $fields[] = $browse ? l($value, "profile/". drupal_urlencode($field->name) ."/". drupal_urlencode($value)) : check_plain($value);
          }
        }
        return implode(', ', $fields);

Can we do the same here?

Hi there,

Just wondering... is patch3 still required or has this patch been integrated into the CVS version of the projects module? I assume it is still required.

Many thanks,
Jack

OK, I just tried applying patch 3 against version 1.140 of issues.inc and I've also tried updating to the very latests CVS code but I'm afraid neither fixed the problem described here:

http://drupal.org/node/44572

Thanks,
Jack

I had the same problem. It seems to be resolved by issue_3.patch .
I need more tests to be sure about it.
(if I wont write more bug reports for project, then it is OK)
Project on 4.7 seems to be compatibile with 4.7.

Is there any news about whether or not this patch will be entered into the CVS repository for the Project module?

Thanks,
Jack

Is it possible that this issue has already been fixed? Patch3 is for 1.140, but issue.inc is now 1.142 (2006/01/16).

/me asking 'cause I just have tested this module...

- created a project.
- created an issue, selecting one of the existing components.
- viewed issue, looks good.
- edited project, adding a new component to the list.
- edited issue changing the component, selecting the one that I just created.
- viewed issue, looks good.

It all worked for me.

The problem was that validation wasn't being called just before the node was saved (presumably this is a change in the order of calls) so the components string wasn't being converted into an array (as this happened in project_project_validate()). I've changed this to do call the conversion in project_project_insert() and project_project_update(), which appears to fix the issue. Fix applied.

Hi there,

I've just tried installing the most recent code from the CVS but I'm afraid I still can't add a feature request / bug report to a project because I can't select any projects.

I have the taxonomy module installed (I need it). Does the taxonomy module still break the project module (I would try disabling the taxonomy module but I'm afraid I can't because it gets used so much).

Many thanks,
Jack

Can't reproduce this error, and it doesn't appear to be necessarily related to this issue.

Make sure you're creating a new project to submit issues on, as your existing data may have errors. If you still have problems, submit a separate detailed support request.