The default styling of the NWS Alert plugin sets the <article> container z-index to 10000 on hover to prevent it from displaying behind content. This is possibly a conflict with your site theme or other plugins. If you’re willing to share the webpage URL I will take a look and see whats causing the problem.
Unfortunately it looks like there isn’t much that I can do with the plugin to prevent this sort of situation from happening. I’m not real familiar with Visual Composer, but it looks like your theme is looking for rows with a child that has the “span_12” class and sets the z-index to 10. Essentially each row has a z-index set, so even if I set the alerts plugin to z-index of 10000000 the parent elements would supersede that since it, and it’s siblings, have a z-index of their own.
One way around this is to set the row (that contains the NWS Alerts shortcode) to a higher z-index than its siblings. You could set custom CSS for the 1weather page in Visual Composer and use the id of the row.
#fws_54ee43cd94e10 {
z-index: 11;
}
Though this will fix the problem it’s not the best solution since the id may change depending on how Visual Composer builds these ids. If you’re able to add a custom class to the row that contains the NWS Alerts shortcode (something such as ‘nws-alerts-page-builder-stack-fix’) then you could use that class in the CSS to target the row and know that it wouldn’t change. Something like this:
.nws-alerts-page-builder-stack-fix {
/* Uses 10000 to match the z-index of the NWS Alerts article */
z-index: 10000;
}
I’ve logged this and will be looking into possible solutions for future releases of the NWS Alerts plugin.
