Closed (fixed)
Project:
Maestro
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2012 at 22:30 UTC
Updated:
27 May 2014 at 19:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Hamid.D commentedI have the same problem
Comment #2
_randy commentedSo I gather you are setting a process variable from a content type task's field value?
In order to diagnose this issue, there would have to be some debugging done to determine what the field_data_column is being set to as well as what the $data array is being set to.
If you are able to dsm or log the values of those data elements are, that would help.
Also, I believe we use this functionality in one of our test flows. Are you able to run through the test flows to ensure this does indeed fail (or work)?
Comment #3
_randy commentedI can't seem to reproduce the issue. reopen if this is still happening.
Comment #4
andrii-severynenko commentedIn maestro.module in function content_type_task_maestro_set_process_variable_logic
Before line:
$retval = $data['#items'][0][$field_data_column];add this:
Comment #5
larskleiner commentedI get this notice when I try to set a Maestro variable from a content type field value (a user entity reference field).
$dataon line 1420 of maestro.module just returns an empty array.Attached the patch for #4 which seems to fix this.
Comment #6
larskleiner commentedI get below warning with patch #5, attached patch should fix it.
Comment #7
_randy commentedLast patch looks Ok. Will commit.
Comment #8
_randy commentedCommitted.