Not sure if this belongs in the VBO or in Entityforms queue.
For some reason, only Entityform fields are appearing in my "Display Values" list, within a bulk operation field. All other content type fields are missing completely from this list. I can see them when I perform a bulk operation, but editing them does not have any effect.
Initially I thought this might be permissions-related, and so I reversed all changes made using Field Permissions (had only restricted one or two fields), rebuilt permissions at admin/reports/status/rebuild and then I double-checked permissions at admin/people/permissions. I'm totally baffled and have no idea where to continue troubleshooting beyond blindly groping around in a copy of the database.
Ctools 7.x-1.6 (happened with 7.x-1.5 as well)
Entityforms 7.x-2.0-rc1
Within a view display, when "All" is selected in the operations field, I can perform any bulk operation, but a "Modify entity values" operation that involves any field that is not associated with one of the entityforms I created will silently fail. No errors or warnings. The fields I want to modify are visible on the second operations page in the "Fields for type [my content type name]", but checking the field's box, making a change and executing the change has no effect. It looks like it runs, but nothing happens, and no error messages are thrown.
Comments
Comment #1
silurius commentedComment #2
silurius commentedI finally found the source!
By disabling the Entityform Notifications submodule, VBO was once again able to "see" fields not created for an Entityform Type. The fields are listed in the VBO field in my view display, and my edits are also sticking now.
The interesting thing was, I hadn't really played around with Entityform Notifications yet. It appears that one of the four canned components it ships with has a default permission that conflicts with VBO in some way.
At this point I think I've done all I can with this issue, but I welcome and encourage anyone else who has more time to pinpoint the exact cause and, ideally, propose a patch for either module.
Comment #3
silurius commentedUpdating issue title to more accurately reflect the likely root cause.
Comment #4
joelpittetI'm helping maintain both VBO and entityform, could you give me the minimum combo of things to reproduce this bug?
Maybe it's been resolved in the latest releases?