Easily load site specific functions, scripts and CSS files into your site without editing your theme's functions.php or other source files.
A standard WordPress install is incredibly powerful and flexible. For a lot of people, WordPress out of the box plus one of the stock WordPress themes is enough. But the possibilities for customization are endless; you can add plugins and other themes. Sometimes these do just what you want. Sometimes you need to ... tweak WordPress. A very high proportion of the customization advice you'll find on the web starts with these lines ... add the following to the end of your theme's
functions.php or even worse, advises that you modify the source code of your theme or your plugins. This is bad for many reasons:
functions.phpmakes theme specific customizations; change your theme and your customizations will no longer get loaded.
WordPress doesn't yet support a way for site specific customizations to be made and loaded without touching theme, plugin or core files; that's what this plugin is for. When WordPress does support such a way, this plugin will thankfully be obsolete.
In short, very easily. But before you read any further, take a look at Asking For WordPress Plugin Help And Support Without Tears before firing off a question. In order of preference, you can ask a question on the WordPress support forum; this is by far the best way so that other users can follow the conversation. You can ask me a question on Twitter; I'm @vicchi. Or you can drop me an email instead. I can't promise to answer your question but I do promise to answer and do my best to help.
By default the plugin installs with no customizations loading; you'll need to enable them as you need. See the Installation section for more details on how to do this.
To answer the first part of this question, it's probably best to start at the beginning and get a solid grounding in these tools and technologies before you start making customizations.
To answer the second part of this question, if you don't know what customizations you need then this plugin probably isn't for you.
WP Customizer looks in each of the directories that you've configured (or left as the default) for each type of customization to load. To stop a specific file loading, simply rename it so that the first character of the file name is the underscore (
_) character and that file will be skipped over when the plugin is looking for files to load. If other words, just rename
Yes you can. Take a look at the Filter Support and Usage section for information on how to use the plugin's filters to do all of this and more. In fact, by using the plugin's filters you can specify every single option that the WordPress
wp_enqueue_style API calls accept.
There's a couple of things that might be happening here. Your file type might be incorrect; your path might not exist or be readable, your file might not exist or be readable or your file might be disabled (starting with an '_'). The plugin's Debug tab is designed to help diagnose this sort of thing. The Debug tab performs a dry run, without actually loading any files, and checks that files and directories exist and are readable. If you see any entries highlighted in yellow then this will indicate that a file is probably disabled. If you see any entries highlighted in red then this will indicate that a file or directory either doesn't exist or is not able to be read.
This is unlikely but always possible. A customization file with errors in it can have unforeseen consequences. If this does happen firstly disable all your customization files by renaming them to have an underscore (
_) as the first character. Hopefully things will be OK again. Now rename each customization file back by removing the underscore, one by one, to narrow down which one breaks things. Now would also be a good time to define
WP_DEBUG in your
wp-config.php file to get some helpful error messages in your PHP log file.
For the cases of expired felines or sudden precipitation, this is way outside what a WordPress plugin can do; it's probably an unfortunate coincidence.
I'm British too and yes, it's spelt customisation over here, not customization. As both Oscar Wilde and George Bernard Shaw are quoted as saying '(Britain and America are) two nations, separated by a common language'. By default, WP Customizer uses American English, but if you're British and you want British English instead, simply define
WP_LANG to have a value of
en_GB in your site's
wp-config.php and WP Customizer will automagically become WP Customiser.
WordPress and this plugin use the gettext tools to support internationalisation. The source file containing each string that needs to be translated ships with the plugin in
wp-customizer/lang/src/wp-customizer.po. See the I18n for WordPress Developers page for more information or get in touch for help and hand-holding.
Totally; this plugin is licensed under the GNU General Public License v2 (GPLV2). See http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt for the full license terms.