[wp-trac] Re: [WordPress Trac] #7709: 'content_url' not pluggable
WordPress Trac
wp-trac at lists.automattic.com
Tue Sep 9 00:57:57 GMT 2008
#7709: 'content_url' not pluggable
----------------------+-----------------------------------------------------
Reporter: krudolph | Owner: anonymous
Type: defect | Status: new
Priority: low | Milestone: 2.8
Component: General | Version: 2.7
Severity: minor | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Comment (by DD32):
> Well, since the constant is set in WP's core there's no chance of that.
Reading the wp-config.php file is definitely required before plugins and
themes can be loaded
Sorry, It was late :/ I was thinking "URL's are in defines, Dir's are in
functions"..
By moving them after the plugins are loaded, i was refering to the default
values, with the thought "If a user defines it manually, thats what they
want full stop" in the back of my mind.
> I suppose you mean content_url (since there's no content_dir function
anywhere in the code base)? As I wrote, its content cannot be filtered
Ah yeah.. I meant the content_url() and family, some plugins will use the
constants, others will use the functions though, so be warned there..
> that's what I meant by “not pluggable”).
Sorry, "pluggable" means Function-replace, While "filtered" means having a
filter available to me, thats probably what got me a bit confused.
Adding a filter to the *_url() functions would be a good move IMO, but, as
i said before, not all plugins use it, and a fair few are going to rely on
the constants directly.
--
Ticket URL: <http://trac.wordpress.org/ticket/7709#comment:3>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list