Headerbuilder looks strange after update to PRO V2

Support
#1

I share the console information in a secure note.

have you changed any paths that we need to know and exclude from all caching instances/minifies etc?

#2

Hi There,

Thanks for writing in!
I will give you all JS files list of the theme which should not be minified:

  1. wp-content/themes/pro/framework/js/dist/site/x-body.min.js
  2. wp-content/themes/pro/framework/js/dist/site/x-head.min.js?
  3. wp-content/themes/pro/framework/js/dist/site/x-icon.min.js
  4. wp-content/themes/pro/framework/legacy/cranium/js/dist/site/x-body.min.js
  5. wp-content/themes/pro/framework/legacy/cranium/js/dist/site/x-head.min.js

Also here is the list of the JS files of the Cornerstone which should be excluded:

  1. wp-content/themes/pro/cornerstone/assets/dist/js/site/cs-body.js
  2. wp-content/themes/pro/cornerstone/assets/dist/js/site/cs-head.js

Thank you.

#3

This is the same as before, correct? This is already excluded :slight_smile: and have flushed and regenerate minify and combine.

Also see that the default builder path is changed form /x/ to /pro/ have updated page rule in cloudflare to bypass. Still seeing the issue.

#4

Hi there,

It’s already /pro/ even on very first version of Pro. And /x/ is always for X theme, but those permalinks are always changeable in the builder settings.

This is also normal for every update since your cache is based on older versions. Updating it while there are older cache could case the same display issue.

We also added a feature you could use to clear-up styling cache, please go to Admin > Pro > Settings and click Clear Style Cache button. Then purge your CF caches too, else, it’s not going to take effect.

Thanks!

#5

Yeah got that but changed to /pro/ and wild card is used of course.

Already cleared, all cache instances and that new feature yes, still the same issue.

#6

Hi there,

In that case, please provide your site’s URL and admin login credentials in a secure note. Then your CF login credentials too so could test it too.

Thanks!

#7

Right now I can not do that since we deploy other things on the server right now and cloudflare so I don’t want strangers in the systems at the moment. I will check in tomorrow and see if I can give you temporary access.

#8

Sure, please let us know.

#9

Problem solved. It’s because you have changed the path to /pro/ which was not added to our exclusion rule to skip cache and pass request to backend in xvarnish/cachewall.

#10

Glad you sorted the issue and thank you for sharing that information.

Cheers!

#11

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