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

Ignores Vizy fields #104

Open
TK1288 opened this issue Oct 21, 2024 · 2 comments
Open

Ignores Vizy fields #104

TK1288 opened this issue Oct 21, 2024 · 2 comments

Comments

@TK1288
Copy link

TK1288 commented Oct 21, 2024

Describe the bug

I am using some fields inside Vizy field. The plugin doesnt provide any information in Audit tab

Steps to reproduce

  1. Create any field
  2. use it inside Vizy builder
  3. check Audit tab of "Field Manager" plugin
  4. field is not there

Craft CMS version

4.12.7

Plugin version

3.0.9

Multi-site?

No

Additional context

I have also Vizy plugin installed, version: 2.1.23

@engram-design
Copy link
Member

This would be true of any nested field, like Neo, Hyper or Vizy. We don't dive into each "block" of these sorts of fields, and just go with the top-level fields. We don't need to do this for Super Table and Matrix in Craft 4, as these fields aren't global, but in Craft 5, they are.

I'll have to look at what's involved in including those inner fields.

The Audit tab has been largely superseded in Craft 5, due to fields now containing a column with the number of layouts it's used it as well.

@TK1288
Copy link
Author

TK1288 commented Oct 24, 2024

We use some nested fields in our projects. Field manager plugin is super useful to have an overview what is used where (at least for me). Having this information available for vizy, neo and other fields - would be really good.
Without it, I still need to go and check each of those fields manually, to know where is which field used right now :(
Thank you in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants