johntarling → changed the visibility of the branch 3508661-ajax-error-when to hidden.
Created a quick fix for this by just checking that the entity is available before fetching the UUID.
johntarling → changed the visibility of the branch 2.2.x to active.
johntarling → changed the visibility of the branch 3508661-ajax-error-when to active.
johntarling → changed the visibility of the branch 2.2.x to hidden.
johntarling → changed the visibility of the branch 3508661-ajax-error-when to hidden.
johntarling → created an issue.
The referenced bug to do with the mercury editor context issue has resolved this problem, marking this as fixed.
@pixelwhip Thanks for the speedy fix! Tested and section titles are editable again. Marking as reviewed and tested.
This works well, marking as reviewed and tested.
@pixelwhip Thanks for this! The cursor positioning works pretty well but occasionally it is slightly offset which i think is either the padding applied from the mercury editor to the area when editing or perhaps the ckeditor toolbar initialising and taking up some space.
This is a big improvement overall though, marking as reviewed and tested.
johntarling → created an issue.
Just applied this patch to test and I get an immediate error when entering edit mode on a node now.
I can confirm that I get the same behaviour using the 2.x branch too.
johntarling → created an issue.
I think the fix for this is to add overflow-x: hidden; to the style constructed for the main tag inside the mercury-dialog web component. That seems to keep the right pane resizable and removes the scrolling when Gin is used and doesnt impact the Claro theme usage.
johntarling → created an issue.
johntarling → created an issue.
Hit this issue too when creating a tabbed content component in D10.2 with Layout paragraphs 2.04.
johntarling → created an issue.
johntarling → created an issue.
That setting lets you override the groupings in the "Choose a component" form and accepts a YAML string. An example would be as follows.
layout:
label: Layout
components: ['section']
content:
default: true
label: Content
components: ['text', 'heading', 'hr', 'quote', 'accordion', 'table', 'date_location']
media:
label: Media
components: ['image', 'image__image_download', 'image__image_link', 'gallery', 'video', 'logo_list']
call_to_action:
label: Calls to Action
components: ['cta', 'cta__image', 'cta__image_simple']
emebs:
label: Embeds
components: ['iframe', 'person', 'view']
@justin2pin Tested this on mercury templates and confirmed that the front end mercury editor can now be used once selected against the entity in the mercury config. The update db routine also correctly fixed up existing templates.
We ran into this issue too. I've created an issue fork with the fixup. It also sorts out some of the permission references where incorrect casing was used.
johntarling → made their first commit to this issue’s fork.