Christoph Posted February 6, 2017 Share Posted February 6, 2017 Quote We currently encounter problems with frontend editing of repeater fields, too: in our case it's simply not possible to frontend-edit repeater fields for users with a specific role, although these users are able to edit the respective repeater fields in the regular backend page editor. Superusers are able to frontend-edit repeater fields as expected. This is what @design-a-point wrote in a different thread. I experience the same issue, but couldn't find a solution, yet. Any role other than superuser isn't able to front end edit a field. Any ideas? Thanks for your help! Link to comment Share on other sites More sharing options...
kongondo Posted February 6, 2017 Share Posted February 6, 2017 (edited) So why start a new thread about the same thing ? I'm merging the threads unless I'm missing something?. Edited February 6, 2017 by kongondo Link to comment Share on other sites More sharing options...
Christoph Posted February 6, 2017 Author Share Posted February 6, 2017 The thread had a different topic and was marked as solved, that's why I started a new one Link to comment Share on other sites More sharing options...
kongondo Posted February 6, 2017 Share Posted February 6, 2017 OK. To help other members help you, please: Describe your situation better. Saying you 'experienced the same issue but the other thread had a different topic' is hardly enough to go by. E.g. PW versions, what role(s), etc? Link to the 'other' thread. I had to Google to find it . This is the other thread. Show us some code. What have you attempted so far? Thanks. Link to comment Share on other sites More sharing options...
Christoph Posted February 8, 2017 Author Share Posted February 8, 2017 Ok, sorry for any inconvenience! While trying to better explain my problem I came up with a solution. Because the issues described in the post mentioned above are related, as I discovered, I wrote my solution over there: So, this thread is obsolete. 1 Link to comment Share on other sites More sharing options...
kongondo Posted February 8, 2017 Share Posted February 8, 2017 Hey @Christoph. There was no inconvenience and no need to apologise . It's just that a properly formulated question not only helps those who can potentially come up with a solution, but also those who might have a similar problem in the future will be able to easily relate. Glad you got it working and thanks for sharing your solution! 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now