WP Native Dashboard
[resolved] Can not get language list (25 posts)

  1. jishi
    Posted 2 years ago #

    It seems there's no connection to SVN or something like that. Downgraded to 3.5.1 to get any result. I hope you gonna fix it soon.


  2. rafaelvidal
    Posted 2 years ago #

    Why you think that?
    What problem are you getting?

  3. gregersen
    Posted 2 years ago #

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

  4. jishi
    Posted 2 years ago #

    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.

  5. jishi
    Posted 2 years ago #

    Hello again!
    I hope this will help you.
    When you're on the page http://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 ;-)

  6. jishi
    Posted 2 years ago #

    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.

  7. ventende
    Posted 2 years ago #

    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.

  8. @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.

    Thanks, was having this same trouble.

  9. ventende
    Posted 2 years ago #

    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.

  10. 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.

  11. 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.

  12. ventende
    Posted 2 years ago #

    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.

  13. 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.


    Tells you all about the svn repository

  14. 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.

  15. ventende
    Posted 2 years ago #

    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.

  16. 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.

  17. And actually they are all in the repository, the plugin is only pulling in the ones that are "tagged" for 3.7.1.

  18. ventende
    Posted 2 years ago #

    Ok, so one could expect that the plugin will include more updated languages as time goes by. I guess the point in having the plugin is that it keeps track of the WP version developments, thus making it a dynamic tool. I understand from your explanation that it's an open source project that relies on contributions from people willing to update the translations, it would be more practical if the languages (any update) were all accessible in any plugin version as mentioned in my earlier post. As you also confirm the language differences are not that big between the WP versions after all, so it wouldn't hurt.

  19. I just did a quick video tutorial on how this all works.


    Hope it helps.

  20. ventende
    Posted 2 years ago #

    Thanks, I appreciate that. The WP interface language has always been a big deal, don't get why WP haven't addressed these issues themselves. The plugins that solves these issues are most welcome.

  21. What language do you need? You may be able to find a version of WordPress that has been completely translated for your language. Such as Polish.


    Try changing pl. to your language and see if you get a complete version for your language.

  22. ventende
    Posted 2 years ago #

    I ALWAYS want WP in English for myself but sometimes my clients that I design for needs the admin to be in other languages. When I produce websites for myself I also need them to be localized in Scandinavian languages, but at the same time retain the English WP admin. I use a plugin named Admin in English, that overrides everything I got going in regards to po/mo translations on the server and that is exactly want I want cause it seems almost impossible to localize a WP theme without having to cope with a WP admin language that is the SAME as the localized language. Whenever I changed the WLANG codes it messed up my localization site wide. I went crazy trying to achieve two different languages until I found that plugin. I was hoping with Native Dashboard" that I could do the same if I have clients from different countries, like other European countries. It looks like Native Dashboard may very well be the answer, I'm just depended on it to be up to date with WP versions to avoid having to look for older localization files. I guess I could always preform that task if I really needed it, but one always hope for swifter solutions.

  23. All of these type of translation plugins use the same repository for mo/po files. Which ever one you use will use the same files. It's what they do with those files and how they use them that is the difference.

    There's another that I use...

    This one is more for multi-lingual sites. Posts and pages can be written in an language and have that language be set as the default and then it will use Google or Bing to translate those pages to the other languages selected. I know that Google and Bing translations can be real crap sometimes but that plugin also allows for anonymous people to correct those translations.

    For what you described WordPress Native Dashboard is your solution. If you want multi-language on the front end then I would suggest Transposh.

    If you want to see how Transposh anonymous user correction works you can visit my ESL website. http://nes.pila.pl. Change the language to Polish and you'll see a check box. Check the box and it'll allow you to make changes. Most of this site was written in English but about 90% of it's been corrected by anonymous users.

  24. ventende
    Posted 2 years ago #

    Thanks for the tip. I always end up ripping my hair out when it comes to localization of the blog language in WP, cause each time I localize with PoEdit and go trough the procedure of adding po/mo files to a site I always end up with some few words in English. Examples: "by:author name" - "comment: number" - "post comment" - and all the month names etc. These words never show in the translation process and they're not coming from the theme, it's WP blog language.

  25. You can forget poedit, I made that mistake also.

    Here's another plugin to localize and translate plugins and widgets and just about anything else you need to translate.


Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WP Native Dashboard
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic


No tags yet.