[SOLVED] Delimiter fields not emptying/updating correctly

I´ve put quite a number of fields into a table/list that I created in the HTML area of the delimiter field.
Now when I want to clear the values of the corresponding fields in the backend aren´t emptied correctly and some (!) values aren´t changed.

This is what I get from a cb user fields database check:

CB fields data storage Database structure differences:
Table #__comprofiler Column avatar type is varchar(255) instead of text
Table #__comprofiler Column cb_profilbild type is varchar(255) instead of text
Table #__comprofiler Column website type is varchar(255) instead of text

The CB fields data storage database structure differences can be fixed (adjusted) by clicking here: Click here to Fix (adjust) all CB fields data storage database differences listed above (you can also Click here to preview fixing (adjusting) queries in a dry-run), but in all cases you need to backup database first as this adjustment is changing the database structure to match the needed structure for the installed version.
Click here to Show details

CB fields data storage database checks done. If all lines above are in green, test completed successfully. Otherwise, please take corrective measures proposed in red.

Any ideas?

Looks like you applied a quickfix to those columns and changed them from varchat to text to get around database column size limits. If intentional just ignore the tools check otherwise click the link to let tools fix it.

This shouldn't have anything to do with delimiter fields not working properly; please be more specific as to what is happening with them. Delimiter field display uses the description column of _comprofiler_fields.

Hello Kyle,

it looks like the conditionals plugin causes the problems. If a value is changed or deleted and the conditional for "show field" is triggered before the changes have been saved, the values won´t be written to the database. Does that make any sense to you? I am currently trying to work around this problem by making it a requirement to fill all fields or empty all fields before the "show"-condition can be changed.

EDIT: This thread here www.joomlapolis.com/forum/153-professional-member-support/224961-inconstancy-with-cb-conditional has the lowdown on why it appeared to me that the fields didn´t empty/update. A Reset does indeed solve the issue, but is too "dangerous" for me to implement, i.e. the users for sure will delete one entry and accidentally loose a lot of already entered data :p

There's no changing the behavior. It will either reset the values or it won't. Both have their issues so you need to pick which issues your users can live with. Resetting is the recommended usage and it's designed with resetting in mind, but it's disabled by default as it does cause data loss if a conditional mistake is made. Would value resetting on a field by field basis work better for your situation? As it maybe possible to implement that.

krileon wrote: ... Would value resetting on a field by field basis work better for your situation? As it maybe possible to implement that.

Either that or at least a warning about the data loss if fields aren´t empty.

Thanks for the speedy replies!

Michael