Something went wrong while setting issue due date.
check_schema should be reviewed
Closed
check_schema should be reviewed
We have a function check_schema in functions.inc, which is called in 2 occasions:
- In the setup, after the LDAP step
- At login, if config option schema check is activated
But this function in last version only checks for gosaLockEntry, to make sure that core-fd is there, and that’s it. There is a check for nis, but it’s flagged non-mandatory and ignored. And there is a check for mixed group misconfiguration which is useful.
Should we test for more schemas? Is the separation between mandatory tests or not useful? Should nis be mandatory? (for 1.0.15 at least as posix support is still in core)
(from redmine: issue id 5057, created on 2016-08-09, closed on 2016-08-10)
- Relations:
- relates #5003 (closed)
- Changesets:
- Revision 62f937e9 by Côme Chilliet on 2016-08-10T09:20:59.000Z:
Fixes #5057 check_schemas should check for all FD schemas. non-mandatory should show as warning.
- Revision 54380a72 by Côme Chilliet on 2016-08-10T09:22:03.000Z:
Fixes #5057 check_schemas should check for all FD schemas. non-mandatory should show as warning.
- Revision 205ec631 by Côme Chilliet on 2016-08-10T12:17:59.000Z:
Fixes #5057 Change error message for a better one when a schema is missing
- Revision d434d742 by Côme Chilliet on 2016-08-10T12:18:40.000Z:
Fixes #5057 Change error message for a better one when a schema is missing
- Revision 9f1968e5 by Côme Chilliet on 2016-08-10T12:52:29.000Z:
Fixes #5057 Check the right var
- Revision 40fca260 by Côme Chilliet on 2016-08-10T12:52:57.000Z:
Fixes #5057 Check the right var
- Custom Fields:
- Bug in version: 1.0.14