Custom Query (73 matches)
Results (4 - 6 of 73)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12 | fixed | After an update or save sometimes old/stale data/vaules are shown | ||
| Description |
A browser refresh causes the new data to be shown, so the data is persisted but just not fetched in time to show updated values after redirect. This is not due to query caching, as previously believed. (Higher level caching is on in the global config but still needs to be turned on for each case where it is wanted). The solution is to add flush:true to save(), implemented in r178 as per http://jira.codehaus.org/browse/GRAILS-5111 |
|||
| #98 | fixed | Annotation based security is easy to bypass by adding ".html' to the URL | ||
| Description |
Upstream security issue, see: http://jira.grails.org/browse/GPACEGI-41 Recommended fix is to set Config.groovy: grails.mime.file.extensions = false This did not leave gnuMims completely open to the world since gnuMims was configured with pessimistic security. However a logged in user may access urls that they are not authorised to. |
|||
| #22 | fixed | Asset priorities and mandatory registration and testing. | ||
| Description |
For priority 1 assets having a drop down field or a check box where mandatory registration and testing required, registration renewal date can be selected is a feature that we should have. For example, High pressure vessels, cranes, etc would be asset that require distinction. You might wonder why this may be needed? A few reasons, 1 there is a prompt to personnel for regulatory requirements and 2 often audits want a list of assets that require registration. Also see ticket #34. |
|||
