Brian Alexander
Forum Replies Created
-
Forum: Plugins
In reply to: [Classic Editor] Classic Editor adds extra classes to tagsBuilding on @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/. There are some testing instructions on that thread that might help reveal where the additional markup is coming from.
Forum: Plugins
In reply to: [Classic Editor] No se ve el tituloWhen 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:
Forum: Plugins
In reply to: [Classic Editor] remove default font-weightHi, @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 and paste in some text that was copied directly out of Word. The
text/htmlmime 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
In reply to: [Classic Editor] No se ve el tituloHi, @fabianmoreno — I can’t reproduce this issue with WP 6.6.2 + CE 1.6.7 (test in Playground).
Have you tried disabling other plugins to see if any of them could be affecting the post screen? See the Common Classic Editor errors post for some troubleshooting tips.
Forum: Plugins
In reply to: [Classic Editor] Inline translation doesn’t work properlyHey, @krstarica — The fix noted by @psykro shipped today in 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
In reply to: [Classic Editor] Help pls ASAPIn addition to the WP 6.7.1 release, 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
In reply to: [Classic Editor] Most Used Post Categories not savingClassic 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
In reply to: [Classic Editor] Adding Categories Not Chosen 6.7.1@galbaras, 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, 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
In reply to: Selecting Category ProblemHi, @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. If this looks like the same issue, feel free to mark this as resolved and watch for an update soon.
Forum: Plugins
In reply to: [Classic Editor] Safari 18.0 Breaking Classic EditorThanks, everyone, for pitching in and helping each other!
And yes, just confirming here that Classic Editor enables the fix, and is compatible with Advanced Editor Tools.
Forum: Plugins
In reply to: [Classic Editor] Safari 18.0 Breaking Classic EditorThe Safari 18.0 workaround has been officially released in the plugin directory: https://wordpress.org/plugins/classic-editor/.
Thank you, everyone, for your testing! I’ll mark this topic resolved.
Forum: Plugins
In reply to: [Classic Editor] Not able to use Insert Link in Visual EditorThe 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
In reply to: [Classic Editor] Classic Editor not working with WidsmLabs InstructorGotcha. Hopefully the other plugins’ authors can extend backward compatibility support for the classic editor 🤞🏻 I’ll close this topic for now.
Forum: Plugins
In reply to: [Classic Editor] Classic Editor not working with WidsmLabs InstructorYes, 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
In reply to: [Classic Editor] Safari 18.0 Breaking Classic EditorHi, all 👋🏻 As discussed in the related Trac issue, a workaround for this issue 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 🙏🏻
You can test the fix by downloading a zip of trunk and updating locally, or directly in the browser using this Playground test link. Thanks!