🇫🇷France @Grimreaper

Hi,

Thanks both of you for your replies.

Then in case I will adapt my code to only manipulate the body.

grimreaper → created an issue.

Thanks a lot for the followup.

I put one review comment.

Hi,

Changing of project as this is not UI Suite Bootstrap related.

Currently, you can define a block content type with an image field or a media field and then use it. But that's not necessarily the best way. Or use the "data from a field".

It depends on your site structure. And not sure that it is the best experience for editors to access component directly. I think it is better to prepare block types (that will use the components with fields) and so the editors only can place blocks.

grimreaper → created an issue.

grimreaper → created an issue.

grimreaper → created an issue.

Test https://www.drupal.org/project/entity_reference_display →

grimreaper → created an issue.

Also need to be able to handle background image on block contents by adding a media field on the block type and so view displays could use it with tokens.

TODO:
- refactor display processing
- Form to control which media bundle is available and with which field.
- UI Patterns attributes plugin source

Between:
- https://www.drupal.org/project/search_api_exclude →
- https://www.drupal.org/project/search_api_exclude_entity →

Selecting https://www.drupal.org/project/search_api_exclude_entity → because not related to node and much more flexible.

grimreaper → made their first commit to this issue’s fork.

MR rebased.

Here is a new patch from MR to add for projects.

Marking as postponed until ✨ Allow changing the layout of an existing section in Layout Builder UI Needs work is fixed.

grimreaper → created an issue.

grimreaper → created an issue.

Also remove array_pop and array_push regarding 🐛 Do not use array_pop or array_push Needs review

Ok, the problem is that "layout-builder__section" key does not have a weight. So if putting weight on links it appears after the section.

✨ Allow changing the layout of an existing section in Layout Builder UI Needs work is also proposing to put links into a dedicated container so that no side effect on other stuff.

I would prefer to not act on the links so themers can alter LB element to do their own reordering. Especially if a lot of other patches on core and other contrib modules are present.

This is very side effect prone.

Hello,

I will reupdate this MR after finishing some cleanup on the 1.0.x branch and then creating and targeting a 2.0.x branch.

grimreaper → created an issue.

Hello,

As currently the reorder links are wrapped into a container:

$sections[$key]['rearrange'] = [
            '#type' => 'container',
          ];

The hook has currently no impact so it can be removed.

I think to open another branch to get rid of this container wrapper.

If the reorder links needs to appear last (which I agree is better), then setting a weight on it will do it properly.

grimreaper → created an issue.

The Section Library module JS is sensitive to the DOM structure and expected a list with ul > li > a.

waiting for a new USB release.

grimreaper → made their first commit to this issue’s fork.

Thanks.

It is merged :)

Thanks a lot @avpaderno!

Change reverted and marking as postponed until Core issue is resolved.

grimreaper → created an issue.

It breaks the contextual links in admin theme.

Hello,

Thank you, it fixed the fatal error for me!

grimreaper → created an issue.

Currently the only case I see is for attributes props.

So a new source for attributes which would allow to instanciate as many other attributes sources as desired.

As there is no external dependency, I think it can be provided by UI Patterns directly.

I created another MR to have ✨ Support for color widget Active and ✨ Prop source to get background URL Active appliable as patch.

I forgot transform relative when using an image stye.

Good catch.

Hello,

Thanks @avpaderno.

As per your previous comment, here is the comment after 14 days, to remind that I am still interested and I have not received any news from the maintainer.

Thanks for the merge :)

grimreaper → created an issue.

I propose to handle everything in ✨ Support for color widget Active .

I have added a note on the project page.

Hello,

I think this is due to the dependency on ui_icons.

Which is now in beta, so minimum stability beta should be ok.

Could you please retry with minimum stability beta?

A wrapper is removed by a module on my test environment.

grimreaper → created an issue.

Uploading patch for Composer usage.

grimreaper → made their first commit to this issue’s fork.