Coming from #2078807: Create a separate 'Project Ownership' issue queue. New issue queue for project ownership requests exists: https://drupal.org/project/projectownership and we need to move all old/current issues there.
Patch coming soon.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2256249-4-Move-project-ownership-issues.patch | 1.21 KB | tvn |
Comments
Comment #1
tvn commentedPatch for hook_update_n attached. Tested on sprint7 and sprint8 dev sites.
The reason for INNER JOIN node in the query of the first patch is orphaned data in the dev site database. There were lots of orphaned rows in the field_data tables, which had no corresponding rows in the node table, node_load was failing as a result and I wasn't able to test the patch.
The second attached patch has no INNER JOIN node in case you prefer to use this one on production.
Can we prevent email notifications from going out while running this update? E.g. by running it from the 'System Message' user.
Comment #2
drummhttp://cgit.drupalcode.org/project_issue/tree/project_issue.module#n309 has examples.
Use
nodechanges_comment_attributesto specify no email.Use
nodechanges_uidto make it come from System Message, who isvariable_get('project_issue_followup_user', 0).Comment #3
drummThe
JOINis okay in production. I'd rather run tested code than anything else.Finding the nodes with
EntityFieldQuerywould be ideal, but not required for an update function that will never run more than once.Comment #4
tvn commentedAdded nodechanges stuff to specify System Message user and no email.
Tested on https://sprint1-drupal.redesign.devdrupal.org/project/issues/projectowne...
e.g. https://sprint1-drupal.redesign.devdrupal.org/node/2220433
Issue update seem to be working. I was not able to test no email part however, since we now send issue queue notifications via Jenkins job.
Comment #6
drummCommitted & deployed