Hi! I've been investigating a Views 3.0 issue and ran into what I think is probably going to be the solution: #1417126: Views filter by 'Workflow: current state' only works if exposed . However, this is a D7 issue and I really need this in Workflow 1.5 for D6 so I can make it work with Views 3.0.

Currently I get a Views error message: "No valid values found on filter: Workflow: Current state". I get this even after I've deleted the filter! Views won't allow me to save until I get past this error, I think.

Thanks!

Comments

Bastlynn’s picture

Patches for this will be more than welcome, else I will get to the backport soon as I can.

pbeakley’s picture

Sweet! Thanks for getting on this! :-)

leelooch’s picture

well, on 6.x-1.5, change the line 23 in includes/workflow_views_handler_filter_sid.inc

from :
$states[$wname] = workflow_get_states($wid);

to :
$states = workflow_get_states($wid);

this worked for me (seems like $this->value_options must be a flat array, not a multidimensional array), but as I have tested it minimally, feel free to make deeper tests on this change.

sorry for not providing a patch, I don't have git installed.

johnv’s picture

Component: Code » Views
johnv’s picture

Title: Views3.0 incompatibility: No valid values found on filter: Workflow: Current State » Error "No valid values found on filter: Workflow: Current State" using Views3
johnv’s picture

Title: Error "No valid values found on filter: Workflow: Current State" using Views3 » Error "No valid values found on filter: Workflow: Current State" using Views3 (D6)

Marking this explicitely as a D6 issue.

johnv’s picture

Issue summary: View changes

changed link to issue.

johnv’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

I wish there was a nicer way to clear the issue queue from 'D6-issues that are fixed in D7' then a "won't fix for D6."