Error while accessing Global Styles - Typography

Fixed Bugs
1

Dear Team,

I just installed Cwicly 1.2.9.8.2 and regenerated the HTML and CSS.

When I edit a page and click on the Cwicly Global Styles - Typography button I am sent back to blank page on the backend that shows the following error message:

Capture d'écran 2023-07-27 130102
Capture d'écran 2023-07-27 130102991×124 3.65 KB

Content of the clipboard:
TypeError: o.includes is not a function
at t (https://cwicly-showcase.local/wp-content/plugins/cwicly/build/index.js?ver=1.2.9.8.2:3:186107)
at bs (https://cwicly-showcase.local/wp-content/plugins/cwicly/build/index.js?ver=1.2.9.8.2:3:188734)
at kt (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47633)
at js (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:120746)
at kl (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88654)
at yl (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88582)
at vl (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88445)
at ol (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85269)
at cl (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85656)
at zn (https://cwicly-showcase.local/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:32470)

The error occurs both on a live site and on a Local by Flywheel environment. Colours, Elements and Settings do not appear to be affected.

Environment info

  • Windows 11
  • Edge ver. 115
  • WordPress version: 6.2.2
  • Cwicly Plugin version: 1.2.9.8.2

Could you have a look at this? Thanks!

Regards,

Hubert

2

Seems it is not only you seeing this issue and also applies to 1.3-beta2:

3

I have the same bug on my site.

After updating to the latest release and regenerating all assets I cant access the Global Styles Typography anymore.

TypeError: o.includes is not a function
    at t (https://psa-media.com/wp-content/plugins/cwicly/build/index.js?ver=1.2.9.8.2:3:186107)
    at bs (https://psa-media.com/wp-content/plugins/cwicly/build/index.js?ver=1.2.9.8.2:3:188734)
    at kt (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47633)
    at js (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:120746)
    at kl (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88654)
    at yl (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88582)
    at vl (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88445)
    at ol (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85269)
    at cl (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85656)
    at zn (https://psa-media.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:32470)
4

@Louis, just bringing this to your attention if you are not already aware of it.

@psa and @hubie-w, what settings are you using for the sections (legacy or new)?

5

Hi Dan,

I had the Depreciated options (Section Layout, Button Styles and Font Sets) activated. After switching them off and regenerating the assets, I still get the error message.

Best regards,

Hubert

6

Hello @hubie-w and @psa,

Really sorry to read you’re having trouble accessing these Typography panel in Global Styles after the last update, my apologies for any inconvenience this may be causing.

Would it be possible for me to temporarily have access to a live installation of yours so I can see what we might have missed?

Thanks in advance.

And thank you @StrangeTech for tagging, helps notify me directly.

Cheers,

7

problem is new section because I got also in 1.2.8.2

8

Yes I sent you email on support address

9

@g97iulio There must be another factor involved as we have multiple sites with both the new version and the beta version, with deprecated sections turned on and off and we do not get this error on any of them.

10

Btw toggle menu on cwicly.com doesn’t work properly.

11

Sure, I just sent you an email to support@cwicly.com. The Domain is Anmelden ‹ PSA Media — WordPress

Thanks

12

Hi @hubie-w, @psa and @g97iulio,

Thank you for providing us with a temporary access to both your installations.

We believe we might have found the root cause of this issue.

If it’s okay with both of you, could we possibly replace a few files on your installation within the Cwicly plugin, and see if it helps?

If not, please let me know.

Thank you in advance.

13

Hi Araminta,

You should receive the credentials on the support e-mail for https://hubertwagelmans.com.

Best regards,

Hubert

1 Like
14

No problem I’ve made a backup. :+1:

1 Like
15

Yea it’s okay for me

1 Like
16

Hello @psa and @hubie-w,

My apologies for the trouble here. The bug is related to the use of the Fluid Value Maker, which we did not account for when displaying the preview in the Global Styles Typography panel.

I’ve made the necessary file change on your end so it should be working once again.

@g97iulio, unfortunately, since you’re working with the components beta, I won’t be able to fix it for you before tomorrow’s update (we’ll add the change to the current beta). Sorry for the inconvenience here!

Thanks, everyone, for your patience and understanding.

Cheers,

17

When the current beta will be updated ? Thank you . Check cwicly.com mobile menu because doesn’t work properly

1 Like
18

Hello @g97iulio,

The beta will be updated tomorrow to reflect this change.

As for the bug with the mobile menu, thanks for the report. This is an issue that will also be fixed in tomorrow’s update.

Cheers,

1 Like
19

The issue with the menu on Cwicly.com is separate from the problem I am encountering on my website or the specific post I made in the bug report sub-forum. This menu bug appears when I click on the toggle for the first time. In other words, it’s a distinct problem and not related to the other issues I’ve mentioned.

20

Hello @g97iulio,

I have considered them separate issues, thank you.
Rest assured we’ll be addressing them.

Cheers,

1 Like