M7tawa FAQ Manager for Posts

M7tawa FAQ Manager for Posts lets you create and display accessible FAQ accordions on WordPress content, with optional Schema.org FAQPage structured data. Google no longer displays FAQ rich results, but the visible FAQ content remains useful to readers. Features:

• Up to 10 questions and answers per post.
• Manual entry plus fast bulk entry using alternating question/answer lines.
• Drag-and-drop ordering without jQuery.
• Classic Editor meta box.
• Dynamic Gutenberg block using the same saved FAQ data.
• Automatic display before or after content.
• Manual display using the block or [m7tawa_faq] shortcode.
• Responsive, accessible accordion.
• RTL and LTR support.
• Light and dark color-scheme support.
• Optional Schema.org FAQPage JSON-LD.
• Import, export, and reset settings.
• No Bootstrap, jQuery, or external libraries.

2.0.6

• Improved compatibility with dark-mode themes by detecting the actual surrounding page background.
• User-defined custom colors continue to take priority over automatic theme color handling.
• No changes to stored FAQ data, settings keys, shortcode, block name, FAQPage structured data, or database structure.

2.0.5

• Updated the Gutenberg block to Block API v3 for WordPress 7.1 iframe-editor compatibility.
• Added a lightweight block editor stylesheet registered through the block editor style handle so the placeholder is styled inside the editor iframe.
• Clarified FAQPage structured data documentation following Google's retirement of FAQ rich results.
• Preserved the existing FAQPage JSON-LD option, shortcode, block name, stored FAQ data, and plugin settings.
• Verified compatibility with WordPress 7.1.
• No new database tables, migrations, tracking, external services, or unrelated features were added.

2.0.4

• Unified plugin-created PHP identifiers, hooks, handles, nonces, admin actions, DOM identifiers, and stored data under the distinctive M7tawa FAQ naming system.
• Migrated global settings to m7tawafaq_settings while retaining the legacy option for safe rollback.
• Added lazy, non-destructive migration of legacy FAQ post meta into the new _m7tawafaq_ keys; legacy post meta is not deleted during migration.
• Kept the public shortcode as [m7tawa_faq] and the approved slug m7tawa-faq-manager-posts.
• Renamed internal class files and front-end/admin selectors for consistent project identity.
• Removed the duplicate Plugin URI header and retained Author URI: https://m7tawa.com.
• No custom database tables or background site-wide migration scans were added.

2.0.3

• Renamed the plugin to M7tawa FAQ Manager for Posts and prepared the distinctive slug m7tawa-faq-manager-posts for WordPress.org review.
• Updated the plugin header, readme, Text Domain, settings page slug, Gutenberg block namespace, and all related references to the new identity.
• Introduced the uniquely prefixed [m7tawa_faq] shortcode for manual output.
• Removed bundled .po and .mo translation files so translations can be managed through translate.wordpress.org.
• Corrected the WordPress.org contributor username to aymanabdullahdev.
• Preserved legacy settings and post meta for backward compatibility during the identity transition.
• No changes to front-end FAQ HTML, FAQPage schema structure, manual/bulk entry logic, styles, or stored FAQ content.

2.0.2

• Repository compliance maintenance based on Plugin Check results; no changes to saved FAQ data or front-end FAQ structure.
• Added translator comments for placeholder strings used by PHP and JavaScript.
• Documented and suppressed read-only nonce false positives in admin notices while keeping state-changing actions nonce protected.
• Clarified recursive sanitization of nested FAQ and per-post option input after nonce and capability checks.
• Removed the no-longer-needed manual load_plugin_textdomain() call and rely on WordPress just-in-time translation loading.
• Prefixed template and uninstall local variables to follow WordPress naming conventions.
• Updated Tested up to to WordPress 7.0 after successful testing on WordPress 7.0.4.

2.0.1

• Repository-readiness maintenance release with no changes to saved FAQ data or front-end FAQ structure.
• Improved WordPress internationalization flow for English and Arabic administration screens.
• Removed the duplicate custom settings-saved notice and rely on the standard WordPress settings notice.
• Kept all FAQ HTML, accordion behavior, bulk/manual entry, styling options, and FAQPage schema behavior compatible with 2.0.0.

2.0.0

• Added Bulk Entry while keeping the complete Manual Entry workflow.
• Paste alternating question and answer lines and convert them into normal FAQ items in one click.
• Blank lines are ignored, incomplete pairs are rejected, and the existing 10-question limit is respected.
• Bulk-created items use the exact same stored data, server-rendered HTML, accordion, and FAQPage schema as manual items.
• Fixed repeated settings-saved messages.
• No new database tables, AJAX requests, or site-wide scans.

1.3.0

• New lightweight style presets, typography and spacing controls.
• Optional numbering, title tag selection, and animation controls.
• Simpler editor controls with up/down arrows and no add-at-top button.
• FAQ text remains server-rendered HTML in the article with matching FAQPage schema.

1.2.0

• Live settings preview and optional custom colors.
• Unsaved-change warnings and duplicate-question detection.
• Better mobile reordering and add-at-top controls.
• Direct post preview and improved copy workflow.
• Collapsible settings sections and clearer saved-state feedback.
• No new database tables or site-wide scans.

1.1.1

• Added a Settings link, Arabic plugin description, question counter, validation warnings, delete confirmation, and shortcode copy button.

1.1.0

• Added per-post controls, accordion options, copy question, accessibility improvements, and duplicate output protection.