How to show an Essential Grid layer on static, then hide it and show a different layer on hover?

[NMWeb]

I have an Essential Grid with several text based layers on it. I’d like to have one layer of text show when nobody is hovering over the grid, and a different layer of text upon hover.

This seems very straight foward to setup in Essential Grid. When in the Skin Editor each layer allows me to toggle “show without hover on desktop”.

So I expected to be able to simply turn on this toggle for the layers I wanted to show without hover, and to turn off the toggle for the layers I only want to show on hover. However if I turn this toggle on for one layer it causes all of the layers to show without hover, despite the other layers not having this toggle turned on. Am I missing something?

[prakash_s]

Hello @NMWeb,

Thanks for writing to us

To show/hide the layer on hover please have a look at this essentials grid doc to learn more about how to show/hide layers.
https://www.themepunch.com/essgrid-doc/item-skin-editor/#visibility

Hope it helps
Thanks

[NMWeb]

Thanks, but the doc you linked just states the same thing I said, that you can control layer visibility with and without hover via the two check boxes in my screenshot.

However this is not how it’s actually working for me. If I click “show without hover on desktop” for one layer it then causes all the other layers to also show on desktop without hover, regardless of what their settings are.

For example, here I have one layer with that setting checked on:

Here is another layer in the same skin with that setting unchecked:

That second layer shouldn’t show without hover, yet it does. I’ll add a secure note with login credentials to a dev site where this is occurring.

[ruenel]

Hello @NMWeb,

I have investigated the issue further and I suspect that this is a bug in the latest release of the plugin. We have added the issue to our issue tracker so that it will be forwarded to the creators of the plugin. I cannot make any promises relating to a fix at this stage. I will add a note to the tracker referencing your thread report though so our dev team can see there are multiple reports of the issue.

Thank you for your understanding.

[NMWeb]

Thanks @ruenel I appreciate you reporting it to the creators.

Unfortunately this feature, which I’ve used many times in past projects, is pretty critical to a project I’m working on right now. Do you have any recommendations for alternative plugins or work arounds?

Or is there a way for me to perhaps revert to an older version of Essential Grid? I’d be OK if that means having to start all my work customizing the skins over again.

[prakash_s]

Hello @NMWeb,

We have not tested such plugins at our end so can not recommend you any of them, you may search for the plugin on the WordPress plugin repository. Please note that we don’t provide any third-party plugin support. It is out of the support scope.

In case if you have a backup of your site you can restore the site backup. Please note we don’t provide an older version of the bundled plugin.

Thanks for understnading

[NMWeb]

I’m confused, Theme.co regularly provides third-party plugin support for the bundled plugins that come with Pro. You’ve provided me with support for the bundled plugins for five years now.

If I go to ThemePunch and ask for support on this issue they will refer me back to Theme.co, telling me that support for bundled plugins comes from the company providing the bundle.

Has something changed? Going forward should I assume Theme.co will not be providing support for the bundled plugins?

[ruenel]

Hello @NMWeb,

Yes, we do provide support for all of the plugins bundled in the theme. In this case, since this is a bug in the plugin, we can only refer the bug to the creators of the plugin as they are the ones who will be doing the bug fixes and updates of the plugin. Once the fixes and updates are ready, we will then test it and will have to make it available through the Themeco plugin repository.

Hope this explains it briefly. Thanks.

[NMWeb]

Good to know you are still providing support for bundled 3rd party plugins.

In the past when I’ve reported a bug with a bundled plugin Theme.co has provided a work around. Sometimes in the form of CSS, JS, or PHP snippets and sometimes by suggesting alternative plugins, but this is the first time for me that the response has been “it’s a bug, we’ve reported it” with no help beyond that.

This is an especially frustrating response because Theme.co never loops back to the people who reported bugs to let them know they’ve been fixed. Instead I’m expected to thoroughly review the release notes for each theme update to see if my bug is ever fixed (and in my experience for bundled 3rd party plugins the fix is typically not mentioned in theme release notes so the only way for me to know it’s fixed is to test it regularly).

[ruenel]

Hello @NMWeb,

The fixes for 3rd party plugins will not be included in the theme’s changelog simply because it is a 3rd party plugin. All the 3rd-party plugin updates, bug fixes, and new features should be check on their own respective plugin changelog pages. We also have to admit the fact that there are plugin creators that are very prompt and responsive in communicating when there are issues in their plugin and sadly, there are also those that do not even have responded to us back which is in some cases, the bugs or issues on their plugins are not yet resolved. Rest assured that each of the bugs or issues of the 3rd party plugin has been reported and is communicated to their respective plugin creators.

Thank you very much for your understanding.