| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
existing owner_compliance_control_set_ids. Refs #6960
|
|
|
|
and imports. Refs #6960
|
|
- Update the form
- Use policies and update the seeds accordingly
- Add a link in the navbar(s)
|
|
|
|
|
|
And define policies
|
|
|
|
And rename resource methods for better consistency
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disable traffic option in TomTom API invocations. Fixes #6661
|
|
6920 activate newly created referentials
|
|
Fix schedules editor. Refs #6864
|
|
|
|
|
|
|
|
|
|
As long as one arrives after 11pm and leaves before 1am
|
|
|
|
|
|
|
|
6627: Add Chouette favicon
|
|
6572 Create Referentials in a pending state
|
|
af83/6858-workbenches-show--disallow-deletion-of-pending-referent
6858: Workbenches#show: Don't allow pending referentials to be selected
|
|
6841 Revert useless and harmful migration
|
|
|
|
|
|
And fix a bug preventing the deletion of referentials without a schema
|
|
Disable the checkboxes next to pending referentials. This prevents them
from being deleted by the batch deletion operation.
In general it seems like we shouldn't be operating on pending
referentials, so if any new batch actions are added, it would make sense
to me for the checkboxes to stay disabled.
We want to disallow deletion of pending referentials because this can
put the data in an inconsistent state that requires manual intervention
to clean (I think).
Refs #6858
|
|
|
|
|
|
|