grid reorder clashes with previous fields

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Karl Tynan 16 posts 153 karma points MVP 5x c-trib

Aug 05, 2016 @ 08:39
1

Grid reorder clashes with previous fields
If you use the Grid in your doctype for Nested Content, the "Reorder" action for the Grid can break into previous fields (not sure if that is a Grid bug or Nested Content bug).

However, I found that it could be fixed with the following CSS:
```
.nested-content__item .umb-grid .umb-editor-sub-header 
{
  background: none;
  margin: 0 0 -20px 0;
  padding: 0;
}
```
I have:
1. set the background to none, as the default is white m which looked ugly against the grey
2. removed the top/bottom margin, adding negative margin to bring the "Reorder" closer to the Grid
3. removed the padding as this is no longer needed without the white background colour
Don't know if this is useful for anyone else?
Copy Link
Lee Kelleher 4026 posts 15836 karma points MVP 13x admin c-trib

Aug 18, 2016 @ 11:02

1

Hi Karl,

Thanks for posting a fix for this. I haven't experienced this myself, but it's good to know.

I'm not sure which side of the fence this issue lies on, but if it is a Nested Content concern, feel free to send a pull-request with this fix.

Cheers,
- Lee

Copy Link
Karl Tynan 16 posts 153 karma points MVP 5x c-trib

Sep 05, 2016 @ 13:14

0

Hi Lee,

I am not sure where the issue belongs either...

The problem is actually with the "Reorder" text of the Grid, rather than Nested Content, but is only apparent with Nested Content (haven't seen this issue with other packages yet).

Maybe I will try it with some other similar packages (Archetype etc) and see if there is reason to pull-request to Core a more generic fix. Otherwise I will look into a pull-request for Nested Content!

:)

Copy Link
is working on a reply...

Please Sign in or register to post replies

Flag this post as spam?