https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-02-11T01:28:15ZEcoinformatics RedmineMetacat - Bug #4787: User having WRITE permission couldn't update a documenthttps://projects.ecoinformatics.org/ecoinfo/issues/4787?journal_id=164422010-02-11T01:28:15ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>This might be a regression due to recent access control handling changes. From my fuzzy memory, I seem to remember that we used to have some logic in the code that would check to see if an EML document was being updated whether there were changes to the access rules -- if not, then only write permission was needed for the update, but if access changes then ALL permission or ChangePermission permission would be needed. Maybe now we are failing to detect the case of an EML document being updated without changes to its access rules?</p> Metacat - Bug #4787: User having WRITE permission couldn't update a documenthttps://projects.ecoinformatics.org/ecoinfo/issues/4787?journal_id=164432010-02-22T17:47:31ZMichael Daigledaigle@nceas.ucsb.edu
<ul></ul><p>There was a white space issue when comparing database access rules to doc access rules. Trimmed the values before comparing and it works now.</p> Metacat - Bug #4787: User having WRITE permission couldn't update a documenthttps://projects.ecoinformatics.org/ecoinfo/issues/4787?journal_id=164442013-03-27T21:28:06ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 4787</p>