codestyling
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Native Dashboard] Cannot login to WP admin with this plugin installedThe compatibility issue has been fixed at version 1.3.11
Forum: Plugins
In reply to: [WP Native Dashboard] Fatal error on 3.6The compatibility issue has been fixed at version 1.3.11
Forum: Plugins
In reply to: [WP Native Dashboard] Reason for 3.6 add_menu() error and quickfixThe compatibility issue has been fixed at version 1.3.11
Forum: Plugins
In reply to: [Codestyling Localization] Can only translates theme, not wordpressNo it has not. Did you really translate the WordPress itself or the words found inside theme shown as “default”?
Words related to WordPress within a theme can’t be used at all. Only if the WordPress main file contains it, it will appeare. If not, you will never get a translation for those words out of a theme even if they would be packed into the themes file.
If a theme author is using the “default” textdomain, this is a bug within the theme.Forum: Plugins
In reply to: [Codestyling Localization] Can only translates theme, not wordpressYes, I’m the author of “Codestyling Localization” but what is the relation to your inital question related to a Theme and it’s translation?
Forum: Plugins
In reply to: [Codestyling Localization] Script Guard SuggestionsChrome has a scroll bug while inserting new content via ajax. It stops any build in scroll by location hashes and also doesn’t execute the scroll within the ajax call after insertion.
The only workarround is a timeout scrolling during insertion to go arround that bug.I have to check the whitelisting of yoast plugin, thanks for hint about, I’m using the german similat plugin 🙂
Forum: Plugins
In reply to: [Codestyling Localization] Can only translates theme, not wordpressAll texts mapped to textdomain “default” have to be inside the WordPress main translation file. Mostly this is a bug by the plugin authors, if the use texts not contained at WordPress main file.
Even if they would be contained inside the plugins file, they won’t be used, cause the textdomain used in PHP code forces to lookup within the WordPress file instead of looking up inside the plugins file.So i didn’t allow to translate such mistakes, cause even if translated they won’t be shown (except they are already inside WordPress core).
Please contact the plugin author about that, he/she has to repair that.Does this help answer your question?
Forum: Plugins
In reply to: [Codestyling Localization] Script Guard SuggestionsCan’t reproduce it with Firefox. Do you are using a different browser?
Does any script modify the page behavior permitted by guard (like wp-piwik, jetpack, wp-debug)?Forum: Plugins
In reply to: [Codestyling Localization] Script Guard SuggestionsI will check this and handle it after reproduction.
I’ve also planned to report this as new ticket at trac.wordpress.org soon cause this leads at some providers to “white screen of death” if they run PHP >= 5.4 (always STRICT on) and kill the process by first occuring PHP error (locally reproduced with such a config).Forum: Plugins
In reply to: [Codestyling Localization] Error in creation .mo file it_IT.moDo you have a Suhosin extension running limiting the post parameters to 20 or any other post param count limitation ?
If so, the textdomain won’t be transfered and ends up with leading “-” char for any “admin|continent-cities|admin-network” textdomains/mo files.
Currently I can’t find any other way to produce this result.Forum: Plugins
In reply to: [Codestyling Localization] Woocommerce 1.6.6 conflictI have intensivly tested my plugin against a lot well known and wide range used public plugins. My plugin only protects it own pages and doesn’t have any influence to any other pages in Admin aera except its own pages.
So the issue you may see is not caused by my plugin. For sure I have checked it within my local environment with woocommerce 1.6.6 and all works as expected (images before tabs and also color pickers working as expected).Because my plugin shows at its own pages a PHP warning like you wrote:
wp-content/plugins/always-edit-in-html/always-edit-in-html.php on line 39
I would say, the plugin “always-edit-in-html” causes at least some problems at other backend pages too. You can only find out, which plugin is causing the error by deactivation plugin by plugin.If you did lately upgrades of plugins/theme (more than one) or core, any of those updated components can potential cause issues afterwards.
A similar case occured in quite different thread but was addressed by renaming the blog and wordpress url at settings page weeks after install with the www. subdomain prefix. From that point on any call to get_site_url() doesn’t return the domain with the www. subdomain extension but the 1st install saved pure domain at the option table.
That’s why I do a full spectrum analysis first with all occured behavior to find the best matching overall solution.
And yes, it looks like a bug in single installs, if I rename both setting page values and get afterwards at get_site_url() an unexpected/unlogical value.Don’t get me wrong, I will deal with all incomming reports sooner or later but software can’t be free of bugs because it runs on top of hard- and software also not free of bugs. So nobody is able to deal upfront with each and any potential occuring issue. I know, what I’m talking about, normally at my profession I have to deal, write and maintain C++ software with more than 20 million of code lines running at high critical companies.
Don’t guess, what I will do or not.
It more than unprofessional, what do you think you have to tell the world what is right or wrong. You are creating non real live scenarios and trying to explain that it’s common use in the wild. It isn’t!
Futhermore I support my plugins as best as possible but not without analysing it in detail.Forum: Plugins
In reply to: [Codestyling Localization] JS error – plugin not workingHave been analysed in cooperation and will be solve with version 1.99.30 comming soon.
Forum: Plugins
In reply to: [Codestyling Localization] Uncaught TypeError: Object , has no method 'empty'I have adjusted the Turkish plural forms to
nplurals=2; plural=(n>1);as written here: http://translate.sourceforge.net/wiki/l10n/pluralforms
Will be available with update to version 1.99.30