undefined - Contrib.social

🇦🇹Austria maxilein

This is the message on the /admin/reports/updates page:

Views Summarize 1.1.x-dev (2021-Feb-20)
Project not supported: This project is no longer supported, and is no longer available for download. Uninstalling everything included by this project is strongly recommended!
Includes: Views summarize

And that seems different from the module's homepage. Further I am using it on Drupal 11.2 with no problems at all.

📌 | Node Link Report | Automated Drupal 11 compatibility fixes for node_link_report

🇦🇹Austria maxilein

Can you please make a Drupal 11 version.

🐛 | Drupal core | View deleted without notice on deletion of content type

🇦🇹Austria maxilein

I completely agree with you on this: The Drupal site builder/developer needs to attend to these Views, and fix them, regardless if it's 1 or 100.

But it should always be the developers decision on how to approach that.
If I want to get stuff out of a site immediately (for whatever reason) - it is my decision on how to deal with the fallout.
That's why transparency is key.

And since the current warning already lists impacted nodes it cannot be too difficult to provide some more meta information from inside that same routine.

💬 | Solo | Node edit: how to meta from right to bottom?

🇦🇹Austria maxilein

💬 | Solo | Node edit: how to meta from right to bottom?

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Solo | Primary Sidebar Menu - javascript errors

🇦🇹Austria maxilein

🐛 | Solo | Primary Sidebar Menu - javascript errors

🇦🇹Austria maxilein

Thank you. That fixed it.

🐛 | Drupal core | View deleted without notice on deletion of content type

🇦🇹Austria maxilein

🐛 | Drupal core | View deleted without notice on deletion of content type

🇦🇹Austria maxilein

There are more scenarios we should take into consideration and it should always be the admin's responsibility how he wants to proceed.
Why? Because the approach of blocking the uninstall of a module is doable if you have a few views that you can adapt quickly. But if you have very many views and entity types on a large site the invalidation of them can be the approach with lesser pain and cost.
There are two problems:
Finding out which items are affected.
Fixing them.

Also in a dev environment you sometimes realize too late (once you have built lots of stuff with it) that a certain module is faulty or breaking some other much more important functionality so you have to be able to remove it easily.
Then invalidating items (views, entity fields,..) is the better approach, because it may break the site to some extend, but you can still access the configuration of the views and fix it. Invalidation just breaks parts of the site. While a faulty module that cannot be uninstalled can break everything.
If we offer an approach where the admin or dev can make the judgement regarding the path with the lesser pain - would be best in my opinion.

We need to be better in these things at least:
a) Show a warning: just listing the nodes in the gui before deletion is not good enough. If you have many views (100+) you cannot properly take notes for each of them. So also add one single(!) log message that lists all nodes including links to get there and if possible the particular information of configuration changes that will be made - if the admin procedes. This log message can be used as a task list for fixing things - even if the admin/dev does not procede and cancels deletion.
b) Create a log message the admin/dev can work with. see a) and create a very informative task list. Ideally something where I can derive a judgement of which effects the uninstall will have (e.g. is it just views, is it the display of entities, will widgets go missing, ...). We have all this information in the database, right?
c) let the admin/dev decide if he wants to delete OR invalidate affected entities - depending on his knowledge of the site.

🐛 | Solo | Primary Sidebar Menu - javascript errors

🇦🇹Austria maxilein

I will try this module and see if it can make a difference: https://www.drupal.org/project/modules_weight → and post back soon.

🐛 | Solo | Primary Sidebar Menu - javascript errors

🇦🇹Austria maxilein

solo-utils.js is loaded after the solo-menu.js ...

✨ | Formatted Number Input | Add a status page check for the autonumeric.js library

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Save & Edit | Save_edit not workin in Drupal 11

Comment 22 days ago →

🇦🇹Austria maxilein

Thank you.

🇦🇹Austria maxilein

sorry for bothering you.

🇦🇹Austria maxilein

🇦🇹Austria maxilein

Further testing shows that the Fixed Search Block also works when there is something in the header.

🐛 | Solo | Primary Sidebar Menu - javascript errors

🇦🇹Austria maxilein

Maybe it is important to know that I changed the order of the primary menu above the header.

🇦🇹Austria maxilein

Maybe it is important to know that I changed the order of the primary menu above the header.

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Solo | Primary Sidebar Menu - javascript errors

🇦🇹Austria maxilein

maxilein → created an issue.

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

Thank you I figured. But to make the module consistent with the legal requirements before other people download it seems reasonable.

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

GPL2+ license included in release 2.0.3

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

Then the license is ok now. Thank you for your help.

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

Thank you.

What happens to in line 307? Is it automatically replaced also?

At https://spdx.org/licenses/GPL-2.0-or-later.html it is recommended to add some header:

Formatted Number Input for Drupal
Copyright (C) 2025 maxilein

This program is free software; you can redistribute it and/or modify 
it under the terms of the GNU General Public License as published by 
the Free Software Foundation; either version 2 of the License, or (at
 your option) any later version.

This program is distributed in the hope that it will be useful, but 
WITHOUT ANY WARRANTY; without even the implied warranty of 
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU 
General Public License for more details:

But that is not required, is it? Then I would just delete that header if the rest gets automatically replaced.

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

Thank you. I did that and followed the instructions on https://spdx.org/licenses/GPL-2.0-or-later.html

Please, see here: https://git.drupalcode.org/project/formatted_number_input/-/blob/1.0.x/L...

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

Thank you.
I am very confused about that license and where to obtain the original. https://www.gnu.org/licenses/old-licenses/gpl-2.0.html does not exist any longer.
Should I just copy the license file of Drupal core?

📌 | Formatted Number Input | Fix phpcs code formatting warnings

🇦🇹Austria maxilein

Fixed in 1.0.2

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

📌 | Drupal.org security advisory coverage applications | [1.0.x] formatted_number_input

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Save & Edit | Save_edit not workin in Drupal 11

🇦🇹Austria maxilein

I have created a version that works for me. Here is the patch. Please check thoroughly I have not tested all functionality.
Maybe someone can work that into git. I don't know how I would that.

🐛 | Save & Edit | Save_edit not workin in Drupal 11

Comment 28 days ago →

🇦🇹Austria maxilein

I can confirm: it is gone in Drupal 11.2

✨ | Number Formatter | Number formatter not implemented for views aggregation

Comment 28 days ago →

🇦🇹Austria maxilein

There is also an issue in core views: https://www.drupal.org/project/drupal/issues/2735997 🐛 Decimal separator and decimals settings ignored when aggregating decimal fields Needs work

🐛 | Drupal core | Simple decimals fail to pass validation

🇦🇹Austria maxilein

#378 works for me. Thank you

💬 | Menu Block | Difference to D11 core menu block?

🇦🇹Austria maxilein

Thank you.

💬 | Menu Block | Difference to D11 core menu block?

🇦🇹Austria maxilein

And what should be the difference to the core menu block, anyway?

🐛 | Tokens in Views Filter Criteria | Cannot upgrade Site to Drupal 11.2

🇦🇹Austria maxilein

This solution works: https://www.drupal.org/project/token_views_filter/issues/3499480#comment... 🐛 WSOD when filtering by Date field Active

🐛 | Tokens in Views Filter Criteria | Cannot upgrade Site to Drupal 11.2

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Tokens in Views Filter Criteria | WSOD when filtering by Date field

🇦🇹Austria maxilein

Uplifted bug, because it block site upgrade.

🐛 | Tokens in Views Filter Criteria | WSOD when filtering by Date field

🇦🇹Austria maxilein

I am facing the same error while upgrading to Drupal 11.2 running drush updb

------------------- ----------------- --------------- ------------------------
Module Update ID Type Description
------------------- ----------------- --------------- ------------------------
system 11200 hook_update_n 11200 - Add a [time]
column to the
{simpletest} table, if
existing.
system 11201 hook_update_n 11201 - Add the
[alias] field to the
{router} table.
block set_menu_block_ post-update Updates the `depth`
depth_to_null_i setting to NULL if it
f_zero is 0 in any menu
blocks.
file add_playsinline post-update Adds a value for the
'playsinline' setting
of the 'file_video'
formatter.
system convert_empty_d post-update Updates
escription_enti entity_form_mode
ty_form_modes_t descriptions from
o_null empty string to null.
system remove_path_key post-update Remove path key in
system.file.
update clear_disk_cach post-update Removes the legacy
e 'Update Manager' disk
cache.
views_data_export xml_encoding post-update Post update data
export views to
preserve original XML
encoding.
views block_items_per post-update Defaults
_page `items_per_page` to
NULL in Views blocks.
views table_css_class post-update Adds a default table
CSS class.
views update_remember post-update Clean-up empty
_role_empty remember_roles display
settings for views
filters.
------------------- ----------------- --------------- ------------------------

┌ Do you wish to run the specified pending updates? ───────────┐
│ Yes │
└──────────────────────────────────────────────────────────────┘

> [notice] Update started: system_update_11200
> [notice] Update completed: system_update_11200
> [notice] Update started: system_update_11201
> [notice] Update completed: system_update_11201
> [notice] Update started: block_post_update_set_menu_block_depth_to_null_if_zero
> [notice] Update completed: block_post_update_set_menu_block_depth_to_null_if_zero
> [notice] Update started: file_post_update_add_playsinline
> [notice] Update completed: file_post_update_add_playsinline
> [notice] Update started: system_post_update_convert_empty_description_entity_form_modes_to_null
> [notice] Update completed: system_post_update_convert_empty_description_entity_form_modes_to_null
> [notice] Update started: system_post_update_remove_path_key
> [notice] Update completed: system_post_update_remove_path_key
> [notice] Update started: update_post_update_clear_disk_cache
> [notice] Update completed: update_post_update_clear_disk_cache
> [notice] Update started: views_data_export_post_update_xml_encoding
> [notice] Update completed: views_data_export_post_update_xml_encoding
> [notice] Update started: views_post_update_block_items_per_page
> [notice] Update completed: views_post_update_block_items_per_page
> [notice] Update started: views_post_update_table_css_class
> PHP Fatal error: Declaration of Drupal\token_views_filter\TokensDateFilterTrait::validateExposed(&$form, Drupal\Core\Form\FormStateInterface $form_state) must be compatible with Drupal\datetime\Plugin\views\filter\Date::validateExposed(&$form, Drupal\Core\Form\FormStateInterface $form_state): void in /var/www/web/modules/contrib/token_views_filter/src/TokensDateFilterTrait.php on line 32
> [warning] Drush command terminated abnormally.

In ProcessBase.php line 155:

Output is empty.

✨ | Paragraphs Bundles | Carousel: adjust number of slides to browser width

🇦🇹Austria maxilein

Thank you, again!

May I ask: Does it calculate the Slide Gap also?
And when will the carousel check the actual container width: does it do this on page load or also on resize of the browser window?

✨ | Mask Field | Input mask for number fields

🇦🇹Austria maxilein

Don't get me wrong. I really don't care about the credit system ... I am not advertising on drupal.org in any way. Not my personal name, not my companies name ...

I am using Drupal for more than 10 years. Such a module did not exist. So I built it. It took me a week even though I used the help of AI.
And of course I will be using modern technologies.

And yes the module description aims to give the Drupal beginner and a developer who wants to improve the code more orientation than most modules do. It drives me nuts that Drupal is so badly documented.

Tell me where I can opt-out of the credit system.

✨ | Mask Field | Input mask for number fields

🇦🇹Austria maxilein

Thank you. Without any bad intent. Where do I mention this?

✨ | Mask Field | Input mask for number fields

🇦🇹Austria maxilein

Thank you for everything. I have built a module for that: https://www.drupal.org/project/formatted_number_input →

📌 | Formatted Number Input | Fix phpcs code formatting warnings

🇦🇹Austria maxilein

FILE: /var/www/web/modules/custom/formatted_number_input/readme.md
----------------------------------------------------------------------
FOUND 0 ERRORS AND 8 WARNINGS AFFECTING 8 LINES
----------------------------------------------------------------------
1 | WARNING | Line exceeds 80 characters; contains 242 characters
3 | WARNING | Line exceeds 80 characters; contains 274 characters
8 | WARNING | Line exceeds 80 characters; contains 81 characters
61 | WARNING | Line exceeds 80 characters; contains 81 characters
170 | WARNING | Line exceeds 80 characters; contains 99 characters
200 | WARNING | Line exceeds 80 characters; contains 82 characters
244 | WARNING | Line exceeds 80 characters; contains 81 characters
267 | WARNING | Line exceeds 80 characters; contains 113 characters
----------------------------------------------------------------------

FILE: /var/www/web/modules/custom/formatted_number_input/formatted_number_input.module
--------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
--------------------------------------------------------------------------------------
33 | WARNING | Line exceeds 80 characters; contains 136 characters
35 | WARNING | Line exceeds 80 characters; contains 94 characters
37 | WARNING | Line exceeds 80 characters; contains 82 characters
--------------------------------------------------------------------------------------

FILE: /var/www/web/modules/custom/formatted_number_input/src/Plugin/Field/FieldFormatter/FormattedNumberAsWidgetFormatter.php
-----------------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
-----------------------------------------------------------------------------------------------------------------------------
18 | WARNING | Line exceeds 80 characters; contains 84 characters
132 | WARNING | Line exceeds 80 characters; contains 88 characters
168 | WARNING | Line exceeds 80 characters; contains 81 characters
-----------------------------------------------------------------------------------------------------------------------------

FILE: /var/www/web/modules/custom/formatted_number_input/src/Plugin/Field/FieldWidget/FormattedNumberWidget.php
-----------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 13 WARNINGS AFFECTING 13 LINES
-----------------------------------------------------------------------------------------------------------------------
165 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead
265 | WARNING | Line exceeds 80 characters; contains 81 characters
314 | WARNING | #options values usually have to run through t() for translation
315 | WARNING | #options values usually have to run through t() for translation
316 | WARNING | #options values usually have to run through t() for translation
317 | WARNING | #options values usually have to run through t() for translation
338 | WARNING | Unused variable $default_symbol_placement_lang.
413 | WARNING | #options values usually have to run through t() for translation
414 | WARNING | #options values usually have to run through t() for translation
415 | WARNING | #options values usually have to run through t() for translation
416 | WARNING | #options values usually have to run through t() for translation
510 | WARNING | Translatable strings must not begin or end with white spaces, use placeholders with t() for variables
542 | WARNING | Unused variable $placement_label.
-----------------------------------------------------------------------------------------------------------------------

📌 | Formatted Number Input | Fix phpcs code formatting warnings

🇦🇹Austria maxilein

PHPCBF RESULT SUMMARY
--------------------------------------------------------------------------------------------------------------------------------------------
FILE FIXED REMAINING
--------------------------------------------------------------------------------------------------------------------------------------------
/var/www/web/modules/custom/formatted_number_input/formatted_number_input.libraries.yml 1 0
/var/www/web/modules/custom/formatted_number_input/tests/src/Unit/UnformatValueTest.php 27 0
/var/www/web/modules/custom/formatted_number_input/tests/src/Kernel/FormattedNumberFieldTest.php 6 0
/var/www/web/modules/custom/formatted_number_input/formatted_number_input.info.yml 1 0
/var/www/web/modules/custom/formatted_number_input/formatted_number_input.module 68 3
/var/www/web/modules/custom/formatted_number_input/config/schema/formatted_number_input.schema.yml 1 0
/var/www/web/modules/custom/formatted_number_input/src/Plugin/Field/FieldFormatter/FormattedNumberAsWidgetFormatter.php 19 3
/var/www/web/modules/custom/formatted_number_input/src/Plugin/Field/FieldWidget/FormattedNumberWidget.php 33 13
--------------------------------------------------------------------------------------------------------------------------------------------
A TOTAL OF 156 ERRORS WERE FIXED IN 8 FILES
--------------------------------------------------------------------------------------------------------------------------------------------

📌 | Formatted Number Input | Fix phpcs code formatting warnings

🇦🇹Austria maxilein

maxilein → created an issue.

💬 | Paragraphs Bundles | Carousel images stretched out and cut off.

🇦🇹Austria maxilein

Thank you.

💬 | Invoice Management | Can custom fields be added?

🇦🇹Austria maxilein

maxilein → created an issue.

✨ | Paragraphs Bundles | Carousel: adjust number of slides to browser width

🇦🇹Austria maxilein

maxilein → created an issue.

💬 | Paragraphs Bundles | Carousel images stretched out and cut off.

🇦🇹Austria maxilein

I could solve it by playing around with image sizes and width settings.
Can I ask you if it would make a difference to use responsive image styles for the images? Because I could not see any.

💬 | Paragraphs Bundles | Carousel images stretched out and cut off.

🇦🇹Austria maxilein

Thank you!

🇦🇹Austria maxilein

One should mention that it underlies the float max precision of php which is 15.

💬 | Paragraphs Bundles | Carousel images stretched out and cut off.

✨ | Drupal core | Increase maximum length of 32 characters for field machine names to a higher limit

🇦🇹Austria maxilein

maxilein → created an issue.

🇦🇹Austria maxilein

Most modern file systems have longer naming possibilities.

And why not use standardized abbreviations for common Drupal constructs: like bundle_settings.taxonomy_term could as well be bs.tt then you would have much more room for an intuitive naming convention that reflects the individual aspects of a site.

✨ | Gin Admin Theme | Make the "more actions" functionality configurable

🇦🇹Austria maxilein

✨ | Gin Admin Theme | Make the "more actions" functionality configurable

🇦🇹Austria maxilein

Changed to Major and BUG because it causes a lot of headaches outside of gin...

✨ | Gin Admin Theme | Make the "more actions" functionality configurable

🇦🇹Austria maxilein

Also see this comment. https://www.drupal.org/project/save_edit/issues/3528935#comment-16138378 🐛 Save_edit in GIN admin theme in Drupal CMS (11) hardly accessible Active
It shows that is impossible to rely on gin functionality in this matter.

🐛 | Save & Edit | Save_edit in GIN admin theme in Drupal CMS (11) hardly accessible

🇦🇹Austria maxilein

Sorry I was in the wrong. I used Version: 8.x-1.8 not the current dev version of save_ edit

✨ | Gin Admin Theme | Make the "more actions" functionality configurable

🇦🇹Austria maxilein

Thinking about that issue and finding others having problems with it (e.g. https://www.drupal.org/project/workflow/issues/3458569 ✨ Support Gin action item Active )- I have to say that I get the impression that there is something inherently wrong with the gin approach of putting its own functionality buttons above other modules.
Requiring the other modules to flag theme(!) specific attributes will only clutter the drupal code and cause
"Latest version of Gin Admin theme hides actions behind a more actions button unless it is identified as a #gin_action_item."

In how many modules do you expect to find #gin_action_item in the code?!

So I suggest:

Treat all functionality of any module as equal. Therefore making it configurable by admins: per entity type which buttons appear outside of the more actions menu and in which order.

I also think it is a major issue, since it concerns many other modules.

🐛 | Save & Edit | Save_edit in GIN admin theme in Drupal CMS (11) hardly accessible

🇦🇹Austria maxilein

Whatever this line does
if ($config->get('gin_primary')) {: Maybe the problem is that I use gin for admin theme (not main theme) and to edit content?

🐛 | Save & Edit | Save_edit in GIN admin theme in Drupal CMS (11) hardly accessible

🇦🇹Austria maxilein

If I change save_edit.module line 57:

     if ($config->get('gin_primary')) {
        $form['actions']['save_edit']['#gin_action_item'] = TRUE;
      }

      /*if ($config->get('gin_primary')) {*/
        $form['actions']['save_edit']['#gin_action_item'] = TRUE;
      /*}*/

it works and is visible alongside the save button.

✨ | Gin Admin Theme | Make the "more actions" functionality configurable

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Save & Edit | Save_edit in GIN admin theme in Drupal CMS (11) hardly accessible

🇦🇹Austria maxilein

🐛 | Save & Edit | Save_edit in GIN admin theme in Drupal CMS (11) hardly accessible

🇦🇹Austria maxilein

maxilein → created an issue.

✨ | Save & Edit | Allow other entities to use this feature aswel

🇦🇹Austria maxilein

A rookie question: Does ConfigEntityBundleBase also comprise blocks and paragraphs?

💬 | Menu Block | Difference to D11 core menu block?

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

Mentioning this issue may cause problems in the future for some.
https://www.drupal.org/project/drupal/issues/3070381 🐛 Base theme libraries may be output in reverse order Active

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

Thank you as always for your help.

Just to report back: I cannot reproduce the erratic behaviour. I had played with the custom.css without css aggregation disabled for quite some time.
I then changed my maxilein.libraries.yml according to https://www.drupal.org/project/drupal/issues/3070381 🐛 Base theme libraries may be output in reverse order Active to this: adding dependencies.. etc. did not change anything.
Then I re-added the weight. Changed nothing...
So out of desperation I enabled css aggregation. Changed nothing.
I played around with the settings, drush cr.
Disabled css aggregation again.
Suddenly it worked. I really don't know why.
I even tried to remove the dependency and in the end the weight only would also work.
So I still left my maxilein.libraries.yml like this:

maxilein-global:
  css:
    theme:
     css/maxilein-style.css: {weight: 400}
  dependencies:
    - solo/solo-global
  js:
    js/maxilein-script.js: {}

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

It completely varies by element. I cannot detect a pattern. Sometimes there are 3 or more other css loaded after my custom css.

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

maybe this helps: https://www.drupal.org/forum/support/post-installation/2023-12-19/solved... →

Or this https://www.drupal.org/project/drupal/issues/3467860 🐛 Logic error in Drupal's lazy load for asset aggregation Active

And here ( https://www.drupal.org/node/3473558 → ) it says: "In general, libraries should avoid setting custom weights where possible, and rely on properly declaring dependencies between libraries instead wherever possible."

And another very long standing issue here: https://www.drupal.org/project/drupal/issues/1945262 📌 Replace custom weights with dependencies in library declarations; introduce "before" and "after" for conditional ordering Needs work

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

paragraphs-bundles-custom.css still loads after maxilein-style.css
no matter whether it is in maxilein.info.yml or maxilein.libraries.yml
many drush cr ...

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

Thank you. But you are meaning in the maxilein.libraries.yml, right?

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

I now found this: https://www.drupal.org/forum/support/theme-development/2024-03-01/css-lo... →

and this https://www.drupal.org/node/3473558 →

🐛 | Solo | Subtheme not loading css in correct order

🇦🇹Austria maxilein

maxilein → created an issue.

🇦🇹Austria maxilein

Making title more descriptive

✨ | Twig Extensions | Add back missing Twig filters

🇦🇹Austria maxilein

dieterholvoet → credited maxilein → .

🇦🇹Austria maxilein

Since it is already working that way we can also add the drupal_user permissions later - or during review.

💬 | Ultimate Cron | Should "No free threads available for launching jobs" be logged as a warning or as an informational message?

🇦🇹Austria maxilein

To make it easier for anyone to find the open questions:

TODO: I have to mention that with this config I could only get the solr User to connect from search_api - not the drupal_user. I am missing some permissions in the security.json. (see // ---- Permissions for 'drupal_role' for Collection 'core2025' ---- above)
Someone can please point to the correct settings for the drupal_user here! thank you.

🇦🇹Austria maxilein

Seems to work. Thank you!

✨ | Views Summarize | Views summarize future proof alternative?

🐛 | Search API | When using "HTML filter" processor, turning on "Index title attribute" or "Index alt attribute" causes HTML to be indexed after all

🇦🇹Austria maxilein

maxilein → created an issue.

🐛 | Search API | When using "HTML filter" processor, turning on "Index title attribute" or "Index alt attribute" causes HTML to be indexed after all

🇦🇹Austria maxilein

I would also like to mention this issue: it may be a solution - at least temporary https://www.drupal.org/project/search_api/issues/3069515 💬 Silence the warnings: An overlong word (more than 50 characters) ... Needs work

✨ | Ultimate Cron | Specify job in "No free threads available for launching jobs" warning

🇦🇹Austria maxilein

I run into the same problems using search_api_solr. When large base64 encoded images are embedded in the body it makes the SOLR go out of bounds. Probably because I am using ngramstring which has a quardratic memory consumption.
Maybe an option to explicitly treat base64 encoded stuff in strings would be an idea.

I am using Drupal 11.1.7 and SOLR 9.8.1

💬 | Ultimate Cron | Should "No free threads available for launching jobs" be logged as a warning or as an informational message?

🇦🇹Austria maxilein

https://www.drupal.org/project/ultimate_cron/issues/3118275 💬 Should "No free threads available for launching jobs" be logged as a warning or as an informational message? Closed: works as designed