Closed Bellfalasch closed 2 years ago
Could it be solved by a new type of Node Search report format?
For example "a CSV file" and being able to specify the fields that should be included in this report. For example in your case: _path
Example of CSV file that would be generated:
path
/content/superhero
/content/superhero/search
Will be available in DT 5.0.21
OMG ... I'm just speechless
We rely a lot on search function of this app to find parts that are used in a specific way, before making breaking changes. Example: "Part A allows empty field 1, we will now begin enforcing field 1, wish pages does editors need to go to to fix this?", or "Part B had option for illustration, this will now be replaced with option for photo instead".
The search-function gives us all pages, but communicating a list of simple URLs, like pasted bellow, is very cumbersome. Usually editors will work in teams of 3-5 people on a task when we decide to do breaking data changes like this.
A button that opens a modal with a list of all URLs in the result would get us far, or other similar solution. This type of ist is easy to communicate to a bigger editorial team and get them started on the job manually fixing all those pages and parts.