You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the site.yaml where the session name can be configured, if the session name contains a space a cookie error is thrown when trying to initiate the session. There is also a field in the Admin Plugin>Configuration where this value is set by the user. The error "Cookie names cannot contain any of the following '=,; \t\r\n\013\014'" is thrown. This is easily replicated.
It would be logical to expect from a user not to introduce other characters in the session name, but it is not immediately apparent to the user that this error is due to the space in the session name. The user may think that the session name could be his site name since the default session name is "grav-site".
Either there has to be a strong warning that no spaces are allowed or spaces need to be converted into a different character.
The text was updated successfully, but these errors were encountered:
In the site.yaml where the session name can be configured, if the session name contains a space a cookie error is thrown when trying to initiate the session. There is also a field in the Admin Plugin>Configuration where this value is set by the user. The error "Cookie names cannot contain any of the following '=,; \t\r\n\013\014'" is thrown. This is easily replicated.
It would be logical to expect from a user not to introduce other characters in the session name, but it is not immediately apparent to the user that this error is due to the space in the session name. The user may think that the session name could be his site name since the default session name is "grav-site".
Either there has to be a strong warning that no spaces are allowed or spaces need to be converted into a different character.
The text was updated successfully, but these errors were encountered: