If Lime Survey is installed in such a way that the root url for the survey is a long character string, the generated SURVEYURL may be longer than the line size of the email program.

This results in the email program splitting the survey link over multiple lines, and in many email programs, these split URL's no longer function (i.e. the portion of the URL that does not fit on the first line is visible, but no longer part of the actual URL). Clicking on such a broken link will lead to a failed attempt to access the survey, frustrating the invitee.

I just had a need to filter my tokens on a specifc attribute, but the search functionality seems only to adress tokens, names and email adress. But my custom attributes was not searched.
Fortunately I had uploaded my tokens in an orderly way, which made is possible to do what I wanted.

I run many surveys that use closed access and multiple token attributes for each user. I recycle several of these surveys over the course of an academic year, or from year to year.

In these surveys, there are several places where some text should change for each run of the survey, but should be consistent within the run. For example, one survey is used to collect vacation travel plans from students. The name of the vacation changes every time I run the survey, but it appears in several places within the survey and in the invitation emails. Similarly, I specify dates (used for input validation) that are the same for all students but change for each vacation.

Currently, I manage this by using a token attribute to specify the text, and refer to that attribute throughout the survey and email text as appropriate. This works, but it requires that I add the text as an attribute to the token for each student, even though it's the same for each student.

I would like to suggest a feature that would create a set of attributes for the survey, in addition to the attributes for each token.

there is only three Attribute must be filled:firstname lastname and email. so it limited much information for survey that the administrator want to know, it is very good for add one more Attribute, and it must be filled.

When I import a CSV file into the tokens table, using attribute_1, attribute_2, etc., is awkward, I'd much rather use company_name, website, etc., whatever my fields are.

Then conditions and defaults could use those same names, e.g. TOKEN:COMPANY_NAME

An auto-import function would be nice, something that could take a file like

email,website,company_name,year_founded,industry

and import it into the tokens table, automatically adding any new fields that weren't there.