When I create a new issue I can include the Project name and component.

If I edit the issue later, for instead to change the status, the project and component values are lost and even If I specifically include them in further editions this values are not saved.

CommentFileSizeAuthor
#8 project_namespace_hack_patch1.patch606 bytesmlncn
#8 project_namespace_hack_patch2.patch1.1 KBmlncn
#8 project_namespace_hack_patch3.patch11.68 KBmlncn
#8 project_namespace_hack_patch4.patch1.91 KBmlncn
#5 Módulos _ UGT en Ericsson.pdf63.92 KBJASH

Comments

drewish’s picture

drewish commented

i'd suggest giving 1.x-dev a try and see if it's still a problem there.

JASH’s picture

JASH commented

I have tried with 1.x-dev version and I found the same problem.

When I try to update the lost fields, I got an error message indicating "an illegal option".
The value of component field has been lost and the update operation fails.

JASH’s picture

JASH commented

I have upgrade again to 5.x-1.0 and now I'm getting a few more information on the error:

* warning: in_array(): Wrong datatype for second argument in .... /modules/project_issue/issue.inc on line 812.
* You have to specify a valid component.

Remember that the possible values of "component" are selected from a combo and I have even not changed the installation allowed values.

I hope it may help to trace the problem.

aclight’s picture

aclight commented
Status: Active » Postponed (maintainer needs more info)

I think that there's a chance you're running into the $node name space collisions, as discussed at http://drupal.org/node/98278

Can you give us a list of the optional core and user contributed you've got installed on your site.

JASH’s picture

JASH commented
StatusFileSize
new Módulos _ UGT en Ericsson.pdf63.92 KB

Please find enclosed a printout of the modules page.

Thanks in advance, Juan

aclight’s picture

aclight commented

@JASH: It's hard to say which, if any, of your modules might be causing the problem I linked to in #4 (if that's even the problem at all).

I actually just created a handbook page a few days ago with some instructions for troubleshooting project*. It's pretty difficult for us to fix a problem when we can't reproduce it. The handbook page is here: http://drupal.org/node/199367

If you want to go through that it may help you to isolate the problem. If you do use the instructions, please make comments on that handbook page if you have any suggestions, etc.

JASH’s picture

JASH commented

I have deactivate all possible modules (except the Drupal Core Reqeuired, Project and Project issue tracking) and I contine getting the same problem:

When I tried to reasign the project to the issue, the combo with potential components appear, I select one and when I submit the changes i got the error:

An illegal choice has been detected. Please contact the site administrator.

And the component combo is marked as erroneous.

I hope it helps..

mlncn’s picture

mlncn commented
Project: Project » Project issue tracking
Version: 5.x-1.0 » 5.x-1.1
Status: Postponed (maintainer needs more info) » Closed (duplicate)
StatusFileSize
new project_namespace_hack_patch4.patch1.91 KB
new project_namespace_hack_patch3.patch11.68 KB
new project_namespace_hack_patch2.patch1.1 KB
new project_namespace_hack_patch1.patch606 bytes

Confirmed that this is caused by the project* namespace bugs in $node referenced above by aclight.

Had the same problem on editing a: "An illegal choice has been detected. Please contact the site administrator." (That error is annoying even when one isn't the site administrator ;-) )

(I note that on Drupal.org editing issues is disabled entirely, at least for filers of the issue and for project administrators.)

After replacing all occurrences of $node->pid with $node->project_id it started working again! (Actually I replaced a good deal more, every instance of pid outside the database with project_id, because I'm stupid, or consistent, or both.)

(Sort of hoping it would also get rid of the minor re-create-a-path-alias every save bug, but it didn't).

My hack-patch will get your module running again without namespace conflicts, and because it doesn't mess with the database schema at all you'll be able to upgrade to the next release of this module that fixes this issue without worrying about the patch. So, it is attached until http://drupal.org/node/98278 gets committed.

benjamin, Agaric Design Collective

urgh, I didn't do anything right. The hack patch is in three pieces, the first will apply from within project module's directory with patch < project_namespace_hack_patch1.patch

The second and third from within the project_issue directory with patch < project_namespace_hack_patch2.patch and patch < project_namespace_hack_patch3.patch

Update: Typo in patch 3 caught by esteemed colleague Dan Hakimzadeh. Fixed now in attached files.

Update2: And with a patch for comment.inc, inside project_issue run patch < project_namespace_hack_patch4.patch

mlncn’s picture

mlncn commented

I think it's a separate issue, but the form to comment to update an issue only appears on a separate page (via "Follow up" link) and the regular comments (that can show on the same page) do not become endowed with project module magic.

And, I can't edit the comment on the test site like we can here on drupal.org