After upgrading WM from 1.3 to 1.4, I'm getting "Missing handler: workbench_moderation_node_history current filter" warnings all over the place.

I also have a view where a filter says "Handler broken or missing (=1)" which has become very slow (and due to an unrelated proxy server issue makes the page go 504 gateway timeout).
When editing the filter, it also says "The handler for this item is broken or missing and cannot be used. (...) enable the module or remove the filter." (roughly translated from dutch).

Comments

MrSasquatch’s picture

MrSasquatch CreditAttribution: MrSasquatch commented

I am also having this problem. An additional side effect is, if I click on the "Needs Review" tab under "My Workbench," I see all my content, whereas I should only be seeing the content that has a moderation state of "Needs Review." The column for "Moderation State" says "Needs Review" for every node that is listed in this view, but if I click through to the node, I see that the node is in fact some other state, like "Published."

MrSasquatch’s picture

MrSasquatch CreditAttribution: MrSasquatch commented
Priority: Normal » Major

I am updating the status of this issue to "major" because it is seriously affecting our workflows for visitor-generated content, and I am under a lot of pressure to fix this.

pkantor’s picture

pkantor CreditAttribution: pkantor commented

This is caused by the change the field from "current" to "is_current" in the table.

Removing the broken handler and re-adding in the "Current" filter in the View fixed this for me.

Probably a pain if you have more than a few Views to fix though.

scareyclott’s picture

scareyclott CreditAttribution: scareyclott commented

bit of a newbie

#3 works but what a pain having to go through and change all the views.

Took a few days to work out it was this module and not Views itself then get a previous version working to identify the missing handler (then found this thread)
thanks pkantor

MrSasquatch’s picture

MrSasquatch CreditAttribution: MrSasquatch commented

Thanks, pkantor! Since you're so awesome, would you do me a kindness and look at this other workbench issue?

https://www.drupal.org/node/2408199

I would be happy to pay you, or anybody, to take a look at this. Please help.

Thanks!

pkantor’s picture

pkantor CreditAttribution: pkantor commented

Alas, HardTimes, I have a 40 item JIRA backlog of things that need doing on my own site, and about half of them are major projects.

Though is there any reason you cannot edit the View (/admin/structure/views/view/workbench_recent_content/edit) to filter by content type directly with "Content: Type"?

Perhaps not optimal, since it is a manual solution, but does keep them out of user's eyes, and if it is a security issue, then it may be better to have a specific filter for it anyway.

MrSasquatch’s picture

MrSasquatch CreditAttribution: MrSasquatch commented

But pkantor, I thought you could just click the "easy button!" :) Okay, I was going to resort to that. (i.e. filtering by content type) It just bothered me that that is necessary because we used to not have this problem. In the beginning, the only stuff that showed up under the workbench views were content types that were controlled by Workbench Access.

On a somewhat related note... Since I installed Workbench (Access and Moderation) 2 years ago, are there updates to the views that I am not enjoying because I have "the old views?" If so, is there an elegant way for me to update to the latest views for Workbench Access/Moderation?

jlyon1515’s picture

jlyon1515 CreditAttribution: jlyon1515 commented

pkantor, you are an absolute lifesaver! I have a site that is only edited yearly, and there are 3 revision states for pages. All of the views were broken and I couldn't figure out what. #3 worked perfectly.

Poindexterous’s picture

Poindexterous CreditAttribution: Poindexterous commented

@pkantor: Thank you! This worked for me also, I had the same problem. Our recent module update seemed to break our workbench related views, this was one of the problems.

I also noticed that the field and filter relationships for workbench related items in the views had their contextual relationship to the node removed. While I didn't have to remove and re-add them, I did have to reassign the relationships back to node to restore the views back to normal.