1 - You say that e-mail field can be used to send out notifications, but Cobalt users that have "public can post records" the e-mail field could have option to set it as unique.
Joomla has that feature, 1 e-mail per user.
If i set "public can post records" but i want to allow only 1 record per someone that is not registered threw Joomla (ex: bussiness listings). This "unique" feature would help the fact that the administrator doesn't have to:
- acess backoffice
- Go to a record to approve
- check if the e-mail is already on the database
go back to the record and approve if e-mail does not exist
2 - I believe it was already mentioned in this forum that an sql option would be great in most fields. For inserting data into fields and to write data into other tables threw querys... specially the jos_user table.
The basic is something like "register and add record" on a single form. If the field e-mail would allow to execute sql queries i could create an username field and insert the value in jos_user table.
Password field could allow to insert data into jos_user table, also allowing an adittional "verify password" field.
3 - An sql field to retrieve data from a specific table and display it like a type_of_field (checkboxes, dropdown, multi-select, etc).
This would allow for example, that in the same form appear Register fields and then Cobalt Type:
from jos_user table
username:
password:
Select your language:
Cobalt Type
But also complete interaction with every component. Not so user-friendly but possible with few troubles.
Idea
Announcement
Conversation
Praise
Problem
Question
Open
1 - You say that e-mail field can be used to send out notifications, but Cobalt users that have "public can post records" the e-mail field could have option to set it as unique.
Joomla has that feature, 1 e-mail per user.
If i set "public can post records" but i want to allow only 1 record per someone that is not registered threw Joomla (ex: bussiness listings). This "unique" feature would help the fact that the administrator doesn't have to:
go back to the record and approve if e-mail does not exist
2 - I believe it was already mentioned in this forum that an sql option would be great in most fields. For inserting data into fields and to write data into other tables threw querys... specially the jos_user table.
The basic is something like "register and add record" on a single form. If the field e-mail would allow to execute sql queries i could create an username field and insert the value in jos_user table.
Password field could allow to insert data into jos_user table, also allowing an adittional "verify password" field.
3 - An sql field to retrieve data from a specific table and display it like a type_of_field (checkboxes, dropdown, multi-select, etc).
This would allow for example, that in the same form appear Register fields and then Cobalt Type:
from jos_user table
username:
password:
Select your language:
Cobalt Type
But also complete interaction with every component. Not so user-friendly but possible with few troubles.