[wp-hackers] plugins_url function
phillip.lord at newcastle.ac.uk
Thu Dec 15 10:25:42 UTC 2011
Jeremy Clarke <jer at simianuprising.com> writes:
> I hit this issue as well. The best solution I've found is to use some code
> similar to what John B posted that filters plugins_url and targets the
> specific predicable results of __FILE__ on the given system.
It would be a good solution, if I didn't control the plugin or if I
really needed the symlink, I think.
> One optimization I'd add is to use the mu-plugins folder rather than normal
> /plugins/. This way the plugin is always active on that site without having
> any references to it in the database (so that when you copy the db to your
> local dev site the plugin isn't missing). It also just makes sense to have
> it there, as it's party of the 'hard' setup of the site rather than the
> 'soft' config.
I didn't know this -- actually, it's very useful for me, for an entirely
More information about the wp-hackers