joshuavb

Amazing news, thanks so much for confirming @greenshady.

Appreciate everything you and the team do to make our development lives easier!

This seems to be resolved in 6.6.1, confirmed by a few colleagues as well – although I can’t find it mentioned in the 6.6.1 changelog.

@greenshady Is it possible to know how this was addressed? It seems to be resolved across the board with the latest version. I just can’t find where the changes are recorded.

@mattkeys thanks so much for sticking on this, we look forward to the latest version!

Echoing what @titelala has said here, this is affecting our clients’ websites across the board and is requiring us to rollback to 6.5.

WP Core updates should not require us to charge clients for an update to their code base to work – extremely intrusive and unwelcome change.

Edit: we have now rolled back clients to 6.5 and have turned off automatic updates for the time being. Hoping that this can be reviewed and addressed in some way for 6.6.1, it’s been a long time since I saw a Core update that so heavy-handedly affected so many sites at a visual level.

• This reply was modified 4 months, 1 week ago by joshuavb.

Hey @mattkeys, thanks so much for your help and rapid responses – I’ve sung your praises many times to colleagues at this point!

We found an additional issue with our custom icons that still seems to be present in version 4.0.9. When we roll back to 4.0.6 the issue goes away, so we’re confident it is related.

This current thread is marked Resolved, so if you’d like me to open a new one that’s totally fine – I want to respect your support system (just let me know).

To make it easy to debug, we’ve downgraded to 4.0.6 on our Production site but kept 4.0.9 on our Staging site we can compare between them. In both examples below the icons are just below the Hero area in the blue boxes:

Production (4.0.6) – https://reliancehomecomfort.com/cambridge/plumbing/
Staging (4.0.9) – https://reliancehcstg.wpenginepowered.com/cambridge/plumbing/

You’ll see in 4.0.9 that the icons are not working as expected, they do output something but they are messed up and I think I know why.

On 4.0.6 the class is “fak fa-icon-name” and on 4.0.9 the class is “fa-kit fa-fak fa-icon-name”. When we switch the class using Inspect on 4.0.9 back to “fak fa-icon-name” everything goes back to normal, so that was the clue. It looks like in the CSS there is a line “i.fak” is “font-weight: 400 !important” and that is not present in the new class set. What is happening is the browser is applying pseudo-bolding which is messing up the line work. When we add “font-weight: 400 !important” to the .fa-kit class on 4.0.9 everything returns back to normal.

Hoping this helps! Appreciate all the support you’ve provided so far.

Thanks @mattkeys! We have updated the plugin and can confirm things are now fixed.

Appreciate your support on this.

Really appreciate the fast response, it’s really nice to see a plugin author be so responsive.

We’ll hold on to our 4.0.6 version and wait for the 4.0.9 fixes I think – again thanks for your help.

Agreed, after updating the plugin to 1.4.8, it breaks the logo slider completely.

I’m getting the following errors in my console log:

lsp_jquery.cycle2.js?ver=2.1.2:295 Uncaught TypeError: opts.API.log is not a function