Pro Update Issue — Custom CSS not compiling on specific page

Support
#1

Hi folks,

I’ve updated one of our bigger sites to Pro 6 and running into a weird issue. The update went smoothly everywhere except for this page (which is an important one): https://getrepowered.org/shop/

It looks like none of the CSS is being brought into the page and the slider has gone mad. I’ve tried clearing the caches, making small updates, commenting out erroring code, etc. — but nothing seems to get the compiler to pull in the styles.

This is a Page, not a WC Archive Layout. That’s also working fine: https://getrepowered.org/all-products/

Can you take a look and see what I’m missing ?

Thanks!

#2

Hi @lukefinsaas,

Thanks for reaching out.
I have checked the page and looks like the problem is with some Plugin or Cache. As you have already cleared the cache and that does not help, I would like to suggest troubleshooting the following common issue to help us to recognize the reason.

  1. Theme Related Issue
  2. Plugin Conflict
  3. Theme Update related issue
  4. Child Theme Related issue
  5. CSS/JS Customization
  6. Disabling Cache
  7. Disabling CDN

If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins.
If none of the above help, please provide login credentials for your site in a secure note to examine it further, including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.

secure-note
secure-note1040×250 15.3 KB

Thanks

#3

Thanks @tristup. I’ve figured it out (but still a weird error).

This ‘Our Promises’ section was our culprit (https://getrepowered.org/shop/). Removing the section altogether solved the compile issue.

I was able to rebuild it and avoid the issue. For some reason, I’d initially built it as a row (outer) + column (singular promise) + row + column (svg icon) / column (text). Simplifying the structure so that the svg, headline, and text all live in that singular promise column resolved the issue.

So. Not sure why cornerstone was having an issue, but maybe something to note to the dev team re: new version of pro.

Thanks!

#4

Hi @lukefinsaas,

Glad that you are able to figure it out. Maybe something in that section is blocking or creating some errors which block the CSS to be compiled.

Thanks

#5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.