Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Readonly fee field

Readonly fee field 10 years 3 months ago #22515

  • webweaver
  • webweaver's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 0
We have a segment field synched with CB that is assigned by an administrator. Users in different segments have to pay different fees. Unfortunately it can only be used in fee calculations if it is displayed and editable by the user. It would be nice to have a "readonly" setting in fields so we can display the value and use it for calculation, but the user won't be able to edit the actual value.

Please Log in or Create an account to join the conversation.

Readonly fee field 10 years 3 months ago #22516

  • nathan.dth
  • nathan.dth's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 1857
  • Karma: 19
  • Thank you received: 218
You can do this already! You can't make ONE field read-only, but in DT Reg configuration, there is a parameter for making the profile sync Read Only. This will make all data that is imported from the user profile to be read only.

Please Log in or Create an account to join the conversation.

Nathan is no longer affiliated with DTH since the recent acquisition. You can connect with him and get any type of Joomla website help at www.JoomlaEmployee.com .

Readonly fee field 10 years 3 months ago #22588

  • wowza2
  • wowza2's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 11
  • Thank you received: 0

You can't make ONE field read-only ... This will make all data that is imported from the user profile to be read only

The View Only Profile Data option is currently too restrictive, allowing for protection of ALL populated fields for ALL or NO events rather than by field in an event! :x

Suggestions:
  • Why couldn't you add a Protected classification to a field's setting in the event's definition panel? It could be a third option to Required? No|Yes|Protected.
  • A (poorer) alternative would be to have a Protected Default Setting in the Field Management definitions.
  • Ideally, add a ACL condition to the Conditional Options section for every field defined.

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.122 seconds