codestyling
Forum Replies Created
-
This may be related to an early version of WP 3.4 ?
I don’t have any further ideas, please send me a *.zip file of the theme for analysis, if the new version 1.99.17 doesn’t solve it.Forum: Plugins
In reply to: [Codestyling Localization] Codestyling Localizationclosed because of no further response from intial topic opener.
As the plugins page states, it supports currently only locale defintions with country and language code eg: en_US / en_UK / ja_JP.
If you need it short (for other plugins like qtranslate, which isn’t iterested into country) then translate it with full locale and afterwards rename it.not at the moment. why you didn’t mail your translations to the author for inclusion into next plugin update?
it’s not intended to support “ungrouped” handling, because 2 plugins should not have the same textdomain.
Reason: depending on their load order and lets say both have the same term but with different translations, you will get only one of this translations and never see the 2nd.Forum: Plugins
In reply to: CodeStyling Localization for WP Forum ServerI need the plugin or whatever is necessary for local install to get an idea, what wents wrong. Please let me know, how to download and setup this for investigation.
This is a warning designed to show, that the Author is using a not intended way to load translations for a plugin. This may work anyway, but may have also side effects for other plugins that respond on loading filters for translations files. Because the author used the general load function, others may interprete this as normal WP translation load even it is doing a plugin translation load!
Forum: Plugins
In reply to: [Codestyling Localization] Warning displaypreg_match() issue solved at Version 1.99.16
preg_match() issue solved at Version 1.99.16
preg_match() issue solved at Version 1.99.16
Forum: Plugins
In reply to: [Codestyling Localization] Rescan hanging or menu option not workingRelocated directories are workimg like described and tested here: Relocation Answer – entry #2
I did a relocation at the end of wp-config.php like this:
/** Absolute path to the WordPress directory. */ if ( !defined('ABSPATH') ) define('ABSPATH', dirname(__FILE__) . '/'); define( 'WP_CONTENT_DIR', ABSPATH . 'wp-codestyling' ); define( 'WP_CONTENT_URL', 'http://wp33.de/wp-codestyling'); define( 'PLUGINDIR', 'wp-codestyling/plugins' ); define( 'MUPLUGINDIR', 'wp-codestyling/mu-plugins' ); /** Sets up WordPress vars and included files. */ require_once(ABSPATH . 'wp-settings.php');and all works as expected. Can’t see any problem and can’t reproduce it.
Forum: Plugins
In reply to: [bbPress] [Plugin: bbPress] Deprecated function and trailing spacesI wouldn’t name this a non issue for different load functions, cause each of them fires different hooks and filters. So if I want to re-direct all plugin translations to load their files from a dedicated folder supported by a plugin sets this filter, the bbPress plugin is out of scope because it can’t be detected by its load filter as plugin. I have to know it by textdomain and have to code an extra detection because it can’t be assumed as plugin while only using ordinary load method.
Forum: Plugins
In reply to: [Codestyling Localization] Codestyling LocalizationYou can also use my address from imprint page.
Forum: Plugins
In reply to: [Codestyling Localization] Codestyling LocalizationThe permission 777 (includes execute) is not necessary, 666 is enough in highest case. It would be a good idea to have a look at the affected WordPress install to understand the issue. Unfortunately I’m off until Monday. Would you please so kind and provide an appropriated access for testing purpose and send me a mail about, so I can help you starting Monday 20.06. earliest.