Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There's a way of call purposes-pt.json using the latets library version?. #423

Open
nicolasLaverde92 opened this issue Sep 25, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@nicolasLaverde92
Copy link

1.5.9

Describe with reproduction steps – What is the expected behavior?

We are using the last version of iabtf-es version 1.5.9 according with this PR #404 for gvl 3 version and new languages. But in our CMP ( quantcast ) we give the possibility to clients to select tcf2.0 or tcf 2.2

When they select portugues language Portuguess language in TCF2.0 this always fails cause is consuming the updated function changeLanguage where this PT language doesn't exist anymore.

Screenshot 2023-09-25 at 10 55 50 AM

for that reason that pt language is proccess as pt-pt and the file is trying to access is https://vendor-list.consensu.org/v2/purposes-pt-pt.json getting a GVL error....

there's a way I can call this purposes-pt.json for tcf 2.0 ? or this new changes are not compatible with thius old TCF version?

@nicolasLaverde92 nicolasLaverde92 added the bug Something isn't working label Sep 25, 2023
@nicolasLaverde92
Copy link
Author

@marco-prontera maybe there are some way?

@marco-prontera
Copy link
Contributor

@marco-prontera maybe there are some way?

HI, they often say not to use their URLs directly. Rather you have to host the files on your own server and get them from there. At that point I think you can easily rename the files in this way you can cover the requests. Unfortunately, the previous language management was wrong and not suitable for the new translation management. But since it's something totally manageable by CMPs, I don't think you have any problems.

I want to point out that I don't work for the IAB so I can't give you certainty. As you can see I'm only a contributor and not a collaborator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants