When bringing up the array picker, draft items are appearing as well as the approved items. Users are selecting the draft items by mistake and very bad things are happening.
When searching through core/packages/farcry/formtools.cfc getRecordSet() function, there is a variable being set called bHasStatus if the specific content type has it (and sets it to true), however it is NEVER being referenced in any of the WHERE clauses.
One suggestion to fix it is to add it to the where clause in core/webskin/fourq/displayLibrary.cfm where it calls getRecordset(). In p600 its currently on line 107.
We would have changed it in core ourselves, but were wondering if we should allow draft items if they are draft only (meaning that there is no approved yet) since when that item is approved for the first time it will keep the same objectId. If we did go that route, should we then somehow display to the user in the array picker that this is a draft item? ie. "myLabel (draft)".
Critical
When bringing up the array picker, draft items are appearing as well as the approved items. Users are selecting the draft items by mistake and very bad things are happening.
When searching through core/packages/farcry/formtools.cfc getRecordSet() function, there is a variable being set called bHasStatus if the specific content type has it (and sets it to true), however it is NEVER being referenced in any of the WHERE clauses.
One suggestion to fix it is to add it to the where clause in core/webskin/fourq/displayLibrary.cfm where it calls getRecordset(). In p600 its currently on line 107.
We would have changed it in core ourselves, but were wondering if we should allow draft items if they are draft only (meaning that there is no approved yet) since when that item is approved for the first time it will keep the same objectId. If we did go that route, should we then somehow display to the user in the array picker that this is a draft item? ie. "myLabel (draft)".