Opened 15 years ago
Closed 15 years ago
#1112 closed enhancement (fixed)
Create new items with project default properties from active project
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 2.9 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
When creating new items and a project that has project defaults is active the project default properties should be set on the new items.
Change History (10)
comment:1 by , 15 years ago
| Milestone: | → BASE 2.9 |
|---|
comment:2 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:6 by , 15 years ago
comment:7 by , 15 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
There is a serious bug in the fix for this that causes all users to get read access to everything. The problem is related to the lines in [4533] that contains:
pp.granted |= Permission.grant(Permission.READ)
This may seem harmless but actually changes the value of the PluginPermission.NO_PLUGIN which should never change... The root cause is of course the bad design in PluginPermission class which exposes the internal variables. It may make sense to have them readable, but they should at least be "final".
comment:8 by , 15 years ago
| Status: | reopened → new |
|---|
comment:9 by , 15 years ago
| Status: | new → assigned |
|---|
comment:10 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [4527]) Fixes #1112: Create new items with project default properties from active project