Title: CMTooltip bug report Last modified: May 20, 2023 --- # CMTooltip bug report * Resolved [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/) * When I try to use “highlight first occurrence” setting – glossary terms that are in headings H1, H2… are not shown in headings and are totally ignored in the rest of a page. But headings contain key glossary terms for the entire page… * This problem appears for global “highlight first occurrence” setting and for a single page “highlight first occurrence” setting. * Either glossary terms that headers contain should not be counted as the first occurrence, or headers should show the first occurrence tooltip. * I use Astra theme with Elementor and everything else works ok. - This topic was modified 3 years ago by [mountbest](https://wordpress.org/support/users/mountbest/). * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcmtooltip-bug-report%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 12 replies - 1 through 12 (of 12 total) * Plugin Author [CreativeMindsSolutions](https://wordpress.org/support/users/creativemindssolutions/) * (@creativemindssolutions) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16757121) * There is a separate setting that controls whether or not the terms should be highlighted in the h1-h6 tags – it’s called “Avoid parsing protected tags”. * Thread Starter [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16759339) * “Avoid parsing protected tags” H1 setting seems to be set AUTOMATICALLY when I choose “first instance only” option with no option to change this setting. Not only that. Glossary terms that happen to be in the H1 heading are EXCLUDED from parsing for the rest of the page. * Since glossary terms that are in H1 headings are the most important on a given page, the “first instance only” option as it is at the moment becomes useless if glossary term appears in the H1 heading. * Plugin Author [CreativeMindsSolutions](https://wordpress.org/support/users/creativemindssolutions/) * (@creativemindssolutions) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16764906) * In the next version we release the “Avoid parsing protected tags” will be replaced with more granular selection, allowing to include/exclude h1-h6 tags. We’ll likely release it tomorrow. * Thread Starter [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16769747) * I could not find settings that you are talking about. “Avoid parsing protected tags” setting disappeared, but there are no new settings. * The issue remains: when “highlight first occurrence” option is set, glossary terms that appear in headings are completely ignored, no matter what other settings are. * Plugin Author [CreativeMindsSolutions](https://wordpress.org/support/users/creativemindssolutions/) * (@creativemindssolutions) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16772947) * The new setting is in the General Settings – in Term Highlighting section. * Thread Starter [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16773994) * if I choose “Highlight first term occurrence only” H1 headers are not only ignored, but glossary terms that they contain are IGNORED for the rest of the page. No matter what other settings I choose. New Exclude settings have no effect in this situation. * So, “Highlight first term occurrence only” option is USELESS if H1 contains any glossary term, because such glossary term is very important on the page. * Plugin Author [CreativeMindsSolutions](https://wordpress.org/support/users/creativemindssolutions/) * (@creativemindssolutions) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16782807) * I’ve tried to replicate the issues you’re having, but I couldn’t. Here’s my setup: – Exclude HTML tags from parsing: (deselect options all heading tags h1- h6 and h1)– Highlight only the first term occurrence Then on the test page I put the term in h1 first then in the regular text. And it does highlight the term in the h1. * Thread Starter [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16784640) * I tried your setup several times and it does not work for me. Glossary terms that are in h1 are ignored when the first occurrence is selected. I double checked CMTootip settings on individual pages too. * There must be some conflict somewhere. I use Elementor Pro on my website. * Plugin Author [CreativeMindsSolutions](https://wordpress.org/support/users/creativemindssolutions/) * (@creativemindssolutions) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16794237) * Yes, it’s possible there’s some kind of conflict. Could you check please if it works on a regular page without Elementor Pro? That information would help us a lot in pinpointing the issue. * Thread Starter [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16796340) * On solo (non-multisite) Oxygen builder domain ([https://bioresonant.com](https://bioresonant.com)), the h1 headers are not parsed for glossary items, no matter what CMTooltip settings I choose. h2 headers are parsed fine. * When I choose “highlight the first occurrence” , h1 headers are ignored in parsing, but everything else works as expected. Glossary terms that appear in h1 are ignored in h1, but their first non-h1 occurrence is parsed elsewhere. * Plugin Author [CreativeMindsSolutions](https://wordpress.org/support/users/creativemindssolutions/) * (@creativemindssolutions) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16796351) * Our plugin use the WordPress the_content hooks to parse the content. There is no other hooks which are global and can be used to parse content * What you are describing sounds like the theme builder didn’t apply this hook ok the H1 Nothing we can do about this as this is not a bug in our plugin * Thread Starter [mountbest](https://wordpress.org/support/users/mountbest/) * (@mountbest) * [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16796602) * Overall I am satisfied with CMTooltip even though I observe some peculiarities of some settings. * Could meta tags in the source be responsible for strange h1 parsing behavior? Viewing 12 replies - 1 through 12 (of 12 total) The topic ‘CMTooltip bug report’ is closed to new replies. * ![](https://ps.w.org/enhanced-tooltipglossary/assets/icon-256x256.png?rev=2072169) * [CM Tooltip Glossary](https://wordpress.org/plugins/enhanced-tooltipglossary/) * [Frequently Asked Questions](https://wordpress.org/plugins/enhanced-tooltipglossary/#faq) * [Support Threads](https://wordpress.org/support/plugin/enhanced-tooltipglossary/) * [Active Topics](https://wordpress.org/support/plugin/enhanced-tooltipglossary/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/enhanced-tooltipglossary/unresolved/) * [Reviews](https://wordpress.org/support/plugin/enhanced-tooltipglossary/reviews/) * 12 replies * 2 participants * Last reply from: [mountbest](https://wordpress.org/support/users/mountbest/) * Last activity: [3 years ago](https://wordpress.org/support/topic/cmtooltip-bug-report/#post-16796602) * Status: resolved