Prop editor doesn't seem to respect user start forms folder
Hey great job on the package, just tested and it seems like the prop editor outputs all folders and forms and doesn't take the user start folder into account...
When we designed this functionality we wanted to restrict only the nodes in the Forms-section, so you couldn't edit the nodes you didn't have access to.
Put inserting wouldn't be a problem because maybe you couldn't edit form X (because in our use case there was an editor that did most of the editing of the forms) but you could insert it into specific pages.
So it sort of by design, but I see your point. Wondering what the best way is to fix this? Any suggestions,
Well you could make it a config option on the prop editor... , simple checkbox if that is checked then make sure to check the user folder permission
Since in our case we are running a multi site Umbraco instance where user x shouldn't have any access to an other site's forms (each site will have its forms in a separate folder)
We have a very similar scenario where a multi-site Umbraco install has several users who all need to be restricted to their own set of forms, so it would be nice to be able to limit the form picker list to the start node(s) of the current user.
Prop editor doesn't seem to respect user start forms folder
Hey great job on the package, just tested and it seems like the prop editor outputs all folders and forms and doesn't take the user start folder into account...
Hi Tim,
thanks for your kuddoos! Can you send a picture about what you mean?
Thanks, Jeffrey
Sure thing,
So this is how the entire forms tree looks
The user has been restricted to 'Folder' and after that only sees this in the Forms tree
But when using the form picker prop editor he can see the entire tree and forms collection
Looking at the code for the prop editor it doesn't seem to take it into account...
Hi Tim,
thanks for the pictures. That explains a lot.
When we designed this functionality we wanted to restrict only the nodes in the Forms-section, so you couldn't edit the nodes you didn't have access to.
Put inserting wouldn't be a problem because maybe you couldn't edit form X (because in our use case there was an editor that did most of the editing of the forms) but you could insert it into specific pages.
So it sort of by design, but I see your point. Wondering what the best way is to fix this? Any suggestions,
Jeffrey
p.s.: GitHub will be updated soon :)
Well you could make it a config option on the prop editor... , simple checkbox if that is checked then make sure to check the user folder permission
Since in our case we are running a multi site Umbraco instance where user x shouldn't have any access to an other site's forms (each site will have its forms in a separate folder)
Ow and on a side not code on github seems to be outdated... (but again thanks for sharing :) )
Hi Tim,
I've just updated the Github source code to include the latest changes. Should be all up-to-date now.
https://github.com/PerplexInternetmarketing/Perplex-Umbraco-Forms/
Awesome, thanks Timo!
Was this configuration option ever implemented?
We have a very similar scenario where a multi-site Umbraco install has several users who all need to be restricted to their own set of forms, so it would be nice to be able to limit the form picker list to the start node(s) of the current user.
Hi Tom,
if you download the latest version of the package this can be done.
Cheerio, Jeffrey
Hi Jeffrey,
Just looking at it in v1.7, but cannot seem to find an option for this? Nor can I see anything that has changed in the code to add it in?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.