plugin can append unwanted strings to menu items, content, etc.

atomizer, yes 2.7 has this bug and I’m willing to admit it, which I have mentioned in numerous thread on this support page. And I have told you to go back and download version 2.6.

I have said this will be fixed in the next update. And Google provides this ability to bring the website back to it’s main version anyway, so there should be no need for me to stick my own functionality back into the plugin to make this work, except for the fact that you are correct about version 2.7 having this bug.

Thanks for blowing this up and trying to make it appear as if I don’t recognize issues here, when that is clearly not the case in my responses to you.

rob, after asking several times WHY you are using google to “translate” content back to the default language instead of using the db content, i got no answer — that is what frustrated me

at any rate, you admit there’s a bug and therefore the plugin is broken, is it not?

regardless of whether google is supposed to do the job or not, i think wp authors would prefer having their original content put back from the db, unless you are certain that google has an exact, non-cached copy of the text strings when the user reverts back (and maybe google does since it translated the def lang) — still seems a bit sketchy to me though

on second thought, what if the connection to google explodes when the translation back to default is done?

seems like it is best to pull from the db, period

Sounds great, atomizer, thanks for posting.

Hi,

Is it possible to “detect” when a call is made to “return to default language”?

If so, Atomizer could issue an >a href=”atomizer . com” target=”_ top”< call to reload the page from the site’s database (after Google has finished).

I’m not suggesting that “this is how it should be done”. Just offering a thought for this specific situation. It will be redundant, of course, but may be more of what Atomizer wishes.

Thanks again Rob for a (((great))) plugin and Mahhhh-velous Support!

=0)

Hi apostlepoe, you seem to be a good sidekick. Thanks for your posting.

I wouldn’t know how to do this using Google’s default functionality provided in the basic tool. But in my premium version I do use custom functionality to call languages, which could definitely be modified.

But in my premium version everything is customizable because we are using a different approach altogether. So I could remove the entire onclick fire event, and then we could replace it with a link back to the page url, so that it simply reloads the page.

apostlepoe, what you mention I would have to look at in more detail, because I simply wouldn’t know how to do that. But I think the idea we both mention here are the same thing, in theory.

But I was mostly concerned here because Google actually does transfer back to the original default language correctly, without forcing the hard-coded language, and I spoke too soon in my previous comments.

So if atomizer were using version 2.6, Google reverts back to original language correctly, instead of a forced default translation, as I mentioned was the problem with version 2.7. And yes, I use Google to do this, which is the entire point of this plugin. And my point is that, if Google does this correctly (assuming that I setup the plugin correctly), then the whole issue of how it gets back to the default language is really not an issue.

But my premium version DOES offer a fully-customized HTML-powered language drop-down and flags, instead of the Google javascript functionality, which produces the drop-down in the free version. This will allow full control of CSS styles, functionality, and what exactly happens when something is clicked.

atomizer, if you want the premium version so you can have full control, I will provide it for you with full support – see the footer links on the left of my design website here, and you can see the plugin website for purchase if you want.

https://www.studio88design.com/

Thanks guys!

Hi Rob,

Thank you for the compliment ??

I am using 2.6 and it does work perfectly. I haven’t downloaded the Premium version yet and so wasn’t aware of the new functionality. And agree the idea which we’ve both touched on, are really the same.

Looking forward to grabbing the Premium copy this weekend…

Best,

ap

Thanks apostlepoe, I’m glad it’s working for you. Atomizer, let me know if I can continue to help out.

Rob

Hi everyone,

I’m 90% sure of the issues surrounding the appended characters to the end of words after moderate testing, among some other small (but annoying) issues:

1) If you are seeing appended characters to single words on your webpage (i.e. “,af, ro, es”), it’s likely because Google MIGHT be reading that word as another language, and the machine translation does not understand what to do. If you have a Spanish website, all of your words should be hard-core Spanish, and languages should not be mixed on the site. Even with the multi-language option that Google offers, it seems to have problems with a select few websites, so please keep this in mind when using the plugin.

2) If you are seeing single letters in place of words, I am noticing that many web designers still have dummy text (i.e. “Lorem Ipsum”) on their websites. Remember, Lorem Ipsum is actually words written in Latin. In a few select cases, this is causing Google to get confused. Please keep this in mind.

3) Another important thing: be careful on what you use in the site title setting in “Settings > General”. It appears that Google doesn’t like any special characters here. And if you have a unique title, then Google is sometimes detecting it as a separate language. I fixed a website today that had an & (ampersand) character in the title. Google detected this as another language, appending some odd characters to it.

If those issues get fixed, then Google is bringing the site back to the original language as it should

Other than that, please continue to contact me if you have isssues on your websites, I will help.

Rob

Thank You for the update!

=0)

Hi Rob,

I’ve added this plugin right above the footer in my website. The translator works beautifully, but it messes with the markup in my footer only. It deletes a line break and adds a question mark.

You will notice that the footer looks correct before the translator is used, and incorrect once a language is selected including English. https://nwlincoln.org

Have similar problems like this come up?

Thank you!

Hi hmwantz, I see your website, but I imagine you removed the plugin for now. Your issue is likely related to a piece of text in your footer that Google cannot understand. I’m not sure of what that is right now, but if you install the plugin and show it on the site, we can start there.

Or even faster, you can provide login and password, and I will fix for you:

https://www.studio88design.com/get-in-touch/

Let me know and I will help!

Rob

Rob,

I’ve made a page with the translator that you can view. Let me know what you think or if you need anything else. Thank you!

Hi hmwantz, it appears that you have some code showing up in between the <head> and <body> tags, which could be a good start to trying to find the issues.

If you need help, let me know. You can contact me here with login details if you want: https://www.studio88design.com/get-in-touch/

Or we can solve through here, whichever you think is most comfortable.

It will be faster if I look myself.

Thanks for posting!

Rob Myrick

I’m not sure if that incorrect code is causing problems, but we just need to make sure that your page is parsing code correctly, or we will never know the real issue.

Thanks!

Hi hmwantz, I believe that your wp_head() function (located in header.php) might be in the incorrect location. Let me know when you take a look and I can help.

Thanks!