Expresso
ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5
Back to this add-on's main page
View Other Add-ons From PutYourLightsOn
‘Make Editor Full Width’ option - breaking when used in Grid field
Support (Resolved)
xynergy_inc
|
Posted: 05 July 2017 11:32 AM |
|
|
|
Now that EE3 supports configurable widths in the Grid fields, the setting to ‘Make Editor Full Width’ has styling that is causing issues when Expresso is used in a Grid. Devotee won’t let me attache a screenshot, but try including Expresso in a Grid that has 4 columns each set to 25% width and the ‘Full Width’ setting is checked for Expresso.
Is there a way that the ‘Full Width’ option for Expresso can only apply to standalone Expresso fields? Or stay ‘full width’ within whatever size has been defined for the Grid/Matrix column?
Thanks,
Justin
|
|
|
PutYourLightsOn
|
Posted: 06 July 2017 05:17 AM |
# 1
|
|
Developer
|
Hi Justin, we’ll need to look into this and see if we can post a fix. Thanks for letting us know and we will follow up with you soon.
|
|
|
xynergy_inc
|
Posted: 06 July 2017 10:59 AM |
# 2
|
|
|
Thanks for the reply. FYI I found a fix using Digi Nut Control Panel CSS & JS - it’s not pretty (I hate using !important in CSS), but it works:
.grid-input-form td[data-fieldtype=“expresso”] { width: inherit !important; }
|
|
|
PutYourLightsOn
|
Posted: 06 July 2017 11:12 AM |
# 3
|
|
Developer
|
Ok, we’ll integrate this into Expresso for the next release. Thanks for the code snippet!
|
|
|
mediapimp
|
Posted: 30 August 2017 09:59 AM |
# 4
|
|
|
I am having this same issue.
Can you explain where to apply this css: .grid-input-form td[data-fieldtype=“expresso”] { width: inherit !important; } ?
Thanks!
|
|
|
mediapimp
|
Posted: 30 August 2017 10:04 AM |
# 5
|
|
|
Actually, I figured it out, but adding that css does not work for me.
style=“width: 100%”; still gets applied to my expresso fields that are inside grid fields.
|
|
|
mediapimp
|
Posted: 30 August 2017 10:47 AM |
# 6
|
|
|
Got it working. Thanks for the tip!
Would be great to have this fixed soon as to not have to rely on another plugin for the fix.
Thanks!
|
|
|
PutYourLightsOn
|
Posted: 30 August 2017 03:09 PM |
# 7
|
|
Developer
|
Yes the next release will include the fix and will likely be pushed out next week.
|
|
|
PutYourLightsOn
|
Posted: 04 September 2017 12:05 PM |
# 8
|
|
Developer
|
This has been fixed in version 4.2.5.
|
|
|