Hot answers tagged wp-settings.php
There is not much to it, really. During the loading of WordPress engine wp-settings.php file is processed. Among other things this files calls wp_get_active_and_valid_plugins() function, that gets list of activated (through admin interface) plugins from active_plugins option (stored in database). For each active plugin its main file (the one holding plugin ...
The WP plugin architecture is event based and is very simple: Events are attached using add_action() and add_filter(). Events are triggered using do_action() and apply_filters(). All these functions are found in wp-includes/plugin.php More information can be found here: http://codex.wordpress.org/Plugin_API For a "flow diagram" of sorts, see this site: ...
You don’t need a separate rule in your .htaccess. Add … define( 'WP_CONTENT_DIR', 'YOUR_LOCAL_PATH' ); define( 'WP_CONTENT_URL', 'YOUR_PUBLIC_PATH' ); … to your wp-config.php. Do not write into wp-settings.php. This file will be overwritten during the next update – never touch a core file.
The easiest way would be to look at the code of Si Contact Form (since it already does what you want) and use the same kind of system. Shortly, you'll need methods to do the following: Create an XML (or other format) document of your theme options. Save/Export the XML document. Import the XML document (There's no point in exporting if you can't import it ...
Consider everything that comes with a vanilla WordPress installation a core file. Core files will be overwritten on updates, so it's not safe to edit them. E.g. wp-config.php isn't a core file, because the vanilla installation comes only with the sample version of that file.
With a stock WordPress install, you cannot insert server side code like PHP directly into a post, only HTML-compatible text. Using the [code][/code] shortcode only outputs what is inside as PRE and CODE elements of HTML, useful for showing code to your readers. In general, it is a bad idea to put code directly into a post. Thank being said, there are ...
If you've already got a solution that works using FeedPress you might as well stay with that, there isn't a particularly clean way of aggregating multisite posts into a single blog. One alternative is to use the Sitewide Tags plugin, but given what you want to do, you should probably stay with what's working.
Only top voted, non community-wiki answers of a minimum length are eligible