Hello,

There's a bug with latest listing near xxxxx.

When location is set in English and you switch to RTL or another language you expect to see the location's native name if it was saved in the location DB but that's not happening as it only displays in English. However, when you switch to let's say Arabic and you select the same location in Arabic (displays correctly) and then switch to English then the location name correctly displays in English.

Attaching screenshots as reference.

Thanks

One more screenshot

@Wiz
That is correct, selected location is not stored in different locales. It's not expected user would be switching between locales except initial selection.

Yes locations are not stored in locales but they are stored in Location DB, English and as native.

Not sure though I follow the logic with how it's setup as I am able to initially set it up correctly in any language other than English, it would display correctly in native, and when switching to English it would correctly display in English but the same does not happen when setting it "initially" in English and switching to another language with the native location of that language saved in the Location DB.

Should work both ways, not one. Always expect the unexpected with user behavior.

No, locations saved into cookies are stored in cookies and not using database calls to get it's content/name.

Hmmm. Then why is it working perfectly fine when selecting the native name of the default location under any language but English?

The information stored in cookies came from where? a DB call, right? Take Arabic for example if the function that retrieves the location info to save in the cookie is retrieving and storing the location native and English names in the cookie when on the Arabic website, then why isn't it also retrieving and storing the English and Arabic native name when on the English website?

It should apply this same logic to all enabled languages. Cookies can be edited/updated so I don't understand what the issue is with fixing this bug.

Enlighten us please.

An update on an expected fix would be appreciated. To reiterate:

- If it works correctly under any language but English then it should also work correctly under English.

- There are many people that are bilingual, speak English / Spanish, English / Arabic, English / German etc. If an ad was posted under Spanish or Arabic with content in either languages and I was on the English site and can also converse in those other languages, then normally I'd switch over to the ad's site lang version for better viewing / reading.

Thanks

@Wiz
It's not expected for visitors to be cross-changing language of site. It's value in cookie to reduce number of calls to database, no plans to change that.

@MB

I think you're missing the point which I've stated over and over again but I'll give it one last shot.

Two languages: English and Arabic

Setting the default location under the Arabic locale/site adds BOTH Arabic and English location names to the cookie so when I switch to English from Arabic I see name correctly in English.

Now, let's switch to English (cleared cookies and everything).  Setting the default location under the English locale/site adds ONLY the English location name to the cookie so when I switch to Arabic I see English location name instead of Arabic.

The function or script responsible for calling the DB and/or storing the chosen default location names in the cookie is CORRECTLY doing it under the Arabic locale (for any language OTHER than English) but NOT under the English locale, get it?

Hope you understand now.

As for reducing number of calls, the process/call to DB happens only once when you set the default location and it's then stored in cookie - how is that any different from when it correctly calls the DB once then stores BOTH location values in the cookie under the Arabic locale?

I'm a logical person and am not trying to be difficult ... If I'm wrong then by all means correct me. I can fix this on my own as it's clearly a bug that you're so adamant about it not being a bug. I'm failing to understand your confusing logic.