Did I have to re-arrange the G2 filter to the top in order to get it working?
Richard Eriksson - September 17, 2009 - 18:41
| Project: | G2 Glossary |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
When installing the G2 module, the filter would remove all text if there was a <dfn> element in the text. (Not just the marked up text, but the entire body of the node.) I re-arranged the filters in the input format that I added G2 to, putting the G2 filter to the top. Was that the necessary step to get it working? If so, can we add to the documentation (README.txt) that this is indeed one of the installation steps for the module?
#1
Actually, this is one of the solutions, but not the only one: any variation of filters order in which the successive transformations brought by each filter is compatible with the next one will work: this is the basic behaviour of the Drupal filter system.
And since you can't predict which filters will be on any installation, there is really no hard rule as to which filter should go first. In the case of the default filtered html, it doesn't allow the dfn element, so the html filter removes the contents of the dfn element. If that element is not properly terminated, that can mean the whole node. Conversely, putting the g2 filter on top can prevent other filters from intervening, and break other setups.
So this is not really a G2 issue, and I don't think it would be appropriate to add this instruction to the README.txt.