Minimal Fieldset

[Robin S]

Minimal Fieldset

Adds a config option to Fieldset/FieldsetGroup/FieldsetPage to render the fieldset without label or padding in Page Edit. When a neighbouring field in the same row is taller than the fieldset the extra height is distributed evenly among rows within the fieldset.

Requires ProcessWire v3 and AdminThemeUikit.

Why?

This module allows you to create layouts in Page Edit that would not be possible without it. It's useful when you want a layout that has two or more fields as rows that are themselves within a row in Page Edit.

It's also useful when you have some fields that you want to add to a template as a group (i.e. via FieldsetGroup or FieldsetPage) but having a heading and visible wrapper for the fieldset in Page Edit would be redundant.

Example:

Installation

Install the Minimal Fieldset module.

Usage

In the field settings for any Fieldset/FieldsetGroup/FieldsetPage, tick the "Remove label and padding for this fieldset" checkbox.

 

https://github.com/Toutouwai/MinimalFieldset
https://modules.processwire.com/modules/minimal-fieldset/

[horst]

very nice! ?

[Klenkes]

This is really great. In order to make editing easy for users I spend a lot of time grouping and arranging fields in the backend. I definitely will use it!

[arjen]

Thanks! Really nice.

[Klenkes]

11 hours ago, Robin S said:

Requires ProcessWire v3 and AdminThemeUikit.

I was happy too early... AdminThemeUikit required. I am still a Renoman...

[dotnetic]

12 hours ago, Klenkes said:

I am still a Renoman

Upgrade then ?

[d'Hinnisdaël]

Wonderful! Well done and thank you for taking the time and releasing this. I've been thinking about the exact same thing for a while now.

Could you make the vertical spacing optional, via another checkbox maybe? I have quite a few layouts where the secondary column has a lot fewer inputs and would prefer to have them on top.

[Robin S]

2 hours ago, d'Hinnisdaël said:

Well done and thank you for taking the time and releasing this.

Glad you like it. ?

2 hours ago, d'Hinnisdaël said:

Could you make the vertical spacing optional, via another checkbox maybe?

Done, in v0.1.1.

[matjazp]

Thanks for the module. Maybe this could be in the core... Any chance of supporting AdminThemeDefault? If not, then you could possibly check if the user has Uikit theme active before injecting css file and applying classes?

[Robin S]

34 minutes ago, matjazp said:

Any chance of supporting AdminThemeDefault?

No, AdminThemeDefault and AdminThemeReno do some crazy JS spacer stuff to equalise field heights. This module relies on the flex layout used in AdminThemeUikit.

 

34 minutes ago, matjazp said:

If not, then you could possibly check if the user has Uikit theme active before injecting css file and applying classes?

Possibly, but not sure what the point of that would be. The module already requires AdminThemeUikit in order to be installed and also clearly states that in the readme. And if you have AdminThemeUikit installed but you allow some users to choose a different theme then using this module is not going to be a good idea. Best just not to install it in that case.

[Robin S]

In v0.1.2 I've added some warning notices in case AdminThemeUikit is installed but not in use.

[d'Hinnisdaël]

Field exports don't seem to work properly with the module enabled. When exporting a Fieldset (via Setup » Fields » Export), I get the following error: Call to a member function add() on null (MinimalFieldset.module, line 74). $wrapper seems to be unset in this specific context.

Uninstalling the module gets rid of the exception. Could you check if you see the same thing (I'm on 3.0.117) or if I just have something misconfigured?

[Robin S]

@d'Hinnisdaël, thanks for the report. FieldsetClose needed to be excluded - fixed in v0.1.3.

[eelkenet]

I installed the module (v0.1.3) on an existing site, running PW in the current Master release, v3.0.98 on Php 7.2.
After enabling the module for a regular Fieldset (Open) I kept running into this error:

Method InputfieldFieldsetOpen::wrapClass does not exist or is not callable in this context

This is because Inputfield::wrapClass() has not been added to the Master yet, it is only available on the ProcessWire dev release (currently 3.0.119).

The fix for this issue is to replace lines 107-109 with:

// Add classes to inputfield
$inputfield->wrapClass .= ' MinimalFieldset';
if(!$field->no_spacing) $inputfield->wrapClass .= ' MinimalFieldsetSpaced';

 

[Robin S]

Thanks @eelkenet, fixed in v0.1.4.

[cjx2240]

I just want to say I love this module. It means I can have repeatermatrices made up of fieldsets, while also using those fieldsets on their own elsewhere, with much less clutter. Thanks for making it!

Would it not make more sense though for the provided option to be added to Input > Admin theme settings (Uikit) ? Then also it could be overriden from within a template/repeater field group. I think this would be really helpful because while you're likely to not want the title/padding when loading a fieldset within a repeater matrix, you're likely to want it when loading a fieldset in a more standard context.

[Robin S]

12 hours ago, cjx2240 said:

I just want to say I love this module.

Thanks, I'm glad you like it. ?

12 hours ago, cjx2240 said:

Would it not make more sense though for the provided option to be added to Input > Admin theme settings (Uikit) ? Then also it could be overriden from within a template/repeater field group.

The "Admin theme settings (Uikit)" options don't exist for the standard Fieldset fieldtype (FieldsetOpen) so that wouldn't work, and in any case the location of the module settings fields doesn't determine whether or not they can appear in template context.

But in the newly released v0.1.6 I have added support for defining the Minimal Fieldset settings in template context so this should cover what you're wanting to do.

[cst989]

Just fyi this breaks a bit if you put a description for the fieldset and also tick the box. Maybe just in the latest version of PW

[Robin S]

12 hours ago, cst989 said:

Just fyi this breaks a bit if you put a description for the fieldset and also tick the box. Maybe just in the latest version of PW

Thanks. I assume you mean if you accidentally add a description because the point of this module is that it hides the fieldset that surrounds the fields so you wouldn't expect to be able to see any description. In v0.1.7 the module explicitly hides any description and notes for the fieldset so if these are accidentally present they won't disrupt the intended layout.

[cst989]

Sorry I should've been clearer, what I was seeing was that the description was still visible, but the padding broke and spacing at the bottom of the fieldset was out of alignment.

The way I'm trying to use minimal fieldset is like this:

For me, a description would still be kinda handy to have - but I appreciate it would need new CSS logic and that's more complicated than it seems. And I understand if this isn't exactly the aim of the module. 0.1.7 certainly fixes the visual hiccup pictured, so thanks for that ?