[5044] apps/votes: add token generation component to dashboard, use async tasks #4468
Conversation
|
|
||
| <p class="form-hint">{% blocktranslate %}For voting in the third phase, participants need a voting code. You can generate and download the codes here. {% endblocktranslate %}</p> | ||
| <p>{% blocktranslate count counter=number_of_module_tokens %} | ||
| One code has been generated for this module so far. |
There was a problem hiding this comment.
out of curiosity. with adding the voting module it will generate one code per se?
There was a problem hiding this comment.
No, you are right, we should use the number here as well as in other languages the 0 might have an extra form. In English and German the plural is used, so it should be fine. I will check to be sure, though!
There was a problem hiding this comment.
Yes, it does work with the 0 in English and it will also be fine in German with the translation
There was a problem hiding this comment.
Yeah cool, it is sooooo much faster now!
I checked what happens when the unique constraint is violated, then the whole background task fails and no code is generated... but should we merge and handle that later then @fuzzylogic2000 ?
@Rineee Yes, let's merge and I will add a task to handle that. Would be good to do with tests anyway. :) |
This is the generation in an extra dashboard component. It puts the bulk_create in tasks split up in chunks of 100,000. So, to test remember to start the background tasks.