Hi @MaryJewelI,
Great question! The "Edit using old editor" and "Edit using improved editor" options are controlled by the Enhanced Content Editor (ECE) settings.
Here are a few ways to enable them:
Option 1: System Property (recommended)
Navigate to sys_properties.list and search for: sn_km_center.glide.knowman.ece.enable
- Set to true to enable the new ECE editor with the toggle options
- Set to false to force the classic editor only
Option 2: Knowledge Base configuration
1. Go to Knowledge > Administration > Knowledge Bases
2. Open your knowledge base record
3. Look for the Editor or Content Editor field
4. Select between Classic and Enhanced editor per KB
Important notes:
- In newer releases (Washington DC+), the classic editor is gradually being phased out
- The property approach is cleaner and easier to maintain
- If you still don t see the options, clear your browser cache and run cache.do
Hope this helps! Let me know if any of these steps don t work for your specific release version.Hi @MaryJewelI, Great question! The "Edit using old editor" and "Edit using improved editor" options are controlled by the Enhanced Content Editor (ECE) settings. Here are a few ways to enable them: Option 1: System Property (recommended) Navigate to sys_properties.list and search for: sn_km_center.glide.knowman.ece.enable - Set to true to enable the new ECE editor with the toggle options - Set to false to force the classic editor only (no toggle visible) Option 2: Knowledge Base configuration 1. Go to Knowledge > Administration > Knowledge Bases 2. Open your knowledge base record 3. Look for the Editor or Content Editor field 4. You can select between Classic and Enhanced editor per KB Option 3: Workspace settings (if editing from Workspace) If you are landing in the new editor when editing from a Workspace: 1. Navigate to Knowledge > Articles from the main platform nav (not from Workspace) 2. Open the article 3. Check the view selector at the top and switch to "Classic" if available Important notes: - In newer releases (Washington DC+), the classic editor is gradually being phased out, so the toggle may not appear in all navigation paths - The client script approach you mentioned can also work, but the property approach is cleaner and easier to maintain - If you have the property set but still don't see the options, clear your browser cache and run cache.do to flush server-side caches Hope this helps! Let me know if any of these steps don't work for your specific release version.
