Add ability to set the minimum height of the field

[engram-design]

The minimum height is fixed for Vizy fields, it'd be good to be able to configure that in the field settings.

[MattAppleton]

Very big props for this request, please have a look at this Verbb :)

You can see here, we are making an inline video component — here's what it looks like with Redactor...

And here with Vizy — unnecessarily huge!

We'd stick with Redactor but there's an issue with any sort of html view edits, it trashes the Redactor html tags and puts them into plain text.

And advice / tweak ideas much appreciated!

[engram-design]

Added for the next release. To get this early, change your verbb/vizy requirement in composer.json to:

"require": {
  "verbb/vizy": "dev-craft-4 as 2.0.10",
  "...": "..."
}

Then run composer update.

[MattAppleton]

Thanks @engram-design — not sure Im doing this right, I have updated composer, cleared caches etc, but I'm still seeing large text fields, do I need to set a custom config file to reduce the number of lines visible? If so, not sure what the .json values might be...?

See here, Id like a single-line simple view for this kind of caption ideally... even better the Vizy fields could be set to 'collapsed' if we wanted :)

thanks...

[MattAppleton]

[engram-design]

There is a new setting ("Initial Rows") for controlling the number of lines a Vizy field shows by default in the field settings. Its default hasn't changed, so you'll need to update the field settings.

[MattAppleton]

Thanks @engram-design — hmmm... I don't see that yet — and this is what I have in composer's requirements "verbb/vizy": "dev-craft-4 as 2.0.10",

I think you are saying we should see something here, right?

[engram-design]

Should certainly be there, just below the "Block Configuration" settings.

[engram-design]

@MattAppleton My apologies! I completely forgot to notice I hadn't pushed those changes yet (I was working offline over the break), so that should be there now.

[MattAppleton]

Ah! thought I was going nuts :). Trying again now...

[MattAppleton]

Just confirming — thats working nicely so far :)

[engram-design]

Fixed in 2.0.11