Divi Menu Links

Hi Scott! Any chance you could email me the site URL? My address is at the bottom of the settings pages.

If the site isn’t available publicly or whatever, can you email me a snippet of the HTML where you’re seeing the problem? There’s a decent chance I have a flawed assumption in how I’m adding the class…

Hi Curtis,
Thank you for your quick reply.
I actually came up with a jQuery workaround, but I think a solution within the plugin would be cleaner.
Here is the HTML code and a workaround:
<li class="orange fordesktop noExitNotifier menu-item menu-item-type-custom menu-item-object-custom menu-item-234580"><a href="https://www.domain.com/123/">Online Banking</a></li>
In the above code, the “li” class “noExitNotifier” is ignored.
Here is my working jQuery solution:
$(".orange a").attr("class","noExitNotifier");
Hope that helps ?? Thanks again. – scott

• This reply was modified 3 years, 11 months ago by sbernado.

Scott, how are you adding the noExitNotifier class in the first place?

As I read back, I had thought you were talking about the Exit Notifier class that gets added to indicate it’s an outbound link. The noExitNotifier class is one you add manually to any content you want to exclude from Exit Notifier. So my plugin is not placing that class, just looking for it in the <a> tag.

Your workaround will certainly do the job, but it’s going to be somewhere in Divi that you would add the class to the <a> tag instead of the <li> tag. Unfortunately, I’m not that familiar with Divi or I’d be glad to help more.

Does that make sense?

I am adding it through Appearance >> Menus >> and then adding the “noExitNotifier” to the class field within a menu item (view the Screen Options at top of the page to ensure it is checked off or you will not see class as an option).

Does that answer your question?

Yes, it does, Scott. It also confirms that the issue you’re having with that really has nothing to do with Exit Notifier.

Divi is adding the class to the outer element instead of to the <a> tag. When styling for appearance, that works fine, but not in this case. Your workaround does the trick so I think you’re ok, but there’s nothing I can do if the class isn’t actually on the element my plugin is already looking at. It would be quite impractical and slow to take the time to also examine all of the parent elements in case the class is on the wrong element.

Does that make sense to you? I’ll tentatively mark this as resolved, but please feel free to follow up if you disagree. I’ll be glad to continue the conversation.

Hi Curtis.

I agree that Exit Notifier is doing things properly (inspecting anchor tags), and that Divi is causing the issue, but the issue still persists within one of the most popular themes ??

Thanks anyway.