Actions disappearing: op field in drupal_trigger_assignement is to short
tegizio - May 12, 2009 - 16:36
| Project: | Workflow |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I am having a strange issue with Workflow 1.1 for Drupal 6. On only the Workflow tab of the Triggers page the Actions assigned to any state change disappear after they are assigned. I know they are still there because if I attempt to reassign the same action I get a duplicate entry warning. I have been using Workflow with Drupal 5 for some time without a problem but this issue will now allow me to use Workflow with Drupal 6 because I am unable to unassign or review what actions are associated with each workflow trigger.
Any assistance would be greatly appreciated.
#1
I am having a similar problem. When I try to assign an action to a trigger in the Workflow tab the action is not displayed on the trigger/workflow page.
user warning: Duplicate entry 'workflow-workflow-articulation_agreement--9' for key 1 query: INSERT INTO trigger_assignments values ('workflow', 'workflow-articulation_agreement-17', '9', 1) in /var/www/articulation.statecenter.com/modules/trigger/trigger.admin.inc on line 206.
#2
I have been working on this issue for a couple of days and I think I know why the Trigger assignments are not showing up on the trigger/workflow page. When I assign an action to a trigger it is not displayed on the page but it does go into the database table "trigger_assignments". After trying this on a clean install and using the page content type I noticed that "op" column has the following syntax "workflow-page-1", "workflow-page-2", and so on. When I went back to my dev site site I saw that my "trigger_assignments" table column "op" was missing the number. Here is what my fields looked like "workflow-articulation_agreement-". The trailing number is cut off. This also explains another problem I was having with the triggers. All of my workflow triggers were being performed at once irregardless to the workflow state transition.
So, it appears the issue is in the length of your machine-readable name for your content type. Hopefully this is an easy fix for the developer. In the mean time you can change the machine name of your content types.
#3
See also http://drupal.org/node/309919
#4
#294386: op field in drupal_trigger_assignments needs to be longer to support content types with long names
#5
#6
#2 "In the mean time you can change the machine name of your content types." I change the content type machine name but the old name is stile used..
#7
the interface work great and reflect the status of the DB...