codestyling
Forum Replies Created
-
Forum: Plugins
In reply to: [Codestyling Localization] Multiple textdomains in a single pluginYes, the plugin picks up each textdomain contained. It will also write the dedicated *.mo files to disk, if you switch the textdomain select box and press the generate button. The only textdomain not been written to disk in scope of a plugin/theme is the “default” or WordPress textdomain, because this is an issue within the translation context and the author must avoid that.
Nevertheless my plugin will show a warning, that more than one textdomain is contained to show that this is either accidentally (most cases while copied foreign code blocks) or intentionally like in your illustrated case.This is a known problem since 3.5 version of WordPress.
The packaged themes like twenty (ten|eleven|twelfe) have had their own language folder but there is only the *.pot file (translation template). The real files are located at the folder you mentioned above.
Unfortunately my plugin is not aware of this fact and only inspects the themes language folder for existing theme translation. And there are none.This will be changed within version 2.0 of my plugin. This version will support this kind of “re-routed” language file folders. The current work arround is to move (or copy) the files into the themes language folder but have to be renamed too (locale.mo).
This behavoir introduced with WP 3.5 should avoid the overwrite of existing translations. In my opinion this is a first step in right direction but not the full goal as I would expect it. What’s about multisite installation, where several sub blog owner need to have their special own modification of the same language file?
This is currently not covered but will be with my new 2.0 version of my plugin.Thatswhy I do not spend more power into 1.x versions (except bugfixing) and I’m working focused on 2.0 which will require at least 3.5 WordPress to be usable.
Forum: Plugins
In reply to: [Codestyling Localization] Twenty eleven translation into dutchAfter 4 weeks without any response I assumed, my hints solved it. So it will be closed now.
Improved TAB charactor handling won’t make it into 1.x versions from now on because the 2.0 reaches beta state soon. This will be handled with scope of 2.0 version only.
Forum: Plugins
In reply to: [Codestyling Localization] Scripting GuardThere are a lot of different issues contained:
1.) The PHP notice warning within adsense-plugin results from not existing key inside the plugins own options. The author missed to test the existence of it’s values. Please inform the author of adsense-plugin about.
2.) The PHP warning within my plugin was raised because of active ja_JP.mo and is indeed a bug within my plugin in context of special languages. This will be repaired with version 1.99.30 soon.
3.) The misplaced core file enqueue of media upload script is caused by the active theme as I can investigate it. The Theme author is attaching this script into all backend pages but should it only attach to it’s own backend pages where needed. Please contact the Theme author about.
4.) Furthermore the Theme enqueued a second script out of it’s own hosted scripts for assisting media upload as portfolio-upload.js Please contact the author of Theme to restict the script attachment to Theme based backend pages only.
5.) A plugin or the Theme tries to attach a jQuery version from Google CDN provider instead of using the WordPress shipped version of script. This has been remove at my plugins backend pages to avoid conflicts. I can’t find out, which plugin or theme is responsible for. The responsible author should be informed about it.
6.) Reporting the scripts from jetpack WordPress CDN as dubiouse external is not longer the case, I’m afraid, you are not using the latest version of my plugin. It will be reported as supported CDN but with hints since latest versions.
Hope this may explain it more in detail.
Forum: Plugins
In reply to: [Codestyling Localization] Codeslyling no longer works after last update.This seems to be an unknown reason, cause I’ve tested a lot of cases now. To solve this issue I would need an account to inpect the faulting behavior live at the system affected. If this is ok, please send me the credentials by mail, so I can help solving this issue.
Forum: Plugins
In reply to: [Codestyling Localization] Can i deactivate plugin when not translating?There is no reason why keep the plugin always active. If you don’t need it currently, just deactivate it. If you need it again, just activate it.
The few settings the model have so far will stay intact and will be again available after re-activation.Forum: Plugins
In reply to: [Codestyling Localization] Croatian – Hrvatski (hr)As already written here http://wordpress.org/support/topic/language-code#post-3526852 the current 1.x version won’t support 2 letter appreviations of locales.
This will change with version 2.0 scheduled for January 2013.Forum: Plugins
In reply to: [Codestyling Localization] Codeslyling no longer works after last update.Please update to version 1.99.29 that fixes 3 issues.
The problem of SEO plugin remains but doesn’t prevent function of my plugin any longer and will be reported as expected now.Forum: Plugins
In reply to: [Codestyling Localization] Codeslyling no longer works after last update.Problem solved. Your Server doesn’t support subfolder .htaccess files but my plugin comes with one inside it’s main folder. After removing the file all works as expected now.
Forum: Plugins
In reply to: [Codestyling Localization] Codeslyling no longer works after last update.@agrolsy: I’ve tested all the plugins shown by the traces above in total and the plugin works anyway as expected.
The only chance to get this error tracked down is to get a admin login for your backend and I have to inspect the issue.
If this is feasible for you, please send me the appropriated credentials by e-mail.Forum: Reviews
In reply to: [Codestyling Localization] Now it's almost perfect!Within the editor you get warnings about multiple textdomains.
You can also switch to each of them and inspect the affected string afterwards. Additionally you can open the *.php file for each string and it shows the string within the code context highlighted.Forum: Plugins
In reply to: [Codestyling Localization] Plugin not translatning allI don’t understand it, because it’s contained at the scanned file and can be translated anyway. But as long as no new mo file has been generated, it won’t appear, *.po file won’t get used for translation on page, only the produced *.mo files out of.
Forum: Plugins
In reply to: [Codestyling Localization] Plugin not translatning allIt could be, that the plugin does load the textdomain to late or never for your frontpage. If the load call of plugin is performed after the partial content has been generated or wasn’t loaded, than it appears at english.
If you made translations of woocommerce and mostly they work correctly, than this may also a reason for untranslated texts.Forum: Plugins
In reply to: [Codestyling Localization] Plugin not translatning allTry to switch of total cache plugin or reset the cache.
If you did newly translate it the pages won’t get the translation as long as the page get cached again from scratch.
I don’t see any other reason, why the affected texts doesn’t appear.