Comment on WordPress Language Translation by SEO Dave.

WordPress Theme Language Translation If you are happy with inline CSS (I try to avoid it, personal pet peeve) use the “Stallion All In One SEO Additional Sitewide Headers” (that’s a mouthful :-)).

Under Stallion Advanced SEO tick “Stallion All in One SEO ON” this turns on the Stallion All In One SEO options page that will be available after another page loads (go to your Dashboard for example and check the Stallion Theme menu for the new link).

Under the Stallion All In One Options page at the bottom are 4 boxes related to adding info to the header area. The “Additional Sitewide Headers” will load the code on every page of the site except Page templates that have their own header code: I think there’s one built in Page template that doesn’t use the header.php code where the additional header code is loaded, if you build your own Page template that doesn’t use the header.php file remember to replicate anything you add below there as well.

You have two choices that will avoid editing the Stallion core CSS files and avoid upgrade problems I mentioned before.

Add inline css code, this would override the CSS of the core Stallion CSS files

<style type="text/css">
#st_feature {
border: 0px solid;

If you aren’t familiar with CSS the last CSS code loaded is basically what’s shown, so if you have three ways the above sort of code is loaded the first has border 10px, second 50px and the last 0px it’s the 0px that’s used. which means you can override most CSS in a core CSS file by copying it to the header above or a separate css file (see below).

Or create a css file like mycustom.css add it to your Child theme folder and reference it as follows changing the URL to yours:

<link rel="stylesheet" href="" type="text/css" media="screen" />

and add the css you changed in the main files in this file.

Both these options will remove the need for making the changes again after a Stallion update, though you’ll still have to keep an eye on them for conflicts with new features.

It’s on my list of features to add to create a more user friendly way of doing the above.

After you change a language file are you reloading it on the Stallion Language options page?

The settings within the language files are not used on the fly to generate the languages, when you tick a language and save the options the file is read and the settings are added to the database at the time you click the save button. If you change the file and don’t select the file again and save options again the current database settings remain the same. The files are like backups of the language options database, run a file and the new entries are added. Basically a quick way to add a particular set of options, I use the same format on the main Stallion options page for the default SEO settings etc… near the bottom. The language files only holds the language options, the SEO defaults holds all settings.