[wp-hackers] Shortcodes and formatting

Xel xel at netgra.de
Mon Apr 7 19:56:36 GMT 2008

One should integrate something like the
both existing plugins into wordpress.
I speak about the one from Andrew (which I haven't tested) and the one I
wrote myselfe and which is availeable there:
( http://blog.netgra.de/shortcodes-loeschen for those who understand

Not much documentated by now anyway.

They won't be hard to integrate I think and it is better to give users the
possibility to decide which shortcodes should be ripped off than just
deleting content. No matter if you give them the option to turn it on or off
- maybe one has both: Death plugins AND handwritten stuff in [ and ] which
should stay readable.


2008/4/7, Duane Storey <duanestorey at gmail.com>:
> I see both sides of the debate, but I think having to rely on another
> plugin to clean up after other plugins is kind of weak.   Considering
> wordpress already parses the short codes and replaces them with output
> from the plugin, I think it's rather trivial to make Wordpress strip
> out shortcodes that aren't used.  Make it an option in the admin panel
> somewhere maybe.
> I have definitely turned off many plugins, including one that added
> markup (and I had that on enabled for at least 500 posts).  Thankfully
> the markup was in HTML comment tags so I didn't have to worry about
> it, but it would have been unrealistic for me to edit all those posts
> manually.
> On 4/7/08, Jeremy Clarke <jer at simianuprising.com> wrote:
> > On Sun, Apr 6, 2008 at 12:50 AM, Viper007Bond <viper at viper007bond.com>
> wrote:
> >  >  As for HTML comments, this just adds further complications to the
> code, can
> >  >  cause problems with some shortcodes, and is unnecessary for 99.9% of
> people
> >  >  as they won't be devactivating the plugins they use. For that 0.1%,
> Andrew
> >  >  has you covered.
> >
> >
> > Just for the record, I think a lot more than 0.1% of people have to
> >  turn off plugins if only because they break as part of regular
> >  WordPress core updates and the author isn't around or doesn't want to
> >  fix them. Viper, I'm glad you're expressing so much commitment towards
> >  your own plugins, but a lot of users don't know how to guess at which
> >  devs are going to be around a long time and which are just making a
> >  single release of something they built for themselves. I would also
> >  posit that many users, presented with an annoying situation like ghost
> >  tags from a disabled plugin, will just be annoyed rather than looking
> >  for yet *another* plugin to fix the problem (which itself will someday
> >  die, as all things do).
> >
> >  I have to admit I've lost the actual technical details being debated
> >  here, but +1 for any solution that allows shortcodes to be used inside
> >  <!-- -->, as that is how I definitely prefer things to work.
> >
> >
> >  --
> >  Jeremy Clarke | http://simianuprising.com
> >  Code and Design | http://globalvoicesonline.org
> >
> > _______________________________________________
> >  wp-hackers mailing list
> >  wp-hackers at lists.automattic.com
> >  http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list