Automattic / wp-calypso

The JavaScript and API powered WordPress.com
https://developer.wordpress.com
GNU General Public License v2.0
12.4k stars 1.98k forks source link

Widget visibility: Settings do not save on "Custom HTML" widget #57991

Open arunsathiya opened 2 years ago

arunsathiya commented 2 years ago

Quick summary

For the Custom HTML widget, widget visibility rules don't get saved. The widget visibility rules work okay (there's another issue https://github.com/Automattic/wp-calypso/issues/57992) on a paragraph block though.

Steps to reproduce

What you expected to happen

Widget visibility settings must stick.

What actually happened

Widget visibility settings are lost when Customizer/wp-admin dashboard is refreshed.

Context

User report. 4449509-zen.

Operating System

Windows, macOS, Linux, Android, iOS

Browser

Google Chrome/Chromium, Mozilla Firefox, Microsoft Edge, Microsoft Edge (legacy), Apple Safari

Simple, Atomic or both?

Simple

Theme-specific issue?

No. We have tested on Twenty Sixteen, Twenty Twenty, Twenty Twenty-One and Blank Canvas.

Other notes

I have not tested on Atomic.

Reproducibility

Consistent

Severity

All

Available workarounds?

No and the platform is unusable

Workaround details

I said there is no workaround above, but there's one. It's not ideal though: custom CSS to hide the widgets.

arunsathiya commented 2 years ago

These reports are related: https://github.com/Automattic/wp-calypso/issues/54678 and https://github.com/Automattic/jetpack/issues/21446

Robertght commented 2 years ago

Thank you for the report! @Automattic/flow-patrol-create is this something you could take a look at?

devNigel commented 2 years ago

Another case: 33104796-hc Follow up: 4578129-zen

ChrissiePollock commented 2 years ago

Another case - #4707262-zen

fjorgemota commented 2 years ago

Another case: 4712777-zd-woothemes

Tried to use both the customizer and the widgets page to save the visibility rules, but it doesn't work in either way.

zachspears commented 2 years ago

Another case - #5207438-zd-woothemes

inaikem commented 2 years ago

Another case in 36471072-hc

I've added this issue to the Dotcom Prioritization board for review - it's been triaged already, so I'm moving it to the allocation and prioritization queue.

github-actions[bot] commented 2 years ago

Support References

This comment is automatically generated. Please do not edit it.

shelb-elliott commented 1 year ago

We have another case of this submitted to Newspack. It's in a private Slack, so I can't link to it, but wanted to report it anyway.

Ninodevo commented 2 months ago

Hello! At Team51 we have an issue with this for a partner. Can this issue be moved forward?