Steps to reproduce:

  1. Install Drupal core + the token_filter module + features + dependencies.
  2. Create a feature and add the input format 'Full HTML'.
  3. Enable the feature.
  4. Edit input format 'Full HTML' and enable 'Replace tokens'. Save the input format.
  5. Visit the features page and verify status. Nothing should show as overridden
  6. Now apply patch.
  7. Reload the features page: should notice the feature now is in overridden state.

Core 7.38
Features 2.6
Token filter 7.x HEAD

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Rob C’s picture

FileSize
546 bytes
Dave Reid’s picture

Very confused about why this would be necessary.

Rob C’s picture

Dave, i can't seem to export the setting to features without this change with these versions. I tried and tried again and then changed this, and it worked.

Rob C’s picture

(Everything else works fine, media markup, wysiwyg_filter, etc, etc, but this option wasn't exported by features.)

flux423’s picture

Thank you @rob-c for the patch. I'm still having a similar issue.

I've been trying to set the 'Replace Token' value in a strongarm or default_config setting. The patch applies cleanly but i'm not able to wrap up this setting in a feature.

I thought that I would be able to add something like the code below to the featurename.features.filter.inc file in the $formats['wysiwyg_text'] = array();

'filter_tokens' => array('weight' => -45, 'status' => 0, 'settings' => array(),),

Thoughts on how to resolve?

darvanen’s picture

I did just find this in the documentation for hook_filter_info:

An associative array of filters, whose keys are internal filter names, which should be unique and therefore prefixed with the name of the module.

Here's a patch for review that should meet the requirements.