Because of

  function option_definition() {
    $options = parent::option_definition();
    $options['skip_blank'] = array('default' => FALSE);
    // Field element_type and classes cannot be defined in the options
    // definition because the field handlers are not attached when the option
    // defaults are set up in the object's init() method.
    return $options;
  }

the settings are not going into the export. The only possiblity to fix it, is to have semantic_html defined in option_definition. Sure thats a easy fix :)

CommentFileSizeAuthor
semantic_views-fix_export.patch842 bytesdawehner

Comments

Anonymous’s picture

Wow. That's great. I haven't even touched Views 3 yet. Are you able to use the Semantic Views module with Views 3 with only this change? No other issues?

I will test your patch as soon as I can. If you can elaborate on the completeness of this patch, it would help others who confront the same problem in case I don't get to review it quickly.

dawehner’s picture

i'm not sure, whether its complete, i will have a look....

it looks fine. i tested a bit, and it worked as expected.

PS: merlinofchaos suggested to include this module into views core.

BenK’s picture

Cool! Subscribing....

Anonymous’s picture

Status: Needs review » Fixed

If there are new Views 3 integration problems, I'm happy to be more brazen in the development branch now that there's a release. Please open new issues for specific tasks.

Status: Fixed » Closed (fixed)

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