Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: How to view DIFF for grids?

Status	Resolved
Add-on / Version	Publisher 2.6.4
Severity
EE Version	3.5.11

Eric Harth

Oct 05, 2017

Hello mate, I wonder if i’m overlooking something obvious here.

Description:
I noticed that in Version 1.6.6 you Fixed a ticket, “Diffs were not working with Matrix, Grid, Relationship, and Playa fields.”.
Unfortunately even in version 2.6.4 I couldn’t see DIFF working for grid fields, while it DID work for simpler fields like (textarea, text input).

Detailed steps to reproduce the issue:
1. As an editor, make a change in values of one of grid fields.
2. As a publisher view the draft for the requested entry
3. The DIFF is NOT shown for grid type fields

BoldMinded (Brian)

You need to define what template code to use for fields like grid: http://docs.boldminded.com/publisher/diffs

Eric Harth

Thanks for pointing me into the right direction. I gave it a go .. the DIFF is shown below the entire grid and not along each row/col. Can you please guide how can I configure the DIFFs to show along the change element as all the changes clumped together at the bottom of the entire grid aren’t really useful?

An example of my snippet is:

{my_carousel}
    <div>{my_carousel:main_image}</div>
{/my_carousel}

BoldMinded (Brian)

I’m not sure what you mean. Can you share a screenshot?

Eric Harth

Sure, here’s a screenshot of what it currently is (left) and how i was expecting it to be (right). https://image.ibb.co/kND5Jw/grid_diff.png

BoldMinded (Brian)

I figured that is what you were inquiring about, but it would be ridiculously difficult to do that. It’s only meant to show the diff below the field to simulate what he overall difference is.

BoldMinded (Brian)

Going to close this ticket b/c there are no changes to make. The current functionality is working as intended.