[wp-trac] [WordPress Trac] #62361: Set filter "activate_tinymce_for_media_description" to "true" is breaking meadia_descripton by running it through "htmlspecialchars()"
WordPress Trac
noreply at wordpress.org
Thu Nov 14 11:16:55 UTC 2024
#62361: Set filter "activate_tinymce_for_media_description" to "true" is breaking
meadia_descripton by running it through "htmlspecialchars()"
-----------------------------------------+------------------------
Reporter: dagobert24 | Owner: joedolson
Type: defect (bug) | Status: accepted
Priority: normal | Milestone: 6.8
Component: Media | Version: 6.6.2
Severity: normal | Resolution:
Keywords: has-patch 2nd-opinion close | Focuses: ui
-----------------------------------------+------------------------
Comment (by dagobert24):
Replying to [comment:7 azaozz]:
> Frankly I think that the change from #60158 should be reverted. It
doesn't seem a good idea to add support for TinyMCE to the content of
attachment pages just to have paragraph tags. Seems that missing paragraph
tags there should be treated as a bug when using the (so called) Text
editor, `quicktags`. I think this used to work before.
Thank you for your opinion. I on the other hand don't think it should be
reverted. It was something I was waiting for for a long time not having to
use plain HTML tags only and hoping to get the style right or constantly
saving and looking at the changes on the page itself.
The idea of offering a plaintext textarea only for this made it basically
unusable for 95% of all WP users. In addition to the fact that the content
is basically a post directly connected to the picture itself.
> There are few reasons to remove this:
>
> - TinyMCE in WordPress is in "deep maintenance" mode meaning it is not
supported any more except for eventual security fixes.
Ok, I understand but it still in use and one can replace the tinymce by a
different editor. Removing the introduced hook will disable using any
editor completely (without major hoops by plugin creators maybe).
Actually this would rather lead to arguing for the complete functionallity
of the editor-set of the post page. I mean all features including
switching between text, classic editor and the new block editor. (Would be
great btw.)
> - The attachment pages are not used/shown any more. They are disabled by
default on new(er) installs.
Yes, this is true. Disabled does not meand removed and it certainly does
not mean depricated, does it? There are plenty installs still using this
feature, even of cause many others don't know or want to use it. There are
many option/feature disabled by default and these defaults only reflect
the WP product owners descisions and/or surveys about how WP users
normally configure their WP. E.g. most WP users don't want anyone to
register hence this option is disabled by default (not removed).
> Also the fact that this bug is being reported several months after this
functionality was introduced seems to signify there is very little
interest.
Sorry, but I have to disagree. This option/functionallity is not exposed
to the UI. Noone knows about it. Only if one searches for it you can find
it. Many already using the attachment page don't know this. No user
updating WP look at the changes.
It took me some efford too, even finding the right search phrase to
stumble upon it. Their is no plugin for this either. (I am workiing on one
right now and am only waiting that the fix is released.)
> Thinking this type of functionality is best left for plugins that will
also ensure attachment pages are used in the theme/at the front-end.
Without that this is useless.
Anyone turning on this feature will know that the theme needs to support
attachment pages. This is specially true because of the introduced
disabling of attachment paged by installation.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/62361#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list