 |
The error happens only via API invitations? |
 |
As clarified, I can't do mass-edit either. I don't dare to click invite all from the admin because I don't want to spam hundreds of people again. They all got 4 of the same emails already |
|
|
Please, can I ask you to create a new ticket for the mass-edit part? |
 |
For admin GUI : https://bugs.limesurvey.org/view.php?id=18034 Fix are in https://github.com/LimeSurvey/LimeSurvey/pull/2352 |
|
|
DenisChenu - if fixe is marked as closed, doesn't it mean it's been merged and should have been on the latest version, which is the version I have? gabrieljenik - I think it's all around the same token issue so I don't believe there's a need for various issues here but feel free to, I'm not familiar with the codebase. |
|
|
Until it's possible to use a fixed version, could any of you indicate for me how to mark tokens as 'invited' in the database? Some sort of SQL would be great as I'm not sure if only one table is affects and I don't wanna dive so deeply into the code and end up messing the DB. Thanks |
|
|
reopen because system to create PR are updated |
|
|
PR 2691 tested OK towards this bug |
|
|
I've upgraded to Version 5.4.15+221212 and the bug still exists. Reminders were repeatedly sent (using $limeAPI->remind_participants() ) to the same people over and over, yet they haven't been marked. Obviously this is causing a big wave of complaints and reduces our reputation as a non-spammer. Also $limeAPI->invite_participants() keeps showing the same people over and over again |
|
|
|
|
|
From the creation of the issue it was about the API. There are still problems and they don't seem solved in the newest version. |
|
|
Yes, sorry. That was from the Admin GUI |
|
|
|
|
|
I've previously deployed the patch and things seemed better with it. I now upgraded to Version 5.5.2+230109 and it seems the patch isn't there either. So should I apply it again? |
|
|
Yes, please. The patch is not yet released. |
|
|
@DenisChenu Please find below some tests added for remote control invitation process. |
|
|
@DenisChenu This PR https://github.com/LimeSurvey/LimeSurvey/pull/2810 points to master, but it is outdated (see screenshot). I have tested this on 5.x and it fixes the issue, but ... we should probably have one PR for 5.x and one for master (master has the same issue). |
|
|
|
|
|
@tibor.pacalat : can you try if current master didn't broke Survey with token attribute encrypted ? I think there are an issue, but unsure my fix fix it. |
|
|
5.X : https://github.com/LimeSurvey/LimeSurvey/pull/2810 |
|
|
@DenisChenu not sure what you want me to test in master, can you please give me more detailed instructions? |
|
|
Just check what happen with Encrypted attribute I think it broke token table without the fix. Capture d’écran du 2023-10-24 17-29-17.png (35,475 bytes) |
|
|
In order
|
|
|
6.X / master : https://github.com/LimeSurvey/LimeSurvey/pull/3571 |
|
|
Quick review... We are using save instead of encryptSave? |
|
|
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=35672 |
|
|
Tested and merged. |
|
|
Fix committed to 5.x branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=35674 |
|
|
Fix committed to 5.x branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=35673 |
|
|
Fixed in Release 5.6.43+231030 |
- Anonymous
