I guess what you are saying is that it then ‘exports’ the wrong system’s xml (I’m not familiar with the plugin) ? Ideally the plugin itself should be including/using the code rather in such a way so that it still knows the context/system in which it is being used irrespective of where the code is … Read more
You can do that, but you shouldn’t: Keep the global namespace clean. Each name in the global namespace is a collision candidate. Making a variable global, a constant or a function increases the likelihood of a collision, no matter how good your prefixes are. Constants are the slowest global types. Yes, that’s micro-optimization, but why … Read more
The WordPress directory path is available in the constant ABSPATH. Be aware this is not related to the wp-content directory. The constant WP_CONTENT_DIR could be set to exactly the same value. Or another directory on the same level where WP_CONTENT_URL is another domain name. There doesn’t even have to be a wp-content equivalent: themes, plugins, … Read more
So in the old days when WordPress updated you got the whole shebang and deleting Akismet after every time was deadly boring. Things had slightly improved since then (partially driven by minimizing traffic it takes to serve update to everyone), but process also got more complicated. Now there are multiple versions of update archive that … Read more
why would ABSPATH not get defined
You can access the blog ID you are on by global $blog_id; and then you can use that how you want it to work.
You can’t alter a constant once it is defined. That is how PHP works. Don’t fight it. The good news is that you should not be using a constant at all. Use options. // get your value // the second parameter is the default $enable_paypal = get_option(‘enable_paypal’,true); // set your value based on, I assume, … Read more
You should not put any defines in the end of the wp_config.php it is actually explicitly stated in it 😉 Every define you add should be above the line saying /* That’s all, stop editing! Happy blogging. */ Anything after that will have impact only after wordpress had finished to process the request
You can read up the source code of theme.php where get_stylesheet_directory_uri() is defined, inside you’ll see a str_replace() wich is consuming additional resources on each request. The best way to avoid this is to define a variable or constant that contains the path. In that case it is only called once. https://core.trac.wordpress.org/browser/tags/4.3.1/src/wp-includes/theme.php#L0
Defining constants on the global scope instead of using WordPress hooks, the first plugin loaded (See answer linked by Kero) will get the chance to define the constant. However, you could use some of the API hooks in your plugin, the earliest one possible is plugins_loaded, and then you can set priorities for the callbacks … Read more