Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element Index Column configuration gets unwieldy with fields outside the global namespace #4314

Open
BenParizek opened this issue May 25, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@BenParizek
Copy link
Contributor

commented May 25, 2019

The following issue describes a UI issue we run into with Sprout Forms. The issue may exist in other similar scenarios.

Form Element Index Customization

Sprout Forms has a Custom Element where users can add custom fields. Those fields are stored outside the global context like matrix blocks:

Element Field Context Edit Visibility
Entry global Via the Craft Fields tab
Matrix Block matrixBlockType:1 Via a specific Matrix Field settings
Form sproutForms:1 Via a specific Form Field Layout

When viewing the Element Index view for the Form Entries, a user can customize what columns appear, however, as seen in the screenshot above, that view shows ALL fields regardless of what Form Source is being shown.

In many cases Forms are used by marketing departments for short-term campaigns, leading to a lot of similar fields being created. One solution could be to create all these fields in the Global context but that also can lead to an intimidating number of not-so-relevant fields to choose from when working within Craft on any other field layout.

It seems this use case falls between the Entry and Matrix Block use cases in that the fields are outside of the global scope and they are also visible to the Element Index page.

@BenParizek

This comment has been minimized.

Copy link
Contributor Author

commented May 25, 2019

This may relate to, or be more relevant to, Craft Elements if Field Instances are added:
#2403

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.