New customizer feature with WordPress 4.7 and upward
Adding CSS without editing any theme CSS files
To change, add or tryout your custom CSS is a often called question in many support threads. The answers are at most only the CSS snippet you may add to solve your problem but not how to add because this part is very inconveenient. You can try it with the browser tools and if it works use your FTP client or the editor behind appearance. With WordPress 4.7 there is a elegant and quite easy way to add small inline CSS. Users can add custom CSS directly from WordPress admin area. This is super-easy and you would be able to see your changes with a live preview instantly.
There are many ways in the WordPress admin back-end go to the customizer.
WordPress provides with the customizer, a “live-preview” editor. You will see options which was implemented by you Theme. All options are change immediately while editing. That’s why it called the “Live-Preview” editor.
Changes will be available after applied
The customizer is opened with the left side panel and shows a bunch of options. One of this option panels is the tab “Additional CSS”. Click this tab.
The tab opens and show a large text box where you can add custom CSS selectors. And the customizer isn’t the customizer wouldn’t be added or changed CSS rules immediately shown while writhing at your site in the right side.
After you’re satisfied with your added CSS rules don’t forget to click on the “Save & Publish” button on the top of the left side.
This easy and fast method can’t solve all. So called “inline code” for CSS is also for smaller snippets good. As opposed to external added files, which was added once and cached by the browser, are made for large CSS code because the code’s logic is separated and better to update and maintain.
Now, the new added CSS selectors looks create within the head-area on the lowest position to override the other CSS.
Why is my WordPess widget not properly prepared for the new localization?
What is the slug of my WordPress plugin?
What is the slug of my WordPress plugin?
You don’t need any more fils in the language directory. All you need is to register and use translate.wordpress.org
In some cases you get this hint: “This plugin is not properly prepared for localization.”
You added the header with the Plugin Name, Author and Text Domain well. But this warning above isn’t extinguish. So you have to check the Text Domain. It is the slug of your PlugIn.
If you want to migrat your WordPress PlugIn translations and localizations to translate.wordpress.org
The slug of your PlugIn is the Url path of your WordPress repository or the Url path: ‘category-posts’.
The text domain is a unique identifier, which makes sure WordPress can distinguish between all loaded translations.
For translate.wordpress.org the plugin slug isn’t a name of a single PHP file or it isn’t a folder were your plugin is contained in! Translate.wordpress.org is more restricted to extinguish between all loaded translations as the linked How to documentation for internationalize your plugin on https://developer.wordpress.org/plugins/internationalization.
This name is given by WordPress only one time and is so unique.
If your plugin Url is https://wordpress.org/plugins/category-posts, the plugin slug is: ‘category-posts’.
WordPress makes sure that it is a unique name.
The same shows the plugin SVN repository Url path: Is the Url http://plugins.svn.wordpress.org/category-posts/ the plugin slug is: ‘category-posts’.
After changeing to the right slag for your Text Domain. Only few seconds tanslate.wordpress.org shows all widget translation files and have the possibility to translate all translation arguments.
XAMPP FTP configuration for localhost and Mac OS X
FTP Connection Information
For update WordPress with a localhost installation, you must configure and get access with your FTP-client. We use XAMPP as FTP-Client. If it installed we have to “Start” the FTP-Client. Now we are ready to download and update WordPress PlugIns.
With a XAMPP installation on Apple OS X the FTP connection is not configurated automaticly and we have to do this. It means the connection informations, like Hostname, the FTP Username and the FTP Password are missing. Of course it appears an dialog as the screenshot shows above.
A second error can be folder access problems, missing folder or read/write rights. Because the access rights WordPress can not create the needed folders for plugin downloads and updates. We must create these two folders and give them read/write rights for WordPress.
Create this two folders:
Give WordPress read/write access to them:
Now we should download and install WordPress Plugins.