Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Legacy inactive classic widgets break widget functionality on the block edtpr #101170

Open
filipanoscampos opened this issue Mar 11, 2025 · 2 comments
Open

Legacy inactive classic widgets break widget functionality on the block edtpr #101170

filipanoscampos opened this issue Mar 11, 2025 · 2 comments
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Customizer The site customizer for traditional, non-block themes. [Feature Group] Appearance & Themes Features related to the appearance of sites. [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Auto-allocated [Type] Bug When a feature is broken and / or not performing as intended

Comments

@filipanoscampos
Copy link

Context and steps to reproduce

On older simple websites that use Classic themes and that used to have the Classic widget experience, there are left over inactive widgets that we can see if we disable the block widget editor.

We see cases of these widgets breaking the widget editor from time to time.

One such case:
9503276-zd-a8c

And others:
p2EDhh-1VB-p2
p2EDhh-1QP-p2
5923198-zd-a8c

I'm sure there are more.
But removing these from all WordPress.com simple sites would solve issues for many users and remove the need for these users to contact us to clear this for them.

When we are contacted about this, we disable the block widget editor through the BRC and remove the legacy widgets.

Site owner impact

Fewer than 20% of the total website/platform users

Severity

Minor

What other impact(s) does this issue have?

Individual site owner revenue

If a workaround is available, please outline it here.

No response

Platform

Simple
@filipanoscampos filipanoscampos added [Feature Group] Appearance & Themes Features related to the appearance of sites. [Feature] Customizer The site customizer for traditional, non-block themes. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Mar 11, 2025
@github-actions github-actions bot added the [Pri] Normal Schedule for the next available opportuinity. label Mar 11, 2025
@github-actions GitHub Actions
Copy link

Support References

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

  • 9503276-zen
  • 5923198-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Mar 11, 2025
@janmckell
Copy link

Several similar issues were closed, without a fix:
#58696
#58594
#58716
#101170

Hey @tyxla Might you know which team would be responsible for taking a look into this ?

@janmckell janmckell moved this from Needs Triage to In Triage in Automattic Prioritization: The One Board ™ Mar 11, 2025
@janmckell janmckell removed the Needs triage Ticket needs to be triaged label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Customizer The site customizer for traditional, non-block themes. [Feature Group] Appearance & Themes Features related to the appearance of sites. [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Auto-allocated [Type] Bug When a feature is broken and / or not performing as intended
Projects
Automattic Prioritization: The One Board ™
Status: In Triage
Milestone
No milestone
Development

No branches or pull requests
3 participants
@filipanoscampos @matticbot @janmckell