Field xxxx is not defined in $validfields in class vb_datamanager_user

[sv1cec]

KirbyDE,

Thanks.

So what you are saying, is that if someone defines new columns in user table, one should create a plugin, hooked at userdata_start, with the definiitions of the new columns?

A couple more questions, if you would allow me:

Which other tables are treated the same way? In other words, for which other tables, we should define custom columns in this way?

Are the types used in this declaration described some where? INT, UINT, STR, what are the others supported? For example, I used to have STR_NOHTML in globalize function before, is this still supported?

Thanks and rgds