[wp-trac] [WordPress Trac] #11394: Image shortcode

[WordPress Trac]

#11394: Image shortcode
-----------------------------+----------------------------------------------
 Reporter:  caesarsgrunt     |       Owner:                          
     Type:  feature request  |      Status:  new                     
 Priority:  normal           |   Milestone:  3.1                     
Component:  Media            |     Version:  2.9                     
 Severity:  normal           |    Keywords:  needs-patch dev-feedback
-----------------------------+----------------------------------------------

Comment(by Otto42):

 Replying to [comment:39 caesarsgrunt]:
 > Is the content of the post, as in the database, shown straight in feeds
 without being parsed at all? If it's parsed anyway then being shown in
 feeds isn't different from being shown on the site - but I don't actually
 know whether it is or not. (Out of interest, if it's not, what happens
 about embedded videos, galleries, etc?)

 It is parsed, but it doesn't necessarily need to be.

 > Why would you simply delete all shortcodes? Obviously, if you delete
 them, then what they represent won't be there anymore. Do you want your
 image tags to still be there if you delete all HTML too? If you remove all
 forms of formatting so you just have plain text? Where do you draw the
 line?

 I draw the line at having something that is only meaningful in the context
 of WordPress itself in my post content.

 In other words, <img src=...> has meaning in an actual standard.
 Shortcodes are part of no standard anywhere.

 > Besides, there is already a [gallery] shortcode. If you delete it; the
 images it represents won't be shown anymore. Why's that OK, when a
 shortcode for individual images isn't?

 I never said that it was okay. I dislike the use of [gallery]. I don't use
 it myself.

 I don't like shortcodes in general. They are non-standard, they require my
 content to be parsed through WordPress, and they blur the distinction
 between content and code too far, IMO. I'm okay with them, in general, as
 they usually don't carry particularly meaningful content. And when they
 do, it's in a plugin.

 But I don't want the core code doing that. I hate the idea of making my
 content dependent upon the code in WordPress itself, taking it out of my
 hands and putting it into the developers hands. It's a damned poor way of
 doing things.

 I don't want to upgrade and have the actual content on my site change just
 because some code got committed into a new update.

 > Maybe we should have an option to disable the shortcode - enable it for
 normal users who are more concerned about ease of use and the enhanced
 feature set which it helps to enable, and allow advanced users who are
 more concerned about direct data portability without using an exporter to
 disable the shortcode. What do you think of that concept?

 I'd rather it be opt-in only, not opt-out.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11394#comment:43>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software