Image Grid not updating to show changes in overly text size

[DTaylor7]

In using the Image Grid module, I try to change the size of the font that is used in the Overlay. (Under Grid Image>Overlay>Text)

Even though the size is changed, it stays at 12px.

I've contacted HubSpot Support, and they verified that it is likely due to the template I am using. I am using a custom template:

https://app.hubspot.com/design-manager/155527/templates/166201879823#module=170915478905975

It is an older template, so there may be something missing that is causing the error. 

What am I missing?

Thanks!

[DTaylor7]

It appears to be working now. Was a fix applied?

[Jnix284]

@DTaylor7 it's possible, glad to hear it's working now!

[Jnix284]

Hi @DTaylor7 happy to help - the link you've shared is to your HubSpot account and can't be viewed by anyone who doesn't have access.

Do you have a public preview/live URL to the page you can share?

Have you verified it is not a cache issue? You can do this with the unofficial HubSpot Developer Extension for chrome by using the bustcache and debug parameters.

Any additional information about the template code and screenshots would be helpful.

[DTaylor7]

Here is the public page:

https://explore.eyepromise.com/eyepromiseaeg

Thanks for directing me to the Developer Extension. I did try to clear my cache, but same results.

[Jnix284]

Thank you @DTaylor7 for the link, I can see where you tried to change the font size to 18px. It looks like the overlay text is in a span class that has an element style that is taking priority over your change:

Can you share a screenshot of where you've added the text in the editor so I can see what it looks like in the module? This will help me point you in the right direction for where to check next to see if we can get it fixed.

[DTaylor7]

This is where we change the font size:

[Jnix284 · Accepted solution]

Thank you @DTaylor7 this looks like it might be a bug with the module.

I will try to recreate the issue to remove any variables from your account we might've missed to confirm if this is a bug in the module.