Settings not exported with views (particularly relevant for features packages) [#980168]

It seems that the view page/block-specific settings under "Use AJAX" might not be handled in the normal view-sy plugin way, as they're not saved with a view, nor is the dependency on views_flag_refresh enforced during feature package creation. This is in juxtaposition to the views_export submodule that comes with views_bonus modules, which is also a plugin, but whose settings are exported with the view.

I've never played around with views plugins, so unfortunately I'm not much use for advice! Sorry.

Wonderful module, by the way! :)

Comments

Comment #1

crea commented 23 November 2011 at 13:24

If you look at $view->export() function it uses option_definition() method and iterates over defined options. Additional options this module uses are not defined there, so they are not exported. It probably requires additional plugin to declare new options as own, and to export them in a view. During the brief research I wasn't able to find a way to alter default option definition in Views 2 (outside, without new plugin). Maybe it's possible in Views 3.
Another way to fix this is to export module settings in variables.

Comment #2

samerali commented 24 November 2011 at 19:04

I had to use this function to force the settings always enabled (even if it's not enabled on the views settings after feature enable/revert):

function hook_views_pre_view(&$view, &$display_id, &$args){
	if($view->name == $viewname){
		$view->display_handler->set_option("use_ajax_flags",array($flagname => $flagname));
		$view->display_handler->set_option("use_ajax_flags_widget","throbber");
	}
}