Classic Editor vs Urdu Text Fixer

Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor. Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary. At a glance, this plugin adds the following: Administrators can select the default editor for all users. Administrators can allow users to change their default editor. When allowed, the users can choose which editor to use for each post. Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content. In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type. By default, this plugin hides all functionality available in the new block editor (“Gutenberg”).

Urdu Text Fixer makes writing Urdu, Persian, and Arabic content in WordPress effortless. It automatically detects Arabic‑script text (Urdu, Persian, Arabic, Pashto, and others) in both the Block Editor (Gutenberg) and the Classic Editor (TinyMCE) and switches the editing area to right‑to‑left (RTL) mode. Mixed bidirectional content: English words, Western‑Arabic digits, and punctuation like ! , "" () - embedded in Arabic‑script text are automatically wrapped with Unicode bidirectional isolation markers so they render left‑to‑right inside the surrounding RTL context. No configuration needed: The plugin works out of the box. A toggle in the Document Settings panel (Block Editor) or a toolbar button (Classic Editor) lets you disable auto‑detection if needed. Features Auto‑detection Recognises Arabic‑script characters as you type or paste Classic Editor support A TinyMCE plugin with a toolbar button and live RTL switching Bidirectional text fixing English words, numbers, and special characters are wrapped in Unicode LRI/PDI isolation markers during save and display Front‑end rendering Arabic‑script posts are wrapped in so they display correctly on the public site Comments support Arabic‑script comments also receive RTL treatment HTML‑safe Processes only text nodes, leaving HTML tags intact Idempotent Running the fix twice produces the same result; no duplicate markers accumulate