-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Tapio Nurminen edited this page Apr 19, 2017
·
14 revisions
- up to 12 custom fields (text / select) can be used
- fields' types added to custom_settings
- labels and dropdown values defined in custom_values
- values get saved in applications/tblmembers
- only a super-admin or 1st level view can add members into groups
- currently either ordinary members can be given view rights or separate view users can be created
- if view is allowed to add members
- they can delete members
- they can add members into groups (but not define their role in that group)
- members added by view get automatically inserted into that view (members.inc.php::insert)
- views can always set a member as dead or as resigned
- views cannot see member's views
- membership in a suborganization is saved in table 'groups_members'
- views_members depends on groups_members so it is a view instead of an actual table
- adding to group is connected to view; a person belongs to a certain group in a certain role as part of a view
- _allowed_views keeps record of views that are available to the view that is logged in
- search can seek boolean fields too
- setting in coreConfig if boolean search is in use
- currently boolean searches hardcoded in search; these should be rewritten
- reference number: year, padding zeros, autoincrement + "tarkiste"
- if member is written a separate invoice (e.g. before mass invoicing), invoice is marked as individual invoice (is_midyear = 1)
- these members will not receive another invoice in the mass invoicing
- if invoicing address field is given in member info, this custom invoicing address overwrites normal member info in invoices
- is_foreign -setting defines whether Finnish bank transfer form is shown in invoices
- if is_foreign is checked, member is not included in report on postcode distribution
- _summary.php counts how many views users there are