Prestashop: issue with wrong Iso code for Argentina Language persist in Prestashop 1.7.7.0 beta 2

[TecnoHands]

Describe the bug

The ISO CODE For Argentina in prestashop is AG, but the correct is ES (Spanish LANG)

Expected behavior

guys Solve this issue for One time, This bug crash all the traslation function in the BO for cause of the ISO CODE, and if you change it to ES (The correct iso code) Prestashop Fucking off the entire translation function too.
This is not a new bug this is from 1.7.0.0 (2017 or 2018) we are in 2020.....
You only change the flag... the iso code continue bad. The flag We can change in the set up for lang and dont any problem....
The problem is with ISO CODE ISO_639-1

Steps to Reproduce

Install prestashop in spanish lang
Select Country Argentina
See the international option languages
ISO code is AG (BAD) -> (ES) Correct

Screenshots

In page where Help send the user to view the iso code:

Guys In ARGENTINA we speak SPANISH (ES), We dont speak French or other lang.
PLEASE SOLVE THIS BUG

Clean Install Prestashop 1.7.7.0

Change the iso code to the correct ES

After clean cache Fuck off the translation function for all languages

Console after change the iso code

When change the iso code to the incorrect iso code AG, the translate function works again

Additional information

• PrestaShop version: 1.7.7.0 BETA 2
  

• Versión PHP: 7.2.33

[prestashop-issue-bot[bot]]

Thanks for opening this issue! We will help you to keep its state consistent

[matks]

Hi @TecnoHands,

I can see you are frustrated in the tone you use but I must tell you that this cannot be done in this space. The use of words like "fuck" is clearly against our Code of Conduct.

That being said, about your bug:

It seems according to the standards that ISO code for Argentina is either AR or ARG => https://www.iso.org/obp/ui/#iso:code:3166:AR . I think you are mixing language codes and locale codes.

I also see you write this:

This is not a new bug this is from 1.7.0.0 (2017 or 2018) we are in 2020.....

We understand there might be a problem, and that it's important to some people. But our resources are limited, so we have to sort bug reports and work first on the most important bugs. This means that maybe this bug was reported in 2018 or 2016 or 2014, it does not matter. What is going to happen is this: we consider all confirmed bug reports, sort them and we start with the most important, the critical issues. Then when there is no more critical issues, we work on major issues. Then, we work on less-than-major issues. If a new major issue is reported in the meantime, it will be fixed _before_ minor issues. This is why the report date of a bug does not matter. It is not a "first reported, first fixed" todo-list. All bug reports are in a common backlog and we work on the top ones before we work on the ones below.

➡️ Our resources are limited and we can do only so much. If a bug is not currently in our top priority list, we will not work on it now.

We understand this can be frustrating but this is what happens to all big projects. Developer time is limited, so if the amount of issues opened in a certain timeframe exceeds the amount of issues that can be processed using the available developer time, tasks will simply pile up. This is common to ALL projects. This is very well explained by DHH in its blog post "Software has bugs. It's normal."

But here's the upside 😄 : PrestaShop is an open source, community project. If you find that any issue is critical for you, and it's important to have it fixed ASAP, then you can _invest_ into having it done. You can hire a developer to fix it, or if you are a developer yourself, you can try doing it on your own. The most important thing is to share that fix with everyone by submitting a Pull Request -- that's what the open source spirit is all about.

This would not be possible with proprietary software. With proprietary software only the vendor can modify the code, be it bug fixes or new features. Since PrestaShop is open source, you can participate in making it better for both you and every other users. And if other users do the same (pay for a bug fix to be fixed) and submit it to the project, you benefit from these other bug fixes ... without spending money neither time.

➡️ So to sum it up: like in every other open source project, you can either patiently wait for someone to fix it for free, or find the way to fix it on your own (eg. pay an expert).

[khouloudbelguith]

Hi @matks, @TecnoHands,

here's the PR: https://github.com/PrestaShop/PrestaShop/pull/16334 to fix the issue.
It is reported here: https://github.com/PrestaShop/PrestaShop/issues/16029
I tried with 1770rc1build1, I have the same issue

Ping @LouiseBonnard what do you think?

@TecnoHands, about translations, it is ok in my case
https://drive.google.com/file/d/1IE43Wum2YkvtladPf82wag8xv5p2UmO5/view?usp=sharing

Thanks!

[LouiseBonnard]

Hi there, see https://github.com/PrestaShop/PrestaShop/issues/16029#issuecomment-551079194 for some context. We are aware of this bug and the consequences it has for the users but, unfortunately, this is not something we will be able to fix in a minor version but the next major.

[khouloudbelguith]

Thanks @LouiseBonnard

So, this issue cannot be closed since it is not fixed, is it?

[LouiseBonnard]

If I'm not mistaken, the flag has been fixed but not the language.