Search the Community
Showing results for tags 'FieldsetTabOpen'.
Found 3 results
-
Hi everyone! Perhaps I'm a bit enthusiastic in using the Repeater-field & FieldsetOpen combo, as I've already posted another question about it today... But here goes nothing I've got a FieldsetTabOpen which I'm using in a Repeater-field, but that's not working as expected; as in – no tabs showing Instead it just shows the two grouped in FieldsetTabOpen below each other...would be great to see tabs in the repeater as well. To add some visuals in; In the attached images the fluor-green box is my repeater, with two checkbox fields, and after that the two FieldsetOpenTab groups. The other two are how I set up the fields in the repeater (Reno AdminTheme) and the current view in the CMS. Any tips/recommendations as to how I could go about setting this up? I've tested the FieldsetOpenTab elsewhere, it works perfectly – but then again, here I'm trying to use it in a Repeater instead of directly in a template....would I need to place the two tabs in a fieldset? Or some other ingenious construction-ideas that could help out here? Hope someone has an idea as to how to do this! Thanks!
-
Hi all, I added a field FieldsetTabOpen in the user template (with FieldsetEnd as well). Everything works perfectly if the user is super-user: the tab to edit fields within FieldsetTabOpen show up. However, when I logged in as other role, this tab does not show at all. I've tried manual access control in field settings but it doesn't work. Does anyone have this issue?
-
I’m working on my first ProcessWire project and so far I’m really glad that I found this CMS But I discovered that nesting a Fieldset into a FieldsetTab doesn’t work. I tested it with and without the custom admin theme – with the same result. That’s how part of the fields I use in the template look like: There’s a new tab “seo_tab” which contains the fieldset “seo_serp” and a few fields before and after this fieldset. But the result doesn’t look like intended: The fieldset “seo_serp” doesn’t end where it should end. Instead it also covers all the following fields. Any mistake I made? Or is this a bug?
