#5345 - Required CPFs on join form do not save

By PDStig
Added 20th Feb 2023, 10:21 PM
9 views

Identifier	#5345
Issue type	Major issue (breaks an entire feature)
Title	Required CPFs on join form do not save
Status	Closed (cannot reproduce)
Handling member	PDStig
Addon	General / Uncategorised
Description	It appears when members fill out required CPFs on the join form, they do not actually get saved to their profile. (Happened on a long_trans field. Have not tested others).
Steps to reproduce	1. Install without content translation support 2. Create a required profile field of type long_trans (paragraph of translatable/comcode support) and show on join form 3. Enable the option to require staff approval of accounts (might or might not be related to this bug) 4. Fill out the join form to make a new member
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 20th Feb 2023, 10:29 PM

Error log shows it's a database issue. Field __text_parsed does not have a default value. Interestingly, this error also caused the CPF to no longer be a required field despite it being marked required in the settings.

EDIT: Talked to Patrick and it was also a visible error, not just one buried in the log.

By Guest posted 21st Feb 2023, 3:28 PM

Upgraded to major bug because this causes lots of profile issues. Seems to be an issue in how comcode columns are being saved in the database for non-multi-lang sites. Will continue to investigate.

By Guest posted 21st Feb 2023, 3:33 PM

I was unable to reproduce on my dev machine; only happened on a production server. My dev install was not creating those __text_parsed fields without a prefix name.

By Guest posted 22nd Feb 2023, 5:03 PM

Production server is running MariaDB 10.3, and the dev machine is running 10.6

By Guest posted 22nd Feb 2023, 6:07 PM

We tried ensuring database strict mode was on, checking database consistency, running MySQL repair tool, adding FULLTEXT index to the field, switching PHP versions, etc. and could not reproduce on the dev machine. Was probably a freak incident.

By Guest posted 22nd Feb 2023, 6:11 PM

Suspicion is that the '__text_parsed' field was accidentally created somehow, but not by Composr.