Title: Brian Alexander's Replies | WordPress.org

---

# Brian Alexander

  [  ](https://wordpress.org/support/users/ironprogrammer/)

 *   [Profile](https://wordpress.org/support/users/ironprogrammer/)
 *   [Topics Started](https://wordpress.org/support/users/ironprogrammer/topics/)
 *   [Replies Created](https://wordpress.org/support/users/ironprogrammer/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/ironprogrammer/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/ironprogrammer/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/ironprogrammer/engagements/)
 *   [Favorites](https://wordpress.org/support/users/ironprogrammer/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 105 total)

1 [2](https://wordpress.org/support/users/ironprogrammer/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/ironprogrammer/replies/page/3/?output_format=md)…
[5](https://wordpress.org/support/users/ironprogrammer/replies/page/5/?output_format=md)
[6](https://wordpress.org/support/users/ironprogrammer/replies/page/6/?output_format=md)
[7](https://wordpress.org/support/users/ironprogrammer/replies/page/7/?output_format=md)
[→](https://wordpress.org/support/users/ironprogrammer/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Classic Editor adds extra classes to tags](https://wordpress.org/support/topic/classic-editor-adds-extra-classes-to-tags/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/classic-editor-adds-extra-classes-to-tags/#post-18183375)
 * Building on [@psykro](https://wordpress.org/support/users/psykro/)’s response,
   if the text was pasted in from another app, then this looks similar to [https://wordpress.org/support/topic/remove-default-font-weight/](https://wordpress.org/support/topic/remove-default-font-weight/).
   There are some testing instructions on that thread that might help reveal where
   the additional markup is coming from.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] No se ve el titulo](https://wordpress.org/support/topic/no-se-ve-el-titulo/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/no-se-ve-el-titulo/#post-18179223)
 * When you open your browser’s web inspector tools, are there any errors appearing
   in the JS console?
 * There’s a large gap in your screenshot, and I wonder if the markup is hidden 
   or has been removed 🤔 You might view the source to confirm what is going on 
   there. Here’s what appears in my testing:
 * ![](https://i0.wp.com/cldup.com/C3d7g25auR.png?ssl=1)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] remove default font-weight](https://wordpress.org/support/topic/remove-default-font-weight/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/remove-default-font-weight/#post-18177320)
 * Hi, [@briantoronto](https://wordpress.org/support/users/briantoronto/) — I don’t
   have Word, but suspect that the app has applied the styling to the paragraphs.
   This is similar behavior to pasting in formatted text from Google Docs.
 * To test the content of your clipboard, check out this [Clipboard Viewer](https://dmsnell.github.io/ghpages/clipboard.html)
   and paste in some text that was copied directly out of Word. The `text/html` 
   mime type row would reveal any markup that is included in the clipboard contents.
   It’s likely even more verbose than what the classic editor accepted.
 * I will add that the block editor “sanitizes” pasted content from Google Docs/
   Word pretty well, so might be another workflow option to explore.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] No se ve el titulo](https://wordpress.org/support/topic/no-se-ve-el-titulo/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/no-se-ve-el-titulo/#post-18177299)
 * Hi, [@fabianmoreno](https://wordpress.org/support/users/fabianmoreno/) — I can’t
   reproduce this issue with WP 6.6.2 + CE 1.6.7 ([test in Playground](https://playground.wordpress.net/?php=8.2&wp=6.6&networking=yes&language=es_ES&plugin=classic-editor&url=%2Fwp-admin%2Fpost.php%3Fpost%3D1%26action%3Dedit)).
 * Have you tried disabling other plugins to see if any of them could be affecting
   the post screen? See the [Common Classic Editor errors](https://wordpress.org/support/topic/common-classic-editor-errors-and-how-to-fix-them/)
   post for some troubleshooting tips.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Inline translation doesn’t work properly](https://wordpress.org/support/topic/inline-translation-doesnt-work-properly/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/inline-translation-doesnt-work-properly/#post-18177284)
 * Hey, [@krstarica](https://wordpress.org/support/users/krstarica/) — The fix noted
   by [@psykro](https://wordpress.org/support/users/psykro/) shipped today in [Classic Editor](https://wordpress.org/plugins/classic-editor/)
   1.6.7. Please install the update and let us know if it doesn’t resolve the issue
   for you.
 * Marking this issue as resolved, but can reopen if it didn’t work.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Help pls ASAP](https://wordpress.org/support/topic/help-pls-asap/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/help-pls-asap/#post-18177236)
 * In addition to the [WP 6.7.1 release](https://wordpress.org/news/2024/11/wordpress-6-7-1-maintenance-release/),
   [Classic Editor](https://wordpress.org/plugins/classic-editor/) 1.6.7 was just
   released, which further refines the fix until WP 6.7.2 (estimated for January).
   Please try out the plugin update and let us know if it doesn’t resolve the issue
   for you.
 * Marking this issue as resolved for now.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Most Used Post Categories not saving](https://wordpress.org/support/topic/most-used-post-categories-not-saving/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/most-used-post-categories-not-saving/page/2/#post-18177229)
 * [Classic Editor](https://wordpress.org/plugins/classic-editor/) 1.6.7 was just
   released, which further refines the fix. Please try out the update and let us
   know if it doesn’t resolve the issue for you.
 * Marking this issue as resolved for now.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Adding Categories Not Chosen 6.7.1](https://wordpress.org/support/topic/adding-categories-not-chosen-6-7-1/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/adding-categories-not-chosen-6-7-1/#post-18177212)
 * [@galbaras](https://wordpress.org/support/users/galbaras/), [Classic Editor](https://wordpress.org/plugins/classic-editor/)
   1.6.7 was just released. Please give it a spin and let us know if it doesn’t 
   resolve the issue for you.
 * Per the [latest schedule update](https://make.wordpress.org/core/2024/12/02/summary-dev-chat-november-27-2024/),
   WP 6.7.2 isn’t planned until mid- to late-January. This issue wasn’t classed 
   as immediately urgent due to it being addressable through the Classic Editor 
   plugin, which the majority of affected users have installed.
 * Marking this issue as resolved for now.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Selecting Category Problem](https://wordpress.org/support/topic/selecting-category-problem/)
 *  [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 6 months ago](https://wordpress.org/support/topic/selecting-category-problem/#post-18153003)
 * Hi, [@marema29](https://wordpress.org/support/users/marema29/), and thank you
   for the report! Others have reported similar issues today.
 * There is a known issue selecting categories when Classic Editor is active. One
   workaround that could help would be to use the post list screen’s “Quick Edit”
   feature, which doesn’t appear to be affected by this newly introduced bug in 
   my testing.
 * More information on the bug and in-progress fix can be found at [https://core.trac.wordpress.org/ticket/62504](https://core.trac.wordpress.org/ticket/62504).
   If this looks like the same issue, feel free to mark this as resolved and watch
   for an update soon.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Safari 18.0 Breaking Classic Editor](https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/page/2/#post-18094590)
 * Thanks, everyone, for pitching in and helping each other!
 * And yes, just confirming here that [Classic Editor](https://wordpress.org/plugins/classic-editor/)
   enables the fix, and is compatible with [Advanced Editor Tools](https://wordpress.org/plugins/tinymce-advanced/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Safari 18.0 Breaking Classic Editor](https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/#post-18041914)
 * The Safari 18.0 workaround has been officially released in the plugin directory:
   [https://wordpress.org/plugins/classic-editor/](https://wordpress.org/plugins/classic-editor/#developers).
 * Thank you, everyone, for your testing! I’ll mark this topic resolved.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Not able to use Insert Link in Visual Editor](https://wordpress.org/support/topic/not-able-to-use-insert-link-in-visual-editor/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/not-able-to-use-insert-link-in-visual-editor/#post-18041901)
 * The Ned Flanders quote is quite appropriate! Are you able to change the theme
   or spin up a copy of the site in a staging environment? Are there any other sites
   with the same host or client that this happens to?
 * We’ll leave this topic open for more reproduction testing, and perhaps someone
   else with the same issue may discover additional info to share.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Classic Editor not working with WidsmLabs Instructor](https://wordpress.org/support/topic/classic-editor-not-working-with-widsmlabs-instructor/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/classic-editor-not-working-with-widsmlabs-instructor/#post-18041880)
 * Gotcha. Hopefully the other plugins’ authors can extend backward compatibility
   support for the classic editor 🤞🏻 I’ll close this topic for now.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Classic Editor not working with WidsmLabs Instructor](https://wordpress.org/support/topic/classic-editor-not-working-with-widsmlabs-instructor/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/classic-editor-not-working-with-widsmlabs-instructor/#post-18041711)
 * Yes, those options are only available when the plugin is active. If saving with
   those settings doesn’t subsequently resolve the issues with the other plugins,
   then unfortunately my idea of the workaround doesn’t pan out ☹️. It will be up
   to those plugin authors to resolve the conflict when the old editor is enabled.
   It was worth a try!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Classic Editor] Safari 18.0 Breaking Classic Editor](https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/)
 *  Plugin Contributor [Brian Alexander](https://wordpress.org/support/users/ironprogrammer/)
 * (@ironprogrammer)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/#post-18039806)
 * Hi, all 👋🏻 As [discussed in the related Trac issue](https://core.trac.wordpress.org/ticket/62082#comment:14),
   a workaround for [this issue](https://github.com/WordPress/classic-editor/issues/220)
   has been added to the plugin, and it would be great if you could **help by testing**
   to confirm it works with Safari 18.0 (and perhaps a confidence check with other
   browsers under macOS Sequoia). Please share your results on [the issue in Github](https://github.com/WordPress/classic-editor/issues/220)
   🙏🏻
 * You can test the fix by [downloading a zip of trunk](https://github.com/WordPress/classic-editor/archive/refs/heads/trunk.zip)
   and updating locally, or directly in the browser using this [Playground test link](https://playground.wordpress.net/?blueprint-url=https://gist.githubusercontent.com/ironprogrammer/ce478ac9f2beeda5cd28e43796fbacbc/raw/158980c2b5aac5b422367b397cbf1cf225f2fdfb/blueprint.json).
   Thanks!

Viewing 15 replies - 1 through 15 (of 105 total)

1 [2](https://wordpress.org/support/users/ironprogrammer/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/ironprogrammer/replies/page/3/?output_format=md)…
[5](https://wordpress.org/support/users/ironprogrammer/replies/page/5/?output_format=md)
[6](https://wordpress.org/support/users/ironprogrammer/replies/page/6/?output_format=md)
[7](https://wordpress.org/support/users/ironprogrammer/replies/page/7/?output_format=md)
[→](https://wordpress.org/support/users/ironprogrammer/replies/page/2/?output_format=md)