codestyling
Forum Replies Created
-
Do you get reperated FTP credential requests or still after enter the credentials the message, that you don’t have access right?
If the credentials pops up again and again, then something is wrong with your credentials or the ways FTP is working.
If the credentials are accepted but you get the message, that you haven’t enough rights, then something went wrong with the path and domain root, I need to know, how the installation has been done in relation to the directory tree starting with ftp domain root.Currently there is no direct url to do something with a plugin. The last update at least remembers after launching editor, from which component it has been launched and scrolls to after going back to overview page.
If you have the file po or mo symbol shown in red color instead of green, it has the wrong permission to be modified. Please click at the red symbol to change the permission.
If this still doesn’t work, try the 1.99.21 which detects your capabilities at your file system more qualified.
I assume, you have some cache plugin running. So if you translate the files and generate the related mo file, it will not throw away your cached pages with prior available translations.
If you get next day some translations made previous day, this sounds to me, that the cache has been refreshed the affected page by any reason and now you get the correct text.So using a cache plugin and changing translations you have to empty your cache after you finished your translation to get the changed phrases too.
2nd – if pages still no show translated text (especially emails been sent) than this is a problem of how an who sends this mails. If this is done by Ajax or a plugin doesn’t care to load the translations in this cases, you will always get english. As long as the locale is not qualified set prior to send a mail, you will get mails in english.
Summary: getting english result even if translations are available is not a fault of my plugin but within the workflow using the produced translation files.
Question #1: Do you need FTP credential for automatic updates of Plugins/Themes or WordPress itself?
Question #2: Is your WordPress installation able to automtic update in any case?
Forum: Plugins
In reply to: [WP Native Dashboard] [Plugin: WP Native Dashboard] Version 1.3.7 messed upSolved with version 1.3.8 now, please update.
Has been solved with version 1.99.19 and supports both translation separations, less version 3.4 and upwards versions.
Solved with upcomming version 1.99.19 and supports simplified and traditional for both API’s.
Forum: Plugins
In reply to: [WP Native Dashboard] [Plugin: WP Native Dashboard] Version 1.3.7 messed upThis is known and also found. The next update will fix it, this will be version 1.3.8 comming soon.
Yes, you can prevent it even if my plugin can’t evaluate the correct folder. This can be done by placing a translation template inside the language folder. The name of the file should be:
embedchess-xx_XX.potThe files content should be the result of a fresh scan process, so only the untranslated full content should be inside. But it’s also enough, if the file only contains a valid pot header like this taken from the WordPress Importer’s *.pot file:
# Copyright (C) 2011 WordPress Importer # This file is distributed under the same license as the WordPress Importer package. msgid "" msgstr "" "Project-Id-Version: WordPress Importer 0.5\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wordpress-importer\n" "POT-Creation-Date: 2011-07-16 15:45:12+00:00\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "PO-Revision-Date: 2010-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n"This is a bug newly introduced and will be fixed with next version 1.3.8 to be able again to switch back to english, if no english file exists (normally it shouldn’t because of build in).
If I get you right, the multiple sites are configured with a dedicated language setting for each of them. Normally new created users will default to the sites language automatically.
Summarizing your feature request, you would expect to be able to pre-define a different language for user not related to the blog’s default one?Would it be enough to pre-define this language only, if the user will be fresh created or the registration will be approved?
I wouldn’t enlarge the pluign to give admins the ability at later stages to change my personal settings. If I as user pro actively change it to let’s say german, I wouldn’t expect, that the admin can revert it to english and shows me initial dashboard as english even if I left it with german choice.
Hmm, normally the admins need not to have access to very personal settings of dedicated users. Thatswhy the language option is resticted to the profile page and not visible at the user page the admin uses to maintain users.
But you are right, if at multisite installation each blog has got an other default language configured, than this should be respected as default for the user. I have to check, if this is working and will make it working if not yet possible.
The only questionable thing is: If a user is member of more than one blog this user will than get in case of profile mode the last saved language at each of them regardless what lang the current blog will have. To circumnvent this, you have than only the chance to enable the lang admin bar switcher to allow users to switch easy to another lang.
In my opinion it makes not sence to store per blog a user lang but it makes sence to respect the sub blogs configured lang in first place.
Please send me some screenshots. It would help to address your issue.
The locale “US_en” doesn’t exist, it’s “en_US”. But i also worte a mail for clarification to you.