Weaver Xtreme 6.2.1.1 fixes some issues

[Weaver]

There have been several issues with Weaver Xtreme 6.2.1 that have been fixed in 6.2.1.1 just released on WP.

There was a typo that  created an undefined function that was evident when using he WHAT Customizer.

There were problems with Custom CSS options (both from the Customizer and the equivalent CSS+ options in the legacy interface.)

These have been fixed. They were difficult to test because there are so many option. The problem was caused by changing Weaver Xtreme to use only inline CSS rather than loading CSS from files. All should be working now.

One side effect of fixing the issue is that when using the Customizer for Custom CSS, the site display screen will refresh when entering the Custom CSS rules instead of trying to auto-update the site display.

[webitman]

No it did not. Still a problem and again I changed back to 6.2.0.1

[HCB]

The problem still exist.

All kind of code in top off my site…

Went back to 6.2.1

[webitman]

Deactivate the plugin : Weaver Xtreme Theme Support

And now the problem has gone. WP 6.2 + Weaver Xtreme 6.2.1.1

Thanks for this great theme.

[scrambler]

This is not a solution as the theme support plugin is used for some key stuff.

Have you tried reinstalling the latest theme support version from WordPress ?

It should be 6.2.9 and if you have the plus Plugin, that should be 6.2

[Weaver]

@HCB, @webitman –

I am unable to reproduce any issues with the current version 6.2.1.1 currently available on the WP theme repostory.

There were two know issues with the 6.2.1.0 version.

1. an undefined eesc_html__ function which was a typo and only manifested when using the WHAT Customizer interface.
2.  An issue with Custom CSS (from the customizer, or the CSS+ options in the legacy interface). Those options did not work, or caused some CSS text to be displayed at the top of the site. This problem was caused by a problem making the theme backward compatible with Weaver Xtreme Plus V4 (vs the current V6.2 which has been released but only to those with current Weaver Xtreme Plus licenses.)

There were a couple of test versions of Weaver Xtreme 6.2.1.x released before the current 6.2.1.1 was release to the  WP repository.

Please see the (about to be posted) thread explaining the new versioning numbering, and the Theme Support plugin.

If have updated to Weaver Xtreme V 6.2.1.1 from the WP repository and continue to have issues with seeing CSS, please post a private post here for follow up.

[sbarnessckls]

This reply has been marked as private.

[Weaver]

I’m 95% sure I’ve found the issue, and it was a two parter:

First, the theme caches generated CSS, and it was not being cleared for the new theme versions. That will happen automatically now when a new theme version changes the format of the saved CSS (but only when logged in as would be expected – only authorized access to the settings). The GPL borrowed code the theme uses to minify the CSS for the cache apparently does not handle unusual variation of /* comments */, and the theme was was using a few CSS comments that apparently broke the minify code resulting in some broken partial comments in the cached CSS. This did not always result in stray characters appearing on the site.

Testing was pretty difficult for this one, mostly because of the unexpected problem with the CSS minify code. Couple that with the caching issue, and we had a mystery.

Weaver Xtreme 6.2.1.2 should fix this. It was no wonder it was so difficult to diagnose.

[Author]

Posts