Timeline for Magento 1: Which ACL is related to the editor handle?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2016 at 16:56 | vote | accept | Raphael at Digital Pianism | ||
| Mar 8, 2016 at 10:07 | comment | added | Raphael at Digital Pianism | @fschmengler it was hard but I've found the root of my problem! | |
| Mar 8, 2016 at 10:06 | answer | added | Raphael at Digital Pianism | timeline score: 1 | |
| Mar 8, 2016 at 8:27 | comment | added | Raphael at Digital Pianism | @fschmengler you made interesting points, even if that does not help for this problem, it enlighted me on some mechanisms I wasn't aware of. I'm about to do more tests today, I'll update my question when I find more details | |
| Mar 8, 2016 at 8:14 | comment | added | Fabian Schmengler | But that still does not help you. The problem must be somewhere else. I'm sure, other pages with the editor handle work with restricted users. | |
| Mar 8, 2016 at 8:11 | comment | added | Fabian Schmengler | Actually it seems to be the other way around: if a block has an acl attribute it may not be removed. Weird. | |
| Mar 8, 2016 at 8:05 | comment | added | Fabian Schmengler |
Interesting question. I thought, layout and ACL were not coupled at all but I found that you can add a ACL restriction to <remove> elements: <remove name="BLOCKNAME" acl="RESOURCE" /> only removes the block if the user has permissions for RESOURCE. But the remove tag seems to be the only one and has nothing to do with the editor handle.
|
|
| Mar 7, 2016 at 16:45 | history | edited | Raphael at Digital Pianism | CC BY-SA 3.0 |
added 187 characters in body
|
| Mar 7, 2016 at 16:38 | history | asked | Raphael at Digital Pianism | CC BY-SA 3.0 |