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

WordPress 5.6 compatibility – test, log any issues #1485

Closed
haszari opened this issue Oct 1, 2020 · 2 comments
Closed

WordPress 5.6 compatibility – test, log any issues #1485

haszari opened this issue Oct 1, 2020 · 2 comments
Labels
good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically.
Milestone
2.9.0

Comments

@haszari
Copy link
Member

haszari commented Oct 1, 2020

WordPress 5.6 is coming! The goal of this issue is to review WP 5.6 for any relevant changes and test Storefront to confirm everything's working correctly; and log any follow up issues if needed. Probably best to start this testing close to WP 5.6 RC – 17 Nov.

Widgets areas are changing – now edited with block editor! So we may see some wrinkles with widget styling (etc).
@haszari haszari added the good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. label Oct 1, 2020
@nerrad nerrad added the priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. label Oct 9, 2020
@Aljullu Aljullu added this to the 2.9.0 milestone Oct 13, 2020
@Aljullu
Copy link
Contributor

Aljullu commented Oct 21, 2020

I tested Storefront with WordPress 5.6 and I could only find one issue (#1512).

Widgets areas are changing – now edited with block editor! So we may see some wrinkles with widget styling (etc).

Notice this feature has been punted to WordPress 5.7: https://core.trac.wordpress.org/ticket/51506.

This was referenced Oct 22, 2020
Closed
Closed
Closed
Closed
@Aljullu
Copy link
Contributor

Aljullu commented Nov 3, 2020

I will proceed closing this issue for now. We did some testing + we have one more of RC testing to catch new issues. In case some arise, we can open individual issues for them.

@Aljullu Aljullu closed this as completed Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically.
Projects
None yet
Milestone
2.9.0
Development

No branches or pull requests
3 participants
@nerrad @Aljullu @haszari