Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

WP 6.4: Classic Template block for Single Product does not work on the front-end #11454

Closed
sunyatasattva opened this issue Oct 25, 2023 · 2 comments · Fixed by #11455
Closed

WP 6.4: Classic Template block for Single Product does not work on the front-end #11454

sunyatasattva opened this issue Oct 25, 2023 · 2 comments · Fixed by #11455
Assignees
@sunyatasattva
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue/PR concerns a confirmed bug. type: compatibility

Comments

@sunyatasattva
Copy link
Contributor

Describe the bug

Classic Template block doesn't render on the front-end of WordPress 6.4-based block themes.

To reproduce

Steps to reproduce the behavior:

  1. Enable WordPress 6.4.
  2. Enable a block theme.
  3. Go to Site Editor → Single Product template.
  4. Remove the blockified template and add the “Classic Template” block.
  5. Save and check the front-end.
  6. Notice that the template is not rendered.

Expected behavior

The template should render correctly using the “Classic Template” block.

Additional context

p1698230999338099-slack-C02FL3X7KR6
p1698246828170079-slack-C029LRAU2
@sunyatasattva sunyatasattva added type: bug The issue/PR concerns a confirmed bug. type: compatibility priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. labels Oct 25, 2023
@sunyatasattva sunyatasattva self-assigned this Oct 25, 2023
@sunyatasattva sunyatasattva mentioned this issue Oct 25, 2023
Merged
13 tasks
@sunyatasattva
Copy link
Contributor Author

sunyatasattva commented Nov 2, 2023 •
edited
Loading

Can confirm this is solved in 6.4-rc.3 as expected. Also closing the associated draft PR (#11455). However, this created a new issue: #11542

cc @danieldudzic

@gigitux
Copy link
Contributor

gigitux commented Nov 8, 2023

We noticed that 6.4-rc.2 didn't fix the issue. #11455 fixed the issue.

@gigitux gigitux mentioned this issue Dec 11, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sunyatasattva sunyatasattva

Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue/PR concerns a confirmed bug. type: compatibility
Projects
None yet
Milestone
No milestone
2 participants
@sunyatasattva @gigitux