Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Under my installation, I created a new Input Filter, and using the filterbynodetype module, I designated a content type to use that new filter.
The WYSIWYG module is not detecting myconfiguration, because this evaluates to false:
isset($element['format']['guidelines'])
However, $element['guidelines_link'] does exist.
So I changed these two lines adding "|| isset($element['guidelines_link'])" and it seems to work properly:
line 94:
if ((isset($element['#type']) && $element['#type'] == 'fieldset') || isset($element['format']['guidelines']) || isset($element['guidelines_link'])) {
line 139:
if (isset($element['format']['guidelines']) || isset($element['guidelines_link'])) {
Perhaps this is not the correct solution, it just worked for me.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | filterbynodetype-DRUPAL-6--1.form-structure.patch | 2.72 KB | sun |
Comments
Comment #1
janusman commentedMissed part of the title.
Comment #2
sun$element['guidelines_link']does not conform to Drupal core's form structure:http://api.drupal.org/api/function/filter_form/6
http://api.drupal.org/api/function/theme_filter_tips_more_info/6
http://api.drupal.org/api/function/theme_filter_tips/6
If filterbynodetype alters the form structure, it should make ensure that the resulting structure equals the default output of filter_form().
Please note that this bug only appears when the available input formats are reduced to only one input format.
Comment #3
sunThis works from my testing.
Comment #4
janusman commentedTested; marking this as RTBC.
Comment #5
gddI'm clearing out the issue queue in preparation to roll a new release. Is this still an issue? I tried to reproduce it with the dev version of filterbynodetype and the current wysiwyg api and couldn't.
Also some code got moved around so if this could be rerolled it would be helpful.
Comment #6
laddiebuck commentedI have this issue too, and am just wondering whether the D5 version will also be patched? Thanks in advance.
Comment #7
doitDave commentedThis problem has been fixed in a generally reviewed code I have already comitted. Both releases and dev snapshots from Dec 20, 2012 and later should work as desired. If not, please feel free to reopen this issue. Thanks!