codestyling

This is a warning for the case, that after translation not all works as expected.
Nevertheless you should be able to create, translate and generate the required language.

If possible could you provide login credential for the affected blog by mail? I would inspect the behavoir and perform an analysis to narrow this down.

This sounds crasy. Did the translation file *.po also loose the texts or are they only not shown at page?
The main problem to analyse what went wrong is, that i haven’t the affected theme and also not you base tranlation files. If I would have them within my local test environment, I could analyse and fix the bug, if any contained (either my plugin or elsewhere).
If you think, it worth going this way, please send me the theme and translation by mail (can be found at my imprint page).

Depends on what have been changed at php source files in relation to existing po file. If you rescan, than it will check, if the source string is contained at current translations within po file. If so, it will be kept, if not, it will place it as new one string.

Example:
PHP code contains “Car”
PO File contains “car” => “Auto”
rescan can’t find “Car” and places it as untranslated into the rescanned PO file.

Ok, I’ve tested 1.0.8 (free version), may be a lot differences.
Would it be ok, if you could provide the Theme for testing purpose by mail (can be found at my imprint page)?

Do you have defined the WPLANG at your wp-config.php for spanish language?
If this is the case I would need the Theme for analysis purpose why it doesn’t load the generated mo file.
If possible, could you provide the Theme for that pupose by mail (can be found at my imprint page)?

How did you verify, that only english is contained? Still while subblog xy shows up at english?
Did you configure the language for your subblog at network admin for the site?

My plugin picks up each textdomain. Let’s assume, that you are using ‘woocommerce‘ and ‘woocommerce-admin‘. You will find both inside the drop down list of contained textdomains and will also face the warning for more than one textdomains.

By selecting one of them, you will only see those strings, that are related to the given textdomain. All the strings will be hosted within one *.po file. But if you generate the *.mo file, it depends on what textdomain is currently selected.

Generating the file for textdomain ‘woocommerce‘ will result in writing a file like: woocommerce-de_DE.mo
Generating the file for textdomain ‘woocommerce-admin‘ will result in writing a file like: woocommerce-admin-de_DE.mo
Both files only contains those strings related to the textdomain.

If your plugin loads both textdomains, than you will get all translations where needed. So the admin one should be loaded only, if you are logged in and working within admin pages.

Hint: My plugin uses the first found textdomain as the main one. The order of load call appearance in PHP code will determine the choise of plugins main textdomain.