• I’ve upgrade it, created an account in Yandex, generated a new key, chosen 30 languages and put the new widget in the sidebar of my blog.

    It has displayed only my country’s flag (only one flag) unnecessarily and also has not displayed the “credit link” to Yandex.

    So, it’s broken.

    I’ve downgraded to previous version 1.3.2 and everything is OK now, for while…

    https://www.ads-software.com/plugins/global-translator/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author pozzad

    (@pozzad)

    Dear Marcos,
    the reason because, after installing the plugin, you don’t see the flags is that the translations aren’t still available: if the plugin immediately would shows them (before having created the translation), it would be unable to serve the related page and the link would be broken…
    I’ll investigate about the credit link, but I suspect the issue could be related to your theme…

    How do I get the older version of the plugin?

    Thread Starter Marcos Blatt

    (@marcos-blatt)

    wolflegal,
    I’ve done the same what you want to do: downgrade.

    In Developers tab of the link below choose the last functional version 1.3.2 :

    https://www.ads-software.com/plugins/global-translator/developers/

    Good luck!

    Thank you, Marcos. The one tab that I didn’t go check because I didn’t think that it applied, and/or that it would contain the old versions. I should have known better (my old memory isn’t what it used to be). Now, if I go back to the old version, I will have to go through all of the work of changing the html/url code back to what it was, on three separate pages, since the developer of this plugin changed the url’s in the new version, as you no doubt went through yourself (I have the flag links in my header, sidebar and footer). I was hoping the plugin developer would respond to my other request for assistance in this thread so that I might not have to do that, but he doesn’t seem to respond to most requests; and, when he does, only responds to one or two requests every now and then, leaving most people hanging, typical of most “techies”, who falsely think that they’re better than everyone else who are not techies (and probably feel that they’re better than other techies as well).

    Thread Starter Marcos Blatt

    (@marcos-blatt)

    Hi, pozzad.

    Thanks for your reply but how visitors can use the plugin if they don’t see the 30 flags?

    We use your plugin in the sidebar of our blog:
    https://www.materiaincognita.com.br

    Take a look at the first image below:
    https://www.materiaincognita.com.br/download/screenshot-1.jpg

    We are using version 1.3.2 and there you can see all 30 flags we want to show to our visitors.

    The next image shows the appearance of the version 2.0.2:
    https://www.materiaincognita.com.br/download/screenshot-2.jpg

    Where are all 30 flags we want to show?

    Other thing:

    Using version 1.3.2 our site database has 140 MB in size.
    Using version 2.0.2 our site database has reached 375 MB, an increase of 168% (!) in few hours.

    So, what did we do? Downgraded the plugin to version 1.3.2.

    Marcos, evidently the new version is supposed to automatically translate all of the blog’s pages for all of the languages that you choose, without any blog visitor requests to do so. But, the thing is, that apparently overloads the keys quite rapidly if one chooses a lot of languages. One would likely have to have over thirty keys if choosing the translation into thirty languages, obviously using up a great deal of bandwidth and space.

    But now, as I said in my other, more in-depth request for assistance in the other thread, most of the twelve keys that I generated on Yandex and installed into the plugin, on both of my blogs (the latter blog being my mirror site—twelve unique keys to each blog without duplicating any of the keys), have been suspended without even doing ANY translation(s)! I have written Yandex, too; but, so far, no help from them either.

    It seems that this is yet another example of a misguided attempt at an “update/upgrade” that overestimates the so-called “benefit(s)” of same, and underestimates the problems caused by it. I’m sure that Mr. Pozza meant well, but he evidently would have been better off simply updating the old version, pretty much leaving it as it was, and only improving the security and compatibility of the plugin, rather than so drastically altering it, especially without advance warning.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Does not work in WP 4.4.1 version’ is closed to new replies.