Disabling xml-invalid for the project

[tomkolp]

Describe the issue

How to disable xml-invalid quality checks for an entire project in docker. It was recently automatically added to the entire project. How can you do it the fastest? The whole operation will probably take several days.

I've been reading the documentation but only found information about QA exclusions that apply to a standard weblate installation, not in containers.

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

1 Go to string translation
2 See new quality checks, completely redundant throughout the project

Expected behavior

No response

Screenshots

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

Add ignore-xml-invalid to component flags.
See https://docs.weblate.org/en/latest/user/checks.html#xml-syntax and https://docs.weblate.org/en/latest/admin/projects.html#translation-flags

[tomkolp]

Add ignore-xml-invalid to component flags. See https://docs.weblate.org/en/latest/user/checks.html#xml-syntax and https://docs.weblate.org/en/latest/admin/projects.html#translation-flags

I know about the flag, but how do I add it to 3000 components at once?

I added a flag in the base file and it will be added automatically in newly created components. I know I can add it to the component as well, but I'd have to do it over 3000 times.

EDIT:
Might use WEBLATE_REMOVE_CHECK in docker compose, but what is the name of the variable for xml-invalid?

[nijel]

Use class name in WEBLATE_REMOVE_CHECK, those are documented in https://docs.weblate.org/en/latest/user/checks.html#xml-syntax

Maybe there is a bug in the check that it started to trigger now? It's not a new check.

[tomkolp]

We've always used <<player{text/text}>> , this check came out a few weeks ago for the first time.

[tomkolp]

I added to docker-compose:
WEBLATE_REMOVE_CHECK: weblate.checks.markup.XMLValidityCheck
I restarted the containers. The name of this check in the list of all changed its name from Polish to English. When I click on xml-invalid I get the page not found message. The following component have a check only now in English. Do I still need to force the rechecking somehow or is this some kind of bug? If I have to force it, how can I do it for all components?

[nijel]

You can force updating checks manually using https://docs.weblate.org/en/latest/admin/management.html#updatechecks, without that, the checks are updated once in a month (see https://docs.weblate.org/en/latest/admin/config.html#background-tasks).

[tomkolp]

I just wasn't sure if this behavior (message page cannot be displayed) is normal behavior after excluding checks.
I have enabled check recalculation for all components. Initially, I see that "xml-invalid" is disappearing. Seeing the speed of the operation, it will be completed in a few days.

Thanks for leading me to a solution.

[github-actions]

The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.

• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[nijel]

This turned out to be a bug in the XML check, I've just fixed that in 32220fc