Replies: 3 comments 1 reply
-
How many files would match? As a workaround, you can install the add-on via API. |
Beta Was this translation helpful? Give feedback.
-
About 1080 files in a nested folder structure. I accidentally managed to install it, but with a wrong configuration. It showed all files (but said it wouldn't match them). I installed it anyway and changed the wrong monolingual base filename via api to prevent the timeout, thanks! I don't see any activity logs when clicking on the "View logs" button of the add-on though. Is there a way to trigger a scan? |
Beta Was this translation helpful? Give feedback.
-
#14361 seems to have solved the issue. After updating weblate it worked. Thanks! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I’m trying to set up a self-hosted Weblate instance running in a Docker container. I have a large number of files that need translation, so I want to use the Component Discovery addon to automate component creation.
I have already created a project and added a base component to it. However, when I try to add the Component Discovery addon, Weblate times out before I can confirm the “these files will be matched” alert.
After this happens, Weblate remains inaccessible for about two hours, displaying a timeout error. Once it becomes accessible again, the addon setup is lost, and the Component Discovery addon is not enabled.
I’ve attempted this four times, but the issue persists.
Configuration:
Server/Path/Data/Languages/(?P<language>[^/.]*)/(?P<component>.+)/public_(?P=language)\.yml
Server/Path/Data/Languages/en/{{ originalHierarchy }}/{{ component }}_en.yml
Example paths in my repo:
Server/Path/Data/Languages/en/ui/screens/public_en.yml
Server/Path/Data/Languages/en/mails/verification/public_en.yml
Am I doing something wrong, or is there a known workaround for this issue?
Beta Was this translation helpful? Give feedback.
All reactions