Closed (fixed)
Project:
Wysiwyg API template plugin
Version:
7.x-2.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2012 at 18:35 UTC
Updated:
17 Aug 2012 at 14:28 UTC
Jump to comment: Most recent file
Comments
Comment #1
guybedford commentedWould certainly make sense to have a wysiwyg templates permission. I'm more than happy to add this, but if anyone wants to submit a patch, that is welcome as well.
Is there not a more generic permission that can be used for the exporting though?
Comment #2
skwashd commentedThe attached patch adds a new "administer wysiwyg template" permission. It is based on the current 7.x-2.x branch.
Comment #3
skwashd commentedfixing status
Comment #4
guybedford commentedThanks, that seems great for the menu permissions. We still need to add the import permissions I believe. I will be looking into this when I do a full review later this month.
Comment #5
skwashd commentedI agree the import permissions are needed - when the import code lands in the tree. Right now I have a site where I want to allow users to edit templates, but I don't want to grant them access to manage filters. This provides finer grained access controls for the existing functionality.
If this is in the repo, recidive can add the import permissions when he next rerolls his import patch.
Comment #6
recidive commentedIMO we should get the permissions for what we already have.
I'll make sure to add a permission for import/export.
Comment #7
recidive commentedPatch no longer applies. Need to be rerolled adding a 'access callback' to the import menu item, since this run php code.
Comment #8
recidive commentedOk, I re-rolled the patch adding 'import wysiwyg template' permission.
Comment #9
skwashd commentedWe are using this internally and it works as advertised. Can I RTBC a reroll of a patch I wrote?
Comment #10
recidive commentedI'll let @guybedford weigh in before committing this.
Comment #11
guybedford commentedI may have suggested the import permissions without properly thinking it through... is this really necessary?
Personally I'm a fan of simple permissions - I just thought there may be deeper security implications, but I don't think there really are.
Happy to go ahead with the permissions commit, just decide if we really need the import permissions or not!
Comment #12
skwashd commentedA separate permission is required as it allows execution of PHP code - which is a security consideration.
Comment #13
guybedford commentedOk yes of course, makes sense.
Comment #14
adriaanm commentedCan we get this in a new release?
Comment #15
guybedford commentedSure I've committed this into the latest release.