[tgmorris]

Originally Posted by Kaitlyn

I think what is happening is that when a new account is signed up the userfields (5,6,7) aren't getting populated, which does happen if the fields are required (ugly) or the users save their options (pain).

-K

Right. It's necessary to run an update query on the db so it will establish values for existing users. The simplest thing to do is to manually run a query when first establishing this mod to set the default values. Something along the lines of

UPDATE userfield SET FIELD5='Disable', FIELD6='Compact', FIELD7=30 WHERE FIELD5<>'Enable';

should work even if you have existing users. If it's empty to begin with it will get populated with 'Disable' and if it's set to 'Enable' it won't be touched. Of course the FIELDx names should be changed to whatever is correct for the specific implementation.

I seem to recall documenting this a long time ago but can't find it at the moment. :disappointed: