Limit glossification to selected content types and displays

I made an extra Text Format called 'HTML + Glossary' and only that format uses the Glossify filter. Would that solve your problem?

Indeed this may be a solution and even better that what I suggested (option to select bundles) but we will still need an option to apply or not to summary which inherits the text format of the main field (body). I think most people don't want to have summaries with plenty links. Also I didn't check how such glossified summaries appear in metatags or in other token based fields.

Our solution for this was to use Field Formatter Filter → and create a text format with only the Glossify filter. Then, we were able to add that as an additional filter for the fields where we want Glossify to work. Editors do not need access to the text format with this solution, and you don't need to change the text format of your content.

Just commenting this is an issue for me as well, as we only want Glossify on book pages. Thus, will create text formats only for the book content type with Glossify enabled.

Happy to review MR's but this isn't something we're going to implement ourselves. I think it's an edge-case and there are ways to solve this like described above or in contrib.

Feel free to close won't fix or provide an implementation.

nishantghetiya → changed the visibility of the branch 3401411-limit-glossification-to to hidden.

I've created an MR that provides checkbox settings for restricting content type on glossify configuration.

@nishantghetiya thanks, nice!!

• The bundles should be stored as sequence, not as string with separator
• This should also be implemented for the other entity types