After upgrading Drupal, the site's content editors report the MyWorkbench tabs for "Needs Review" and "Needs Final Approval" lists show what appear to be a lot of duplicates.

There will be anywhere from 3 to 11 lines listed for the same "Title", but they will list a different "Revised by", yet all have the same"Last Updated" time value. Plus we're certain not all the other Revised-by people listed edited the content (and there's no way they ~all~ edited at the exact same timestamp).

Also, the whole list used to be only the content needing review or final approval. Now it goes on for nine+ pages listing Last Updated times as far back as a year and three months ago (basically back to when the site was set up).

What got updated from their previous versions were the following:
Drupal (to 7.39)
Workbench (to 7.3-1.2)
Workbench Moderation (to 7.x-1.4)
Workbench State Access (to 7.x-1.0)
CTools (to 7.x-1.5)

fair disclosure: I've lurked here for a few months, but this is my first real forum posting. Be gentle please.

Comments

TMikeCurry’s picture

I checked the Apache Error Logs: No error lines generated for this.

I checked the Drupal Recent Log Messages: None related. And I can access the "Needs Review" and "Needs Final Approval" pages and no new messages come up in the 'Recent Log Messages'.

I have cleared the web browser cache and Drupal cache cleared. So I don't think it's something hanging around in cached css or javascript (if used).

I just have this feeling it's like a SQL thing. Maybe it's in the defined views for workbench moderation...?

num37’s picture

I just ran into this as well, so I figured I'd share what worked for me. In my case, there was a broken handler in the view, and I simply needed to revert the view to use what's in the current code/module.

On the admin/structure/views page, check to see if the Workbench Moderation: Content view is listed as "In code" or "Database overriding code". If it's "Database overriding code", then you'll want to revert the view (it's in the dropdown menu for the view, somewhere below "edit").

It's a good idea to save an export of the view first, especially if you have made any intentional modifications to the view in the past. You'll need to recreate them after, and having a "before" export to compare to an "after" export can make it easier to figure out what modifications you had in there.