Loading...
 
Skip to main content

Features / Usability


Tiki 27.2, Polls do not accept spaces and accent characters anymore

We have juste upgraded from 24.3 to 27.2 and realised that when creating a poll, the spaces and accented character (é, è, etc.) are not saved in the database anymore.

If we look into the database we do see that the characters have been stripped before being commited to the table. And if we edit the database directly to add the spaces and accents, then they will be displayed on the Polls page afterward.

Is this a known problem or is there a new config option that we missed?

Stefan


Thanks for sharing this, Stefan. That definitely sounds like unexpected behavior—accented characters and spaces should not be stripped by default. This might be related to changes in character encoding or input sanitization in version 27.2. I’d recommend checking the GitHub issue tracker to see if others have reported similar problems or to submit a bug report directly.
Here’s the link to the GitHub issues page:
🔗 https://github.com/orgs/discourse/discussionsQuestion [SPAM LINK DELETED]
Hope this helps!


Upgrading from version 24.3 to 27.2 can cause issues with poll data. This is a known issue related to character encoding and is often caused by a misconfiguration in the new version. Check your configuration files for any changes [SPAM LINK DELETED] related to character encoding, such as UTF-8, as a missing or incorrect setting can strip out spaces and accented characters.

Has this been solved and if so is there a version 27.* update that can be installed?

Stefan Beaubien wrote:

We have juste upgraded from 24.3 to 27.2 and realised that when creating a poll, the spaces and accented character (é, è, etc.) are not saved in the database anymore.

If we look into the database we do see that the characters have been stripped before being commited to the table. And if we edit the database directly to add the spaces and accents, then they will be displayed on the Polls page afterward.

Is this a known problem or is there a new config option that we missed?

Stefan


Hi,

I am using version 27.3 and I am not experiencing the issue you are having. I have upgraded three times since then and have not had any encoding issues. Perhaps you should upgrade to 27.3.