Modifying the Blesta DB

[ehansen]

I'm working on integrating SMS into Blesta, and for authentication purposes (I don't want the user to send their passwords or something over plain text), I am wanting add another column to the users table. This would be a simple modification by adding a new column ("sms_key" or something) and populating that for people who agree to.

My question is how bad of an idea is this? I know you're not typically supposed to change tables and such of software that isn't yours, but I do not see how this change would be that bad.

[naja7host]

Of i have Well understand , you CAN add a custom field to the table client via settings , nô need to change via phpmyadmin .

[ehansen]

Originally Posted by naja7host

Of i have Well understand , you CAN add a custom field to the table client via settings , nô need to change via phpmyadmin .

Correction, can it be made to be read only? I just tested it an the user can edit the values when they modify their profile. This isn't something I want to be made possible.

[Paul]

You can toggle the visibility of custom fields, and if the client can't see it they can't update it.. but if they need to be able to see it and not update it what you could do is write a little code in the appropriate template file to do a query for the custom field and display it as text-only.

[ehansen]

Originally Posted by Paul

You can toggle the visibility of custom fields, and if the client can't see it they can't update it.. but if they need to be able to see it and not update it what you could do is write a little code in the appropriate template file to do a query for the custom field and display it as text-only.

If I do decide to leave it visible and editable by the client then for them to change it they just need to edit their profile, put in the new value, then update it?