Opened 3 years ago
Closed 9 months ago
#57126 closed defect (bug) (worksforme)
Broken CSS for Buttons (previously created by Gutenberg block editor) after WP 6.1 Update
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 6.1 |
| Component: | Editor | Keywords: | reporter-feedback close |
| Focuses: | Cc: |
Description
Have multiple sites using popular free themes (Blocksy and OceanWP) and the button CSS (layout, colors, etc) is all broken after recent update to WP version 6.1
According to Blocksy theme devs, they say it's due to the WP core update that could have been handled differently to avoid this issue.
Only way to fix is to manually open every post or page with a button and then re-save the page. This is very time-intensive process for large sites with 100's or 1000's of posts and pages and also trying to remember or figure out which posts have buttons on them in the first place.
Seems that WP core dev team should release a fix/patch for this issue.
See for further clarification:
https://wordpress.org/support/topic/anyone-seeing-broken-buttons-css-afer-last-updates/
https://wordpress.org/support/topic/mobile-view-for-buttons-is-wrong-css-no-margin-or-alignment/
Thank you
Change History (5)
#2
@
3 years ago
@costdev I don't think it is related to the issues you mention, but could be related to https://github.com/WordPress/gutenberg/issues/44659 - I have added a link to this issue there.
#3
@
3 years ago
This is why we added this CSS: https://github.com/WordPress/gutenberg/pull/44334
Do you see the classic-theme.css file on your theme?
#5
@
9 months ago
- Keywords close added
- Milestone Awaiting Review deleted
- Resolution set to worksforme
- Status changed from new to closed
Thank you everyone for collaborating on this. I have reviewed this and I do think that it might be unique to the site and not as confirmed due to those issues linked. For now, my recommendation is going to be to close this as we haven’t heard any feedback. If this is however still an issue we can of course consider reopening if more information comes to light.
@glendaviesnz Is this related to GB 45179, GB 45153, another issue, or does a new issue need to be created?