Yoast / wordpress-seo

Yoast SEO for WordPress

Home Page:https://yoast.com/wordpress/plugins/seo/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Allow the usage of multiple FAQ blocks in a page

josevarghese opened this issue · comments

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened

The FAQ block usage on a page multiple times is set as false . In version 16.3 we added this multiple usage support.

Previous issue: #14429

To Reproduce

Step-by-step reproduction instructions

  1. Add FAQ block to the Block editor
  2. Then try adding the FAQ block to the same page again. You can notice the block showing as hidden/grey out.

Expected results

  1. Multiple usage of FAQ need to be added back

Actual results

  1. We cannot add the multiple FAQ block to a single page

Screenshots, screen recording, code snippet

If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
Screenshot 2024-05-23 at 12 21 17 PM

Technical info

  • If relevant, which editor is affected (or editors):
  • Block Editor
  • Gutenberg Editor
  • Elementor Editor
  • Classic Editor
  • Other:
  • Which browser is affected (or browsers):
  • Chrome
  • Firefox
  • Safari
  • Other:

Used versions

  • Device you are using: Desktop
  • Operating system: Windows
  • PHP version: 7.4
  • WordPress version: 6.5.3
  • WordPress Theme: Twenty Twenty Two
  • Yoast SEO version: 22.7
  • Gutenberg plugin version:
  • Elementor plugin version:
  • Classic Editor plugin version:
  • Relevant plugins in case of a bug:

Please inform the customer of conversation # 1137464 when this conversation has been closed.

Please inform the customer of conversation # 1137505 when this conversation has been closed.

Please inform the customer of conversation # 1137877 when this conversation has been closed.

Please inform the customer of conversation # 1140678 when this conversation has been closed.

Closing as we have fixed this issue on v22.8.