🇧🇪Belgium @yazzbe

> I think the behavior should be configurable. Maybe a $setting to define additional characters?

That is a great idea!

Just like in the block_class module where it is also configurable to allow special characters in classes.

yazzbe → created an issue.

yazzbe → created an issue.

yazzbe → created an issue.

Thanks for your work on this.

The patch from #90 applied smoothly using the patch command (not git). Tested on Drupal 10.2.26 + VDE 8.x-1.4.

Hoping this merge request gets approved quickly.

I manually applied the change to version 1.3, and that completely resolved the issue for us.

Thank you very, very much for investigating this. I greatly appreciate your efforts in resolving it. It might have been a bit of an edge case. But the mystery of the 2 unknown lines of code is now solved :-)

Thanks!

Patch #10 also worked form me on D10.2.0.4 (PHP 8.1.27) and redis 1.7
applied manually

Much appreciated for looking into this.

Yes, the database is MySQL 5.7.44.
Sorry for not mentioning that.

Similar to the issue detailed here:
https://www.drupal.org/project/facets/issues/3422150 💬 "Database exception" when using fulltext search with facet with AND operator Active

The SQL error in Search API occurs on views with both:

- A "full text search field" (e.g. on the title field)
- Facets linked to that view which have an AND operator (not OR)

Switching the facet operator to OR eliminates the SQL error when using the full text search on title field.

Similar to the issue detailed here:
https://www.drupal.org/project/facets/issues/3422150 💬 "Database exception" when using fulltext search with facet with AND operator Active

The SQL error in Search API occurs on views with both:

- A "full text search field" (e.g. on the title field)
- Facets linked to that view which have an AND operator (not OR)

Switching the facet operator to OR eliminates the SQL error when using the full text search on title field.

Yazzbe → created an issue.

I got the same issue when upgrading to Search API 1.31. reverting back to 1.30 seems to fix that problem.
So I think this is more related tot Search API.

Since this is a breaking bug, can I bump this issue to major?

Can the fix be implemented in a stable D10 release?

Many thanks

Ran into the same issue updating from 10.1.7 to 10.2.2.

I had previously uninstalled the Webform module, too. And "webform_default" was also still in my configuration.

#9 saved my day. Many thanks!

Yazzbe → created an issue.

Encountered a similar issue.

The Navbar (top region) vanished after a cache rebuild on the homepage, reappeared on basic pages, but disappeared again on views pages. The Navbar's behavior was inconsistent.

I manually applied patch #4 on Uikit 3.16 in Drupal 9.5.11, which resolved the issue.

NB: Could this fix be included in a new release, as it addresses a critical/breaking website problem?

artmania → created an issue.

artmania → created an issue.

To get styles on a section, I’ve currently managed to work out a solution based on the module “Layout builder Styles”. This way, it is possible for me to add new or custom classes to sections and blocks in the Drupal UI. Maybe that could be a base for this module too.

The options I've setup are similar, but slightly different still:

1 column
2 columns (50/50 - 33/67 - 67/33 - 25/75 - 75/25)
3 columns (25/50/25 - 33/34/33 - 25/25/50 - 50/25/25)
4 columns

Section type
- transparent
- white
- muted
- primary
- secondary

Padding (top/bottom)
- small
- large
- xsmall (custom class)
- xlarge (custom class)
- remove padding

Container width
- default
- small
- large
- xsmall
- xlarge
- expand
- edge to edge (100%)

Grid
- collapse
- small
- medium
- large
- divider

Margin (multiselect)
- small top
- small bottom
- xsmall top
- xsmall bottom
- medium top
- medium bottom
- large top
- large bottom
- xlarge top
- xlarge bottom

Extra (multiselect)
- preserve color
- grid reverse (@mobile)

The last 2 select lists are multiselect, with the “chosen” module for better UX.

The "preserve color" and "grid reverse (on mobile)" are 2 features I definitely recommend. Also, the "edge to edge" container and "multiselect" for margin settings and extra's.

I’ve added 2 custom classes to the padding select box (xsmall & xlarge), those do actually not exist in the UiKit framework (unfortunately) but I use them a lot myself.

NB: I’ve moved the background image and overlay to my custom block settings. That gives me extra possibilities (e.g., background slideshow, custom overlays) and fewer conflicts in the drupal layout builder administration (z-index).

I don't know if a generic module is possible because I allready use some custom classes. What do you think?

Unfortunately, I lack the necessary developer skills to successfully maintain the module.

Yes it works now.
Many thanks for your prompt action.

artmania → created an issue. See original summary → .

Fantastic! 🙏

Applied the patch and it all works fine.

Do you plan to make a D10 release any time soon?

Love the module, which takes a framework agnostic approach (I use it with Uikit3).

Cheers

It also works in views.

But I had to enable the views option "enable field template" under the styling tab.

see attach (NL).

Cheers

Hi Mitsuko,

I have applied patch #5 and manually updated the .info.yml file. Everything appears to be working as intended.

Is there a D10 release planned for this module any time soon?

Many thanks for your excellent Uikit support!

Cheers

I've added an overlay option fro testing. see attachement.

Also conditionally added "uk-position-relative uk-position-z-index" to the container element, only in case an overlay is applied to the background image.

is that something you would consider also for this module?

artmania → created an issue.