Yes ! Confirm the issue !

And seeing "Survey participant summary" when the table does not exist is completely counterproductive and incomprehensible.

No way to allow register without create one particpant too …

The participant table is being created when you activate survey in closed mode.
You can also import participants from csv file before you activate survey.
If you want to import participants from csv file that has additional attributes, you can, but these attributes will be ignored -> this use case is something I can discuss with my team to see how we want to handle this.

@DenisChenu - No way to allow registering without creating one participant - also valid issue.

2 current issue (except the comprehensible part : "There is no participant table" somewhere)

• No way to manage Attributes (but even this one : it's great to allow edition without participant table)
• No way to have register survey without existing participant.

Idea

Capture d’écran du 2025-07-29 10-38-17.png (95,591 bytes)   

Capture d’écran du 2025-07-29 10-38-17.png (95,591 bytes)   

@tibor.pacalat

In general, one would want to configure additional participant attributes before activating the survey, in order to test settings such as branching logic based on those attributes or displaying them on the questionnaire screen etc. Testing should be done while the survey is not accessible from outside. Therefore, the current flow—where the participant table is only created upon activating the survey—is not ideal from a survey design perspective.

In general, one would want to configure additional participant attributes before activating the survey,

There are some other issue related to particpant_attribute

1. Allow updating attribute settings without token table
2. ATTRIBUTE_X always show as invalid if no token table , but settings is set

I have to report it…

Confirming the issue. In fact, it's been present since version 6.15.4, and it's quite annoying, so we had to roll back to version 6.15.3.

We did rollback to 6.15.3 because of this too.

Same here. We rolled back to 6.15.3 and been stuck there since.

Same problem here. Such user interface adjustments should be reviewed by an UI expert before making it into the next official release.
There had been quite a few changes recently which were poorly tested and lead to very annyoing UI design.
@tibor.pacalat, maybe you can discuss this internally on how to deal with this in order to provide better tested releases?

Create a temporary fork to have security fix but not participant update https://github.com/SondagesPro/LimeSurvey-SondagesPro/tree/temp/6.15.3_token

For this bug, when I need to move a massive emails in a .cvs file to LS, first need to activated the survey or create a first participant. That's
unnecessary waste of time because we need to create participant's tables so quick in my Job. For that reason we downgraded the LS version to 6.15.3 (stable version that don't have this problem) isn't recommended in any software for security.

This issue is highly concerning, as the inability to upload participant .csv files directly without first creating a dummy record significantly disrupts the survey workflow. It prevents a smooth setup process and makes it difficult to manage participant attributes efficiently. Being unable to create an empty participant table or properly import participant data from a .csv file represents a serious limitation that impacts both productivity and usability when setting up closed surveys.

This new version not only does not allow managing the participant attributes, but it also prevents uploading participants in bulk. This functionality is really necessary, since the definition of attributes enables the creation of respondent profiles within the questionnaires. It is truly concerning that this cannot be used in the new version.

Following up on this bug, we have noticed that it still hasn’t been addressed. We would really appreciate your help us in resolving it. This issue is extremely serious, not only because it causes delays and workflow disruptions, but also because the inability to create and manage attributes makes it very difficult to properly design and handle the questionnaires and filters, which are essential components for our work and for maintaining data reliability.
We sincerely appreciate any assistance you can provide to help us resolve this as soon as possible.

@tibor.pacalat, can you please assign this, we had the same feedback reported from several customers.