[wp-hackers] [GSOC2010]WPmove [wpurl] tag replace

Piyush Mishra admin at oxymaniac.com
Thu Apr 8 18:37:50 UTC 2010


when talking on the single [wpurl] someone mentioned the delay coz of the
replace, now for the maybe_unserialize new function or for these
shortcodes... wont we have delays in each refresh?

On Thu, Apr 8, 2010 at 11:38 PM, Otto <otto at ottodestruct.com> wrote:

> Sorry, that should have been:
>
> add_shortcode('homeurl', create_function('', 'return home_url();'));
>
> My mistake.
>
> -Otto
>
>
>
> On Thu, Apr 8, 2010 at 1:07 PM, Otto <otto at ottodestruct.com> wrote:
> > On Thu, Apr 8, 2010 at 12:30 PM, Piyush Mishra <admin at oxymaniac.com>
> wrote:
> >> neat :) this helps in working for data now but what about the [wpurl]
> tag
> >> thing?
> >
> > Since you asked, I proposed something similar in trac a while back,
> > for different reasons:
> > http://core.trac.wordpress.org/ticket/11394#comment:20
> >
> > I would prefer something like contenturl, pluginurl, themeurl,
> > homeurl, siteurl, for the various URLs used throughout WordPress. Each
> > of these functions is basically a one-liner, actually. Here's the
> > entirety of the [homeurl] shortcode, for example:
> >
> > add_action('homeurl', create_function('', 'return home_url();'));
> >
> > Actually going through the content and replacing URLs with known
> > shortcodes might not be the greatest way to go about things, however.
> > But making it default to use them for that sort of thing, sure.
> >
> > -Otto
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Regards
Piyush Mishra


More information about the wp-hackers mailing list