Adding a global styles input and specifying a font family causes error

Fixed Bugs
1

Description:

When adding an input style in Global Styles > Elements > HTML, as soon as you specify a font family, a fatal error occurs and the entire interface in no longer usable.

This is the error:

ReferenceError: lg is not defined
    at Ua (https://projectanx.com/wp-content/plugins/cwicly/build/index.js?ver=1.2.9.9.4:3:135657)
    at wt (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47637)
    at js (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:120584)
    at wl (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88659)
    at bl (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88587)
    at yl (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88450)
    at il (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85274)
    at fl (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85661)
    at Nn (https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:32474)
    at https://projectanx.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:83226

Step-by-step reproduction instructions:

  1. Open the Post Editor/Site Editor
  2. Open Global Styles > Elements > HTML > Input
  3. Create a new input style and set the type to any input type
  4. Specify any font family (Google or Local) in the typography settings
  5. Notice the error

Screenshots, screen recording, code snippet

Screenshot 2023-08-24 at 13.55.08
Screenshot 2023-08-24 at 13.55.081195×229 7.81 KB

Environment info

  • WordPress version: 6.3
  • Cwicly Plugin version: 1.2.9.9.4
2

Hi @StrangeTech,

Thank you for bringing this to our attention!

I have been able to reproduce this error in the Global Styles > Elements > Blocks & HTML, and can confirm it is a bug.
We’ll be sure to fix this as soon as possible.

Apologies for the inconvenience.

3

Thank you @Araminta. That is very much appreciated as we are currently holding off on making a site live until this is resolved.

4

@Araminta, from our testing, this seems completely fixed in the latest version, thanks again for the quick turnaround!

1 Like
5

Hi @StrangeTech,

Thanks for confirming this, much appreciated.

Cheers,