Postponed (maintainer needs more info)
Project:
Input Formats
Version:
6.x-1.0-beta5
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2010 at 19:58 UTC
Updated:
31 Aug 2010 at 18:45 UTC
Comments
Comment #1
dagmarI'm not sure to understand your point. This is what I can do: provide a hook to modify an input_format when it is loaded from code before caching.
Input formats cannot be disabled/enabled since there is a lot of code (from Drupal core) that doesn't contemplate that an input format can be disabled. If exists, it is available to be used.
Maybe if you provide a real use case for this feature we can see if this can be achieve or not.
Thanks
Comment #2
Grayside commentedLet me ask my question more clearly:
I have a WYSIWYG feature. It uses this module to create a new Input Format. We also have a feature based on the Inline module. I would like the input filter created by the Inline module to automatically be added to our WYSIWYG's input format.
Because the Input Filter feature comes along later, I cannot rely on the standard import of the WYSIWYG feature to carry it in. (And do not want to mandate a feature reversion to pull the input filter in via a features import pipe alter of some sort.)
Therefore, this requires a sort of API call that is not part of the core architecture of the Input Formats API or the core filter.module. I see this as a part of the core mission of Input Formats to expedite the creation of input format exportables and features.
Here is what I am thinking, for my specific use case:
This whole thing amounts to being able to turn on an Input Filter feature that enhances an Input Format feature.