I have a module that has a few Bulk Operations defined as default views.
Which is possible, IF my module code provides the standard operations settings for that. (I.e. calls _views_bulk_operations_set() / stores that setting in the vbo_settings table.)

For default views, the setting is stored by name instead of by ID. However,
* the 'name' column is 48 characters
* 28(!) of those are taken by VBO, because every(?) string in that table starts with 'views_bulk_operations_prefs_'
* that leaves 20 characters for the view names themselves
* my module name is 16 characters and I like naming default views after their owner module name (plus underscore) to prevent namespace collisions
* that leaves a measly 3 characters for the descriptive view names. (And time for me to figure out where things went wrong, when I had a longer view name.) I had to shorten the names in order for the default VBO-views to be operational.

It's not the end of the world. I'll survive. But maybe the name column can be lengthened?
(Alternatively you could change the naming scheme of your keys to 'vbo_prefs_' and provide an upgrade path. But I doubt it's worth the effort.)

So, do you agree with this assessment, and if so -- should I provide a patch for the .install or do you hack it in without one? :)

Comments

infojunkie’s picture

I agree. It's not nice to leave no room for the views name. I'll happily accept, review and eventually commit your patch :-)

infojunkie’s picture

Status: Active » Fixed

Fixed. Please wait until Drupal refreshes the 5.x-1.x-dev release with today's date, then try it and let me know!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.