Viewing 15 replies - 1 through 15 (of 24 total)
  • rafaelvidal

    (@rafaelvidal)

    Why you think that?
    What problem are you getting?

    gregersen

    (@gregersen)

    Same here, no languages. Nowhere to get them either. Does this thing work at all?

    Thread Starter jishi

    (@jishi)

    Hello Rafael, I get no errors at all, when I click “check repository” on my vanilla 3.7.1, I see no action at all. I checked the same thing on 3.5.1, and everything is ok.

    Thread Starter jishi

    (@jishi)

    Hello again!
    I hope this will help you.
    When you’re on the page https://www.domain.com/wp-admin/options-general.php?page=wp-native-dashboard and you look to the source code, you see no $(‘#csp-check-repository’) mentions. Why? Because function on_admin_head() was not called. Why? Because ‘admin_head’ event is not fired. Why? I don’t know, mb some changes in 371.

    Why won’t you transfer all the JS printed in function on_admin_head() to another place, like function on_print_metabox_automattic_i18n() ?

    Regards, Alexander ??

    Thread Starter jishi

    (@jishi)

    Me dumb ))
    In order to make it work you have to check extend Backend Admin Bar with a language quick selector.” box at least, save, and only then you’ll be able to receive the language list.

    Sorry for buzz.

    ventende

    (@ventende)

    This plugin is not working very well, after download my language list is short and consist of only 8 languages, none of them useful to me.

    Doug M

    (@nes-native-english-services)

    @ventende

    Choose another version of wp. I believe this only pulls language files that are updated for the version of wp you ask for. If the language file you need wasn’t updated for 3.7.1 then it won’t be available. If you try an older version of wp then you may find the file you need.

    @jishi
    Thanks, was having this same trouble.

    ventende

    (@ventende)

    Hm, going back to older version of WP is not an option. Had so much troubles with fixing damages from the recent upgrade, it totally messed up my defaults and ruined a lot of tweaks. Anyways, a plugin should always validate with the latest WP version I think, going backwards is kinda… backwards.

    Thanks for the tip anyway.

    Doug M

    (@nes-native-english-services)

    You’re not going backwords with your wp install. You’re only pulling a version of the mo/po files that was created on an older version. They will work with the new version of wp. I just updated to wp 3.7.1 and I’m using a 3.3 version of the Polish mo/po files.

    Try the 3.3 version of the mo/po files…you’ll probably find what you’re looking for.

    Doug M

    (@nes-native-english-services)

    To the dev team on this plugin….

    A small note in the settings panel to point out the ‘must save before retrieving svn files’ and a description of how to look for a version of the files would answer a lot of questions and probably help the star rating on your plugin.

    ventende

    (@ventende)

    Older version of mo/po files? I don’t get this. Versions? What does the localization files have to do with this? I thought the plugin held the translations for all the languages. How does the languages in the list have anything to do with any localization files? I’m looking to change the wp admin language. The 8 random languages that appears in the list has nothing to do with the localization of my site.

    Doug M

    (@nes-native-english-services)

    No, the plugin pulls the translations from the svn. The svn is where all the translation files are held.

    The svn is a repository and they are voluntarily updated by users. When someone comes across something new that needs to be translated they will do it.

    When the translation is edited or added to then there will be an update to the version number. If the translation you are looking for hasn’t been updated since a certain version(ie Polish hasn’t been updated since 3.3) then it will hold a tag within the file stating it’s for v3.3. BUT, there aren’t many changes that need to take place to keep it up to date with the current version of the actual WP system. I’d say 99% of the time there is no need to update the mo/po files when they update the core of WP.

    Give it a go…search backwards through the version numbers in the drop down until you find the most recent version of the mo/po files for your language. You’ll be ok…promise.

    https://codex.www.ads-software.com/WordPress_in_Your_Language

    Tells you all about the svn repository

    Doug M

    (@nes-native-english-services)

    I know it takes some time for all the files that are available for a certain version to be ‘pulled in’ so I’d suggest trying 3.3 first. You’ll likely find what you’re looking for.

    ventende

    (@ventende)

    Ok, so the 8 languages that’s in the repository are the only ones that are currently valid for WP 3.7.1? But there’s not too much difference in the front-end language from the former WP version, shouldn’t the repository just generate the older translations instead of just the 8 that’s been translated to exact suit the new WP version txt? And then just alter those translation files when possible? I mean, it’s far better to have 90% than nothing after all.

    Doug M

    (@nes-native-english-services)

    Well…not exactly the correct wording ‘valid’. Those are the ones that have had updates or someone went in and changed the version identification in the file to WP 3.7.1.

Viewing 15 replies - 1 through 15 (of 24 total)
  • The topic ‘Can not get language list’ is closed to new replies.