Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Steps to reproduce:
- Install Drupal core + the token_filter module + features + dependencies.
- Create a feature and add the input format 'Full HTML'.
- Enable the feature.
- Edit input format 'Full HTML' and enable 'Replace tokens'. Save the input format.
- Visit the features page and verify status. Nothing should show as overridden
- Now apply patch.
- Reload the features page: should notice the feature now is in overridden state.
Core 7.38
Features 2.6
Token filter 7.x HEAD
Comment | File | Size | Author |
---|---|---|---|
#6 | token_filter-filter_name-2528596-6.patch | 1.05 KB | darvanen |
#1 | token-filter-fix-features-support-1.patch | 546 bytes | Rob C |
Comments
Comment #1
Rob C CreditAttribution: Rob C commentedComment #2
Dave ReidVery confused about why this would be necessary.
Comment #3
Rob C CreditAttribution: Rob C commentedDave, 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.
Comment #4
Rob C CreditAttribution: Rob C commented(Everything else works fine, media markup, wysiwyg_filter, etc, etc, but this option wasn't exported by features.)
Comment #5
flux423Thank 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?
Comment #6
darvanenI did just find this in the documentation for hook_filter_info:
Here's a patch for review that should meet the requirements.