codestyling
Forum Replies Created
-
The questionable line deals with filenames of *.mo and *.po file. Could it be, that inside the naming of one of your plugin files are special character contained?
I can’t reproduce the issue until I know a case (filename) which produces this result. Could you pease find out, which *.mo/*.po/*.pot is responsible for this behavior and give me this example as test base?After donwloading “Redirection” Plugin, I did create a new german language file, did a rescan an opened the editor.
Than I did switch to plurals, entered both phrases and pressed the save button. All work fine no warning has been issued.
So make it short, i can’t reproduce the error you described above. I have no idea, why this happens at your system. This warning will only be issued, if you press generate mo-file in case the entiered translation file is empty. But also generation of mo-file with only this plural editing works as expected at my machines.Forum: Plugins
In reply to: [Codestyling Localization] Codestyling LocalizationGoDaddy seems to have problems with file access permissions. The *.po and *.mo files need to have permission 666 or 664 or 644 to be readable/writable. (from highest needed down to lowest, also known as [rw-|rw-|rw-] or [rw-|rw-|r–] or [rw-|r–|r–]).
Could you please check at a file not scannable or editible what permissions it has?Seems to be related to the filename in analysis. Did the plugin using special chars at some filenames like ‘$’, ‘^’ or brackets ?
Forum: Plugins
In reply to: [Codestyling Localization] Codestyling LocalizationQuestion: Are the permission buttons for po and mo files green or red colored? In case of showing in red, it can’t be scanned, please press the red buttons to get the correct file permissions. I have no other idea, it seems to be related to the file permissions at the hoster.
Forum: Plugins
In reply to: [Codestyling Localization] Codestyling LocalizationDo you need FTP credential for automatic updates at this install? If yes, than this server may be not suitable for this plugin. Currently it can’t deal with servers, where the files can’t be changed because of ownership is different to running script. This is subject of future change.
If you switch the ownership of existing files to those the plugin creates, than it should work. Please check this.Forum: Plugins
In reply to: [Codestyling Localization] Codestyling LocalizationCould you please describe the problem more specific?
What happens and what went wrong doing so?
Rescan may only fail, of the files at the server have the wrong user rights and the script is not allowed to access them.closed as resolved now. if not please reopen it.
Without having a look at your backend page it is hard to tell you what’s wrong with that. It may depend on browser used, plugin and/or themes being used or simply the server where all is running.
You can invite me for investigation and solution if you want.Without having a look at your backend page it is hard to tell you what’s wrong with that. It may depend on browser used, plugin and/or themes being used or simply the server where all is running.
You can invite me for investigation and solution if you want.This may be caused by the problem I found in multibyte overload environment. Please update to version 1.99.11 and reopen this thread if not fixed.
I assume that this is not the full message of failure. If you have a WP version installed higher than 2.5 there should be another field shown the reason for.
Forum: Plugins
In reply to: [Codestyling Localization] fatal error when activating the pluginThis has been changed in plugin version 1.99.11
But it can only be handled by limiting the IDNA Feature to PHP versions >= 5.2.1 because of later introduced type casts necessary for convertion.
Your hosters seems to use a lower version. If you haven’t and IDNA Domain, all is fine. If you have one, please upgrade your PHP version.While cross reading all your other failed plugin posts at other authors plugins, it looks to me, that something inside your install collides with several other well working plugins too.
There seems to be at least one plugin or theme at your install damaging the scripts other authors successfully running (me too).
Ofter i had those issues with old themes self hosting outdated jquery versions not meeting the newer one comming with wordpress and break afterwards plugins and mostly also the TinyMCE.
Please check your theme and/or plugins about outdated javascript libraries.Yes, it is supported, if you meet at least 3 required entries:
- The Plugin needs at header fields a name.
- The Plugin needs at header fields a textdomain specifier.
- The Plugin needs at header fields a language file path.
If the plugin follows this, the translation is possible and supported.
Example (taken from my own plugin):
<?php /*
Plugin Name: CodeStyling Localization
Text Domain: codestyling-localization
Domain Path: /languages
*/?>