Closed DeanGonzalez closed 8 years ago
After do some testing over the permissions stuff, we still having some problems here
@bryanboza if the are only losing the job in H2 this is NOT a problem. There is a slow query timeout in h2 and h2 is not a production DB. @freddyucv @jgambarios lets not work on this if that is he case
This is not a trivial fix @jtesser and it is not part of the original issue reported here. I would create a separate issue for that case.
Following what Daniel and Jason said:
"After you go to the site properties --> Permissions, and reset the permissions stuff over the site, when you come back to the user permissions and try to apply cascade permissions again, we are loosing one by one every category...."
I will clean up this ticket and we will back to work on it.
I created a separated issue for the h2 error: https://github.com/dotCMS/core/issues/9014 And another for the auto refresh problem: https://github.com/dotCMS/core/issues/9015
@freddyucv please remember to include the Functional Tests along with the new requested changes, we missed those tests in the previous merge.
Similar issue was tested in Client running 3.3.1 and locally using Starter Data.
Support Ticket: https://my.dotcms.com/tickets/detail.dot?id=c32027ac-4c8f-410d-a0e7-b17d630e2b9b
Please test.
Tested on dotcms 3.5 nightly build Linux/Postgres
"1- Login as admin 2- Go to CMS Admin // Users 3- Click on a User's Name 4- Click on Permissions Tab 5- Under ""All Hosts"", give the user Publish access to all objects (Hosts, Folders, Containers, etc.), click the ""Cascade Changes"" checkbox and click the ""Apply Changes"" button. "
Failures: Failed to Cascade Containers, Templates, Template-layouts, and Rules
screenshot of what was cascaded: http://screencast.com/t/cEmgoOM5y
screenshot of permissions not fully inherited on host: http://screencast.com/t/N4O0GmbT
No errors in the log - but seems to have completed https://gist.github.com/DeanGonzalez/61062bfa4db9867fe7801309c643af65