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

[Bug]: "The Meta Version field is required" when installing languages #1097

Open
antoniozh opened this issue Oct 24, 2024 · 3 comments
Open

Comments

@antoniozh
Copy link
Contributor

antoniozh commented Oct 24, 2024

What happened?

When installing languages from the marketplace, it seems like the API returns languages without the version field. Unfortunately, I get this exception as a notification: "The Meta Version field is required."
This response comes back when trying to install new languages:

{
  "#notification": "    <div\n        class=\"alert alert-danger\"\n        data-control=\"flash-message\"\n        data-allow-dismiss=\"false\"\n        role=\"alert\"\n    >\n                    <p>The Meta Version field is required.</p>\n            </div>\n    ",
  "X_IGNITER_ERROR_FIELDS": {
    "items.0.ver": [
      "The Meta Version field is required."
    ]
  }
}

Also, the confirmation dialogue shows no version number, maybe the API left out the version of the language packs?

What did you expect to happen?

Languages to be installed seamlessly

Version

3.x

What browser are you seeing the problem on?

Chrome, Microsoft Edge

Relevant log output

{
  "#notification": "    <div\n        class=\"alert alert-danger\"\n        data-control=\"flash-message\"\n        data-allow-dismiss=\"false\"\n        role=\"alert\"\n    >\n                    <p>The Meta Version field is required.</p>\n            </div>\n    ",
  "X_IGNITER_ERROR_FIELDS": {
    "items.0.ver": [
      "The Meta Version field is required."
    ]
  }
}
@dextar47
Copy link

Getting the same error when installing new language

@webgrafia
Copy link

same problem to me

@nitroglyzerin
Copy link

Bug happend to me too.
Is a fix in Progress or a workaround possible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants