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: Wyvern fields oddly huge in Matrix
| Status | Resolved |
| Add-on / Version | |
| Severity | Trivial |
| EE Version | 24 |
Shark Attack
Apr 05, 2013Hi, I have a Wyvern field applied as a Matrix column. In the publishing page the field size seems to be oddly large regardless of what size setting is applied in the channel field definition. I’ve attached an image of that part of the publishing page when the Wyvern display height is set to 10 px; however, the publishing page also looks like that when the display height is set to 50, 100, 200, or 400px—or anything else.
Earlier I did experience a situation where setting the display height to very small amounts (eg. 10px) would cause the field in the publishing page to display without the Wyvern toolbar and with any text in the field showing as source code, but I’ve been unable to reproduce that now. Odd in itself, I guess. Also, the ‘resizeable’ checkbox seems not to be ‘uncheckable’—I can uncheck it and submit the field changes, but the next time I edit that field it is rechecked.
I’d be grateful if you could take a look as it makes the interface for the client look rather weird and off-putting. I’m not seeing any javascript issues (although I find Safari’s recent Inspector updates a bit cryptic, so I might just be looking in the wrong place).
I’ve put a duplicate of the site onto my own hosting, details below.
Thanks.
Rick Lecoat
BoldMinded (Brian)
Have you inspected the styles of the editor field? I’ve never seen this happen, just wonder if there is another add-on or style declaration somewhere that could cause this.
Shark Attack
I’m checking it now, from the matrix row inward. The text area (class=”wyvern”) has an inline style height of 10px, in accordance with the (admittedly rather extreme) channel field setting. No other height rule shows up for it in the inspector.
Its sibling div (id=”cke_field_id_35_row_id_21_col_id_21_33781983”) has a height: auto applied by .cke_reset.
The parent td of these two shows no height rules.
The grandparent (tr. matrix.even) shows no height rules either.
There are so many nested elements in the generated markup that it’s impossible to relate it all here. Short version: I’m not seeing anything that I would expect to cause this. There is a height: 100% rule on the iframe which, if I disable it, stops the wyvern box overflowing the bottom of the matrix row. But it’s still 150px or more tall. There are lots of height: auto rules in the Wyvern/CKE code and some height 100% ones, but AFAICT it’s the Wyvern field that is pushing the matrix row to the height that it is. But I can’t see why or where.
You have CP access, so maybe your more practiced eye can spot the issue? In the meantime I’ve set the channel field to a more reasonable 90px height, to eliminate at least one unnecessary element of oddness.
Shark Attack
Update: when viewed in Chrome (Mac) rather than Safari (Mac) the vertical breaking out of the Matrix row height does not occur. However, the fields are still not respecting the height set in the Channel Field definition and seem to be taking the default 200px height (+ 25px for the horizontal DOM tree panel at the bottom).
Hope this helps.
BoldMinded (Brian)
Would you be able to backup your database and start uninstalling other addons until you get down to nothing but Wyvern? I’m using it on a site now and I don’t see this happening in chrome or safari. I feel like this has to be an addon conflict.
Shark Attack
Sorry for the delay in responding, I wasn’t in a position to do any testing for most of last week. Anyway, one by one I’ve uninstalled every third party add-on – modules, accessories, extensions, field types and plugins – and the problem persists. The only third party add ons in the mix are Wyvern and Matrix. (I don’t see any point in uninstalling Matrix since the only place I’ve noticed the odd behaviour is when I have a Wyvern field type inside a Matrix field). I even reinstalled the native Text Area (rich text) field type, which I had previously uninstalled, in case Wyvern was expecting to have it available, but it made no difference.
So I’m a bit stuck. Any more ideas?
BoldMinded (Brian)
I’ll have to login to the cp and take a look later today.
Shark Attack
Okay, thanks. However, for various reasons I’m letting the client use the CP that I provided previously as a testbed/sandbox, so maybe I should set up a duplicate for your testing purposes (to avoid conflicts). It will also mean that I can set it up in its more stripped-back form for you. Shall I just email the details to you at your support email address when I’ve got it done (later today I expect)?
Shark Attack
I just sent updated CP login info to you via email.
Shark Attack
Update: solution found. Brian emailed me the following:
… Ok, In the themes folder look for the matrix2.js file. And on line 19 you should see this: config.height = ‘100%’; comment that out, then it should work. …
I can confirm that this fixes the problem for me, so if anyone else is reading this thread with similar issues, try the above fix. Also, in case Brian folds this change into later versions of Wyvern, I should add that this issue was occurring under Wyvern version 1.5.6.
(Whether it gets folded into later builds or not I guess depends upon whether mine is an isolated case or whether this is an issue that would affect anybody combining Matrix and Wyvern).
Anyway, it’s fixed. Thanks Brian.