Title: WP Customizer Author: vicchi Published: Òkúdù 5, 2013 Last modified: Bélú 9, 2017 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/wp-customizer/assets/banner-772x250.png?rev=723003) Plugin yìí **kò tíì ṣe àyẹ̀wò pẹ̀lú àwọn ìtújáde mẹ́ta pàtàkì tó kẹ́yìn ti WordPress**. Ó lè jẹ́ pé a kò tọ́jú tàbí ṣe àtìlẹ́yìn fún un mọ́, ó sì lè ní àwọn ọ̀ràn ìbámu nígbà tí a bá lò ó pẹ̀lú àwọn ẹ̀yà WordPress tuntun. ![](https://s.w.org/plugins/geopattern-icon/wp-customizer_f7f3e9.svg) # WP Customizer Láti ọwọ́ [vicchi](https://profiles.wordpress.org/vicchi/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/wp-customizer.1.0.2.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/wp-customizer/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/wp-customizer/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/wp-customizer/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/wp-customizer/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/wp-customizer/) ## Àpèjúwe This plugin allows you to manage and load site specific functions, scripts and CSS files into your WordPress site without the need to edit your themeÌtumọ̀ Yorùbá:’ s `functions.php` or any other source file. Settings and options include: 1. Choose the type of customization you want to load; functions, scripts, CSS in any combination. 2. Choose where you want the customizations to load; in the WordPress front-end, in the WordPress admin screens or both. 3. Choose where you want to store your customization files, without the need to add to or modify your themeÌtumọ̀ Yorùbá: ’s or your pluginÌtumọ̀ Yorùbá: ’s source files. ### Filter Support And Usage WP Customizer supports multiple filters; the pluginÌtumọ̀ Yorùbá: ’s filters allow you to * modify the set of functions files that are about to be loaded * modify the set of script files that are about to be loaded * modify the characteristics of each script file that is about to be loaded and which will be passed as arguments to [`wp_enqueue_script`](https://codex.wordpress.org/Function_Reference/wp_enqueue_script) * modify the set of CSS files that are about to be loaded * modify the characteristics of each CSS file that is about to be loaded and which will be passed as arguments to [`wp_enqueue_style`](https://codex.wordpress.org/Function_Reference/wp_enqueue_style) Each filter will be only be called if the customization type is enabled in the pluginÌtumọ̀ Yorùbá: ’s options; if a customization type is enabled but no files are found to be loaded, the filter will still be called but will be passed an empty argument. As with all WordPress filters, any filter hook function should either return the modified argument or the original argument if no modification were made. #### wp_customizer_functions, wp_customizer_admin_functions, wp_customizer_common_functions The _functions_ filters are called when preparing to load the list of front-end functions (`wp_customizer_functions`), of admin functions (`wp_customizer_admin_functions`) and of common functions (`wp_customizer_common_functions`). The arguments that each filter hook function receives is identical in all cases. The filter hook function takes a single argument which is an array of file names. _Example:_ Prevent all function files from loading by returning an empty file list. ``` add_filter('wp_customizer_functions', 'function_handler', 10, 1); function function_handler($files) { // $files = array( // array( // 'file' => (absolute path of function file) // ), // array(...) // ); return array(); } ``` #### wp_customizer_scripts, wp_customizer_admin_scripts, wp_customizer_common_scripts The _scripts_ filters are called when preparing to load the list of front-end scripts(` wp_customizer_scripts`), of admin scripts (`wp_customizer_admin_scripts`) and of common scripts (`wp_customizer_common_scripts`). The arguments that each filter hook function receives is identical in all cases. The filter hook function takes a single argument which is an array of file details. _Example:_ Add jQuery as a dependency to all scripts and enable each script to load in the postÌtumọ̀ Yorùbá: ’s footer. ``` add_filter('wp_customizer_scripts', 'script_handler', 10, 1); function script_handler($files) { // $files = array( // array( // 'file' => (absolute path of script file), // 'handle' => (auto-generated handle for script), // 'src' => (URL of script file), // 'deps' => (dependencies, defaults to an empty array), // 'ver' => (version, defaults to false), // 'in_footer' => (load in footer, defaults to false), // ), // array(...) // ); foreach ($files as $file) { $file['deps'] = array('jquery'); $file['in_footer'] = true; } return $files; } ``` #### wp_customizer_css, wp_customizer_admin_css, wp_customizer_common_css The _CSS_ filters are called when preparing to load the list of front-end CSS (` wp_customizer_css`), of admin CSS (`wp_customizer_admin_css`) and of common CSS (` wp_customizer_common_css`). The arguments that each filter hook function receives is identical in all cases. The filter hook function takes a single argument which is an array of file details. _Example:_ Override the media type for all CSS files to use the `screen` media type. ``` add_filter('wp_customizer_css', 'css_handler', 10, 1); function css_handler($files) { // $files = array( // array( // 'file' => (absolute path of css file), // 'handle' => (auto-generated handle for CSS), // 'src' => (URL of CSS file), // 'deps' => (dependencies, defaults to an empty array), // 'ver' => (version, defaults to false), // 'media' => (media type, defaults to 'all') // ), // array(...) // ); foreach ($files as $file) { $file['media'] = 'screen'; } return $files; } ``` ## Àwọn àwòrán ìbòjú * [[ * Settings and Options: Functions Tab * [[ * Settings and Options: Scripts Tab * [[ * Settings and Options: CSS Tab * [[ * Settings and Options: Colophon Tab * [[ * Settings and Options: Debug Tab * [[ * Settings and Options: Functions Tab with Contextual Help ## Ìgbéwọlẹ̀ 1. You can install WP Customizer automatically from the WordPress admin panel. From the Dashboard, navigate to the _Plugins / Add New_ page and search for _“WP Customizer”_ and click on the _“Install Now”_ link. 2. Or you can install WP Customizer manually. Download the plugin Zip archive and uncompress it. Copy or upload the `wp-customizer` folder to the `wp-content/plugins` folder on your web server. 3. Activate the plugin. From the Dashboard, navigate to Plugins and click on the _“ Activate”_ link under the entry for _WP Customiser_. 4. Prepare your customization files. By default, WP Customizer looks for front-end functions in a directory named `functions`, for front-end scripts in a directory named `scripts` and for front-end CSS files in a directory named `css`. 5. Admin screen customizations are placed in a similar set of directories, prefixed with `admin_`, as in `admin_functions`, `admin_scripts` and `admin_css`. 6. Customizations common to both the front-end and the admin screens are placed in directories prefixed with `common_`, as in `common_functions`, `common_scripts` and `common_css`. 7. You can either create the default directories and place your customization files in them or create your own directory hierarchy. 8. Now you can configure the loading of each type of supported customization. From the Dashboard navigate to _Settings / WP Customizer_ and enable loading of the customization files as you require. 9. If you choose to use a non-default set of directory name, you should ensure the pluginÌtumọ̀ Yorùbá: ’s options are updated to reflect this. ## FAQ Installation Instructions 1. You can install WP Customizer automatically from the WordPress admin panel. From the Dashboard, navigate to the _Plugins / Add New_ page and search for _“WP Customizer”_ and click on the _“Install Now”_ link. 2. Or you can install WP Customizer manually. Download the plugin Zip archive and uncompress it. Copy or upload the `wp-customizer` folder to the `wp-content/plugins` folder on your web server. 3. Activate the plugin. From the Dashboard, navigate to Plugins and click on the _“ Activate”_ link under the entry for _WP Customiser_. 4. Prepare your customization files. By default, WP Customizer looks for front-end functions in a directory named `functions`, for front-end scripts in a directory named `scripts` and for front-end CSS files in a directory named `css`. 5. Admin screen customizations are placed in a similar set of directories, prefixed with `admin_`, as in `admin_functions`, `admin_scripts` and `admin_css`. 6. Customizations common to both the front-end and the admin screens are placed in directories prefixed with `common_`, as in `common_functions`, `common_scripts` and `common_css`. 7. You can either create the default directories and place your customization files in them or create your own directory hierarchy. 8. Now you can configure the loading of each type of supported customization. From the Dashboard navigate to _Settings / WP Customizer_ and enable loading of the customization files as you require. 9. If you choose to use a non-default set of directory name, you should ensure the pluginÌtumọ̀ Yorùbá: ’s options are updated to reflect this. Why should I use this plugin? 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Ìtumọ̀ Yorùbá: ’ll find on the web starts with these lines … _add the following to the end of your themeÌtumọ̀ Yorùbá: ’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: * Editing your themeÌtumọ̀ Yorùbá: ’s `functions.php` makes _theme specific_ customizations; change your theme and your customizations will no longer get loaded. * When your theme and plugins get updated youÌtumọ̀ Yorùbá: ’ll find all your careful hand crafted customizations get overwritten and lost. * A lot of theme and plugin authors wonÌtumọ̀ Yorùbá: ’t offer support for changes you might have made to the source code. * Your customizations might work; but you might also inadvertently make some other changes which will stop things working. WordPress doesnÌtumọ̀ Yorùbá: ’t yet support a way for site specific customizations to be made and loaded without touching theme, plugin or core files; thatÌtumọ̀ Yorùbá:’ s what this plugin is for. When WordPress does support such a way, this plugin will thankfully be obsolete. How do I get help or support for this plugin? In short, very easily. But before you read any further, take a look at [Asking For WordPress Plugin Help And Support Without Tears](http://www.vicchi.org/codeage/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](https://wordpress.org/support/plugin/wp-customizer); this is by far the best way so that other users can follow the conversation. You can ask me a question on Twitter; IÌtumọ̀ Yorùbá: ’m [@vicchi](http://twitter.com/vicchi). Or you can drop me an email instead. I canÌtumọ̀ Yorùbá: ’t promise to answer your question but I do promise to answer and do my best to help. Is there a web site for this plugin? Absolutely. Go to the [WP Customizer home page](http://www.vicchi.org/codeage/wp-customizer/) for the latest information. ThereÌtumọ̀ Yorùbá: ’s also the official [WordPress plugin repository page](https://wordpress.org/extend/plugins/wp-customizer/) and the [source for the plugin is on GitHub](http://vicchi.github.com/wp-customizer/) as well. IÌtumọ̀ Yorùbá: ’ve installed this plugin but it doesnÌtumọ̀ Yorùbá: ’t do anything? By default the plugin installs with no customizations loading; youÌtumọ̀ Yorùbá:’ ll need to enable them as you need. See the _Installation_ section for more details on how to do this. I donÌtumọ̀ Yorùbá: ’t know PHP or JavaScript or jQuery or CSS; what customizations do I need? To answer the first part of this question, itÌtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’t know what customizations you need then this plugin probably isnÌtumọ̀ Yorùbá: ’t for you. I donÌtumọ̀ Yorùbá: ’t want to load all of the functions, scripts or CSS files I have; can I select which ones get loaded? WP Customizer looks in each of the directories that youÌtumọ̀ Yorùbá: ’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 `foo.php` to `_foo.php`. IÌtumọ̀ Yorùbá: ’m a WordPress power user and want to specify things like dependencies for my scripts or make my CSS customizations load in the page footer; can I do this? Yes you can. Take a look at the _Filter Support and Usage_ section for information on how to use the pluginÌtumọ̀ Yorùbá: ’s filters to do all of this and more. In fact, by using the pluginÌtumọ̀ Yorùbá: ’s filters you can specify every single option that the WordPress [`wp_enqueue_script`](https://codex.wordpress.org/Function_Reference/wp_enqueue_script) and [`wp_enqueue_style`](https://codex.wordpress.org/Function_Reference/wp_enqueue_style) API calls accept. IÌtumọ̀ Yorùbá: ’ve enabled functions/scripts/css and supplied a path but my function/ script/css isnÌtumọ̀ Yorùbá: ’t loading? ThereÌtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’t exist or is not able to be read. WP Customizer has crashed my website/killed my cat/made it rain; what do I do? 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Ìtumọ̀ Yorùbá: ’s probably an unfortunate coincidence. What is all this talk of “customization”; IÌtumọ̀ Yorùbá: ’m British and itÌtumọ̀ Yorùbá: ’s spelt “customisation” … ? IÌtumọ̀ Yorùbá: ’m British too and yes, itÌtumọ̀ Yorùbá: ’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_‘](http://www1c.btwebworld.com/quote-unquote/p0000149.htm). By default, WP Customizer uses American English, but if youÌtumọ̀ Yorùbá: ’re British and you want British English instead, simply define `WP_LANG` to have a value of` en_GB` in your siteÌtumọ̀ Yorùbá: ’s `wp-config.php` and WP Customizer will automagically become WP Customiser. WP Customizer isnÌtumọ̀ Yorùbá: ’t available in my language; can I submit a translation? 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](https://codex.wordpress.org/I18n_for_WordPress_Developers) page for more information or get in touch for help and hand-holding. I want to amend/hack/augment this plugin; can I do this? 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. ## Àwọn àgbéyẹ̀wò ![](https://secure.gravatar.com/avatar/e0331ac4613a00df87c3bb71d817a01b0eb244a89e4b2e4ad90b3c44d229884b? s=60&d=retro&r=g) ### 󠀁[Superb Plugin Ìtumọ̀ Yorùbá: – well recomended](https://wordpress.org/support/topic/superb-plugin-well-recomended/)󠁿 [Venutius](https://profiles.wordpress.org/venutius/) Ọwẹ́wẹ̀ 27, 2016 ItÌtumọ̀ Yorùbá: ’s been three years since this was last updated and itÌtumọ̀ Yorùbá:’ s still going strong, I really hope the author will keep up its development. I use this plugin to change all kinds of CSS features that otherwise IÌtumọ̀ Yorùbá: ’ d have no clue how to change, the interface is simple yet incredibly powerfull, if it stops working I@ll be in big trouble! [ Ka gbogbo àwọn àgbéyẹ̀wò 2 ](https://wordpress.org/support/plugin/wp-customizer/reviews/) ## Àwọn Olùkópa & Olùgbéejáde “WP Customizer” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ vicchi ](https://profiles.wordpress.org/vicchi/) [Túmọ̀ “WP Customizer” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/wp-customizer) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/wp-customizer/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/wp-customizer/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/wp-customizer/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/wp-customizer/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà The current version is 1.0.1 (2013.09.18) #### 1.0.1 * Release 2013.09.18 * Fixed: Annoying Markdown syntax in plugin overview text. * Fixed: Pointer help file is now included; this was missing in v1.0.0. * Added: Pointer text for the Debug tab. #### 1.0.0 * Released 2013.05.29 * First version of WP Customizer released ## Àkójọpọ̀ Meta * Ẹ̀yà **1.0.2** * Ìgbàgbọ́hùn tó kẹ́yìn **ọdún 9 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **20+** * Ẹ̀yà WordPress ** 4.8 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **4.8.28** * Èdè * [English (US)](https://wordpress.org/plugins/wp-customizer/) * Àwọn àmì * [customise](https://yor.wordpress.org/plugins/tags/customise/)[customize](https://yor.wordpress.org/plugins/tags/customize/) [functions](https://yor.wordpress.org/plugins/tags/functions/)[scripts](https://yor.wordpress.org/plugins/tags/scripts/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/wp-customizer/advanced/) ## Àwọn ìbò 5 lára àwọn ìràwọ̀ 5. * [ 2 5-star reviews ](https://wordpress.org/support/plugin/wp-customizer/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/wp-customizer/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/wp-customizer/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/wp-customizer/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/wp-customizer/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/wp-customizer/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/wp-customizer/reviews/) ## Àwọn Olùkópa * [ vicchi ](https://profiles.wordpress.org/vicchi/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/wp-customizer/) ## Ṣe ìtọrẹ Ṣé o fẹ́ ṣe àtìlẹ́yìn fún ìlọsíwájú plugin yìí? [ Ṣe ìtọrẹ sí plugin yìí ](http://www.vicchi.org/codeage/donate/)