Report Page for places where fences is used

Created on 18 December 2020, over 4 years ago
Updated 14 April 2025, 14 days ago

Problem/Motivation

I'm having problems with a site and want to see if fences is the culprit. I need to see about uninstalling it to test the theory.

There's no way to know "where" fences has overridden a field which makes it near impossible to yank fences out of an environment without digging directly in the DB or looking at each and every single field instance.

Steps to reproduce

n/a

Proposed resolution

Add a page to the reports section that outlines which fields/views has been overridden with fences.

A quick screenshot would allow someone to remove fences if they need to and rebuild it quickly or to maybe transfer the settings to another site if they wanted to replicate the output somewhere else.

Remaining tasks

n/a

User interface changes

Add page to admin/reports/fences-list

API changes

n/a

Data model changes

n/a

✨ Feature request
Status

Active

Version

2.0

Component

Code (fences)

Created by

πŸ‡ΊπŸ‡ΈUnited States philsward

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States mortona2k Seattle

    Maybe the Paragraphs Report β†’ module has some inspiration.

    I think this will be easier, since fences aren't content they aren't hidden in the database. We should be able to export site config and grep for uses of fences if needed. A UI for this would be nice.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Thought about this again and while the idea behind is still great, I think this doesn't belong into this module, but into a much more generic field reports module (e.g. https://www.drupal.org/project/issues/field_tools β†’ ) or core. The report should show the used field formatters grouped per entity display. Same should exist for widgets then.

    So while I totally like and support the idea behind, it should not be implemented in fences and I'm just keeping this open to save the idea, but see this as WON'T FIX HERE.

Production build 0.71.5 2024