search

WeblateOrg / weblate

Web based localization tool with tight version control integration.
https://weblate.org/
GNU General Public License v3.0
4.5k stars 989 forks source link

Can't dismiss warnings ("Things to check") on projects where I'm the admin #6467

Closed realpixelcode closed 2 years ago

realpixelcode commented 3 years ago

I'm the creator and admin of the Sijacom project on Bubu's Weblate server. There are some warnings about some translation strings, for example unchanged translation or The string uses three dots (...) instead of an ellipsis character (…).

Trying to dismiss those warnings fails and I always get the error "Forbidden" in a red popup. This happens regardless of the language.

I have no clue what might be the reason and Bubu (the server admin) has already looked at the logs but didn't find anything.

unchanged translation warning:

Sijacom Weblate forbidden before

Forbidden error after clicking on Dismiss:

Sijacom Weblate forbidden after

nijel commented 3 years ago

Is the check actually dismissed? How does it look when you reload the page? Do you get any JavaScript errors in the browser?

Bubu commented 3 years ago

It produces a 403 error server side (seen in webserver logs, I can't see anything logged by weblate about this.)

(So I don't think it is dismissed successfully, but OP needs to fully confirm that).

realpixelcode commented 3 years ago

Is the check actually dismissed? How does it look when you reload the page? Do you get any JavaScript errors in the browser?

After re-loading the page, the unchanged translation warning is still there.

In the console, there's the error POST https://weblate.bubu1.eu/js/ignore-check/6663 – 403 Forbidden as well as the warning: 

Source Map Error: Error: request failed with status 404
Resource address: https://weblate.bubu1.eu/static/CACHE/css/output.cade745eae67.css
Source Map Address: bootstrap-datepicker3.css.map

There are no errors or warnings in the network log (besides the 403 above).

realpixelcode commented 3 years ago

Now, that's weird. First, I tried it with Firefox where I received the 403. Just now, I tried it with Ungoogled Chromium where it seems to work. How is that? Is it Firefox' fault? I use some privacy addons such as uBlock Origin or uMatrix but they don't block anything on Weblate. Also, I use uBlock Origin in Ungoogled Chromium as well 🤔

nijel commented 3 years ago

It seems that some portion of JavaScript was not executed in Firefox. Can you try disabling extensions in Firefox if that makes any difference? I do use Firefox and it works just fine here...

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

nijel commented 3 years ago

You can also try removing cookies for the domain. I've seen some similar weird errors when bot secure and insecure cookies were set in the browser.

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!