kcaluwae

@theotest

Are you able to use the language switcher at the homepage?
I think I have a similar issue, my homepage is always shown in English and I can’t switch to Dutch unless I clear the cache. Then I can switch to Dutch but not long because after a while it’s again only showing the English version.

My thread: https://www.ads-software.com/support/topic/polylang-language-switcher-not-working-homepage/

@celine13 Ignore my previous message. This morning we’re facing the same issue back again…

@celine13 Are you still having issues? They seem to have disappeared on our site today. (without doing anything actually)

Maybe just temporary, don’t know…

@celine13
Not yet, unfortunately. I was hoping for an answer to know if I can safely disable the language detection on the homepage. I suppose that is causing this issue.

Do you have anything else that could be caching your website? Do you work with cloudflare?

@jcastaneda
Thanks for the code snippet. First time I edited the functions.php file like this and it worked.

Uploaded the JS file, modified the code snippet slightly so it’s called asynchronous and on the specific page only. It was actually a lot easier than I expected.
??

Are both pages linked? If you build a page you will get a language box (called languages) on the top right side of the screen. This is where you can choose which language the page is but another function is that you can indicate which posts are their counterparts in the languages you’re writing in.

Eg.

Page 1 = Hungarian article about meditation
The top box in the languages section will show Hungarian.
Beneath that you will have an empty box with a plus sign with the English flag.

To add a translation in English you click on the plus sign next to the English flag. This will create a new page and automatically link this page to your other Hungarian page. (indicating it is the translation.

If you already have your English page but they’re not linked. You can check this as both pages will show a plus, once they’re linked they will show the translated page title, you start typing the title of this English page in the box next to the plus. If has an autocomplete function. You select your page title and hit enter. Now the pages are linked and your problem should be fixed.

Thanks @sterndata, they are a bit expensive at the current stage but I will keep it in mind once I start earning some serious money with my site.

OK thanks @jcastaneda.

A plugin would probably be the easiest solution but as this is just one small script and it will probably be just for this one post I don’t want to add another plugin that potentially slows down my site.

I already created a child theme for my site. Once I have a child theme I can safely add this code to my child theme’s functions.php and I don’t need the functionality plugin.
Am I right?

Hi @chouby,

I would really appreciate if you could have a look at my questions.

Thanks,
Kris

Hi, I would appreciate if somebody could provide me some help with this question.

I see how this problem is resolved for users of WP Rocket caching so I wonder if a solution could also be provided for W3 cache users.

Also, please in the meantime let me know if deactivating ‘Detect browser language’ would stop this from happening and if this would not break my permalink settings.

Thanks.

Thanks @bogdanstratulat
Can it be related to this? : https://github.com/polylang/polylang/issues/236

• This reply was modified 6 years, 3 months ago by kcaluwae.

Done.

@supportray

Thanks for getting back to me.
I missed the 403 error on the hotel images. Thanks for pointing that out.

Unfortunately removing googlebot doesn’t solve the problem. The noscript tag is still there and I’m still not sure that it’s (only) the noscript tag that causes the error. I did notice that removing the noscript tag solved the problem but I’m trying to understand what happens here and therefore did some tests on my staging site.

On my staging site, which is an identical copy, I don’t have these issues.
I see that the HTML that is being generated is different

Staging : <a href="https://www.wapititravel.com/blog/wapiti-staging/?thirstylink=the-royal-park-hotel-kyoto"><img src="https://i2.wp.com/www.wapititravel.com/blog/wapiti-staging/wp-content/uploads/2018/06/royal_park_hotel_kyoto_sanjo.jpg?resize=300%2C262&ssl=1" alt="The Royal Park Hotel Kyoto Sanjo" width="300" height="262" /><noscript><img src="https://i2.wp.com/www.wapititravel.com/blog/wapiti-staging/wp-content/uploads/2018/06/royal_park_hotel_kyoto_sanjo.jpg?resize=300%2C262&ssl=1" alt="The Royal Park Hotel Kyoto Sanjo" width="300" height="262" /></noscript></a>

Production : <a href="https://www.wapititravel.com/blog/goto/the-royal-park-hotel-kyoto/" title="The Royal Park Hotel Kyoto" rel="nofollow noopener noreferrer" target="_blank"><img src="https://i1.wp.com/www.wapititravel.com/blog/wp-content/uploads/2018/06/royal_park_hotel_kyoto_sanjo.jpg?resize=300%2C262&ssl=1" alt="The Royal Park Hotel Kyoto Sanjo" width="300" height="262" /><noscript><img src="https://i1.wp.com/www.wapititravel.com/blog/wp-content/uploads/2018/06/royal_park_hotel_kyoto_sanjo.jpg?resize=300%2C262&ssl=1" alt="The Royal Park Hotel Kyoto Sanjo" width="300" height="262" /></noscript></a>

I did not compare both in great detail but as you can see the noscript tag is there in both instances. 1 difference I note is that on production I get a whole lot of attributes in the a-tag that I don’t have on the staging site.

I added the link in the same way by editing the picture in wordpress and making it link to a custom URL where I entered the affiliate link manually.

I used to have this picture attached to the affiliate link but I detached the image. I ‘m not quite sure if the attached images automatically generate links. I was hoping that this link would cause the attributes to appear (and somehow would have been broken on my staging site because of the copy) but that’s not the case.

I tried to remove the extra attributes in the developer tools but as soon as I remove an attribute I seem to break my link. Clicking the image doesn’t do anything anymore. Compare this to the faulty scenario where clicking the image opens a blank new page and shows 403-error in the console.

ThirstyAffiliate’s settings on both enviroments are the same. Further insights on why these attributes appear on production and not staging would be helpful.

• This reply was modified 6 years, 4 months ago by kcaluwae.
• This reply was modified 6 years, 4 months ago by kcaluwae.

FYI I checked the sitemaps, they do not contain the affiliate links.

I’m not sure if it’s related to the noscript tag.
Another one of the 403 errors is coming from this affiliate URL :
https://www.wapititravel.com/blog/goto/the-royal-park-hotel-kyoto/

The error is found on this page.
https://www.wapititravel.com/blog/en/3-week-itinerary-japan/

Search for ‘Royal Park hotel Kyoto’ and you will find a section with 2 links. One in the text as a plain link and one at the bottom as a button. I’m not sure which one causes this 403 error but if I inspect the links with developer tools both contain the ‘nofollow’ attribute.