🇩🇪Germany @joachim namyslo

Jan, sobald ich von Wacken zurück bin, mach ich dass gern dieses WE spiele ich noch im Schlamm :-D

joachim namyslo → created an issue.

Ich hab mal eben knapp 150 Übersetzungsvorschläge hinzugefügt. Damit sind wir hier wieder auf Stand.

So maybe we should tell people where to add this screenshot than, so they can solve that issue and add a default file in the right place, so users can replace it?

It's just a thought, maybe it'll make things much easier for some people.

joachim namyslo → created an issue.

Hallo Niklas. Ich gehe schwer davon aus, dass die Ansicht, die für die Darstellung der News-Artikel zuständig ist aktuell nicht nach Anzeigesprache der Benutzeroberfläche filtert. Ich hab leider immer noch keine Admin-Rechte auf der Seite, sodass ich nicht nachsehen kann. Aber ich gebe dir einfach den Tipp schau in die Ansicht und setze den Filter für die Anzeigesprache.

That's fine. It's clear enough to understand and it saves us a lot of headaches.

Well, that looks much better than before.
It would be nicer, of course, if the background color of the circular icons could be adjusted when the values for dark mode are applied.

That would make the widget look much rounder.

What I also noticed is that the Duplicate entry created by ECA does not have an icon. Here, you could consider implementing a generic icon for such cases, but that should be the subject of a separate issue.

joachim namyslo → created an issue.

Hier sind noch 5 neue Strings dazugekommen, die hab ich mir eben geschnappt und übersetzt.

It's good to know, that this is a bigger issue. We where looking for the root cause multiple years, so if we came across a solution that solve this uppercase/lowercase issue in all affected places, that would be very great.

Dann muss ich am Wochenende wohl wieder mal commerce installieren. Vielen Dank.

Hallo Jan,

zur Frage soll ich den Modulnamen übersetzen? Ja bitte. Der bleibt in der Online-Hilfe und auf der Seite „Erweitern“ immer in englisch erhalten. Zum Finden der Module bei Google reicht dass.

Angesehen hab ich mir das ganze ich hab mich auch grade zur Thematik grade noch mal 18 Minuten ausgelassen und die Review gleich mit gemacht, damit die Leute auch mal sehen können, wie wir das tun.

Für alle die nicht so gern lesen gibt's gleich noch mal einen Link zu einem Video dazu. Die Review (Siehe Video). In 30 Minuten sollte der Server dann die Dateien neu erzeugt haben, sodass die Übersetzung dann zur Verfügung steht. Wenn dann noch was sein sollte, Rechtschreibfehler oder Grammatikfehler, die gerade übersehen wurden und ihr findet die in der UI, bitte einfach wie immer im Nachgang abändern und kurz hier bescheid geben.

Video der Review: https://youtu.be/Qib-ZbcQEEw

Review
https://localize.drupal.org/translate/languages/de/translate?project=dec...

Oh ha, dann müssen wir damit leben. Dass sind ja nicht so viele Strings. Dann schreiben wir dekoratives Bild, lassen dass zu und denken nicht weiter drüber nach. Ok? Ich schreibe heute Abend gern die Strings um.

Also ich hab mal Widget durch Steuerelement ersetzt, so wie sich das gehört aber das wort dekorativ ist einfach nicht gut gewählt. Also ich weiss, was das Modul macht, aber Bilder sind immer dekorativ. Egal ob sie einen Alt-Text haben oder nicht.Also als normalsterblicher Nutzer würde ich mich erst Mal nachdenklich an der Nase kratzen und mich fragen was das soll. Ausgezeichnet ist Blödsinn, dass ist richtig. Aber ich hab keine gute Alternative. Gefühlt hört sich dekoratives Bild einfach K***e an. Ich überleg mir was.

Ja dass ist mist, dass sehe ich. Ich schau mal was du vorgeschlagen hast.

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

Ok. Ich hab die Dinger jetzt mal zugelassen. Es könnte sein, dass da noch ein Syntax Fehler wegen eines BR auftaucht. Das wissen wir aber erst wenn der Server die Dateien gerendert hat.

Einfach mal Vorschlagen. Dann können wir die Suggestions exportieren und dass mal live betrachten. Ich meine wenn wir uns schon einmal in 100 Jahren mit Drupal commerce beschäftigen, dann können wir dass auch gleich richtig machen.

Das machen wir doch gern.

Ich habe noch kein Ticket geschrieben, weil ich nicht weiß warum das so gelöst wurde. Du kannst gern ein Ticket aufmachen, ich will den Leuten hier nicht immer die Credits klauen.

Hello Jürgen,
Hello Jeeva,

that's a very good question.

Event

In the case of the word “event,” the context is definitely technical, as in “logging event.” This is because, in simple terms, Danse actually logs everything first in order to inform users about an event that has occurred. This is not specific to Danse.

Background Information

However, it is important to know that Drupal uses the wrong word whenever there is no context.

This is because Drupal tries to use as few translations as possible so as not to bloat the websites' databases with strings translated into languages other than English. So we don't just have reusable fields in Drupal, we actually have reusable translation strings. Wherever this resampling doesn't work, a translation context is needed.

Of course, you both know this, but you never know who might stumble across this issue one day.

Nootification and Notification action

In the case of Notification and Notification action, I didn't find any cases when searching the translation server that would lead me to conclude that we need context here. A notification is always a notification, and a notification action is always something you do with a notification, for example:

Edit a notification
Delete a notification
Create a notification
etc.

None of the modules for which there are currently translations on the Drupal translation server use notification action in a different sense, so we don't need any context here.

+1 for this do not let it die please.

joachim namyslo → created an issue.

joachim namyslo → created an issue.

joachim namyslo → created an issue.

joachim namyslo → created an issue.

Ha,

da kann ich lang in der UI suchen. In /home/joachim/cms/web/core/modules/config_translation/src/Plugin/Menu/LocalTask/ConfigTranslationLocalTask.php steht von Zeile 25 - 33 folgender Code:

 public function getTitle(?Request $request = NULL) {
    // Take custom 'config_translation_plugin_id' plugin definition key to
    // retrieve title. We need to retrieve a runtime title (as opposed to
    // storing the title on the plugin definition for the link) because
    // it contains translated parts that we need in the runtime language.
    $type_name = mb_strtolower($this->mapperManager()->createInstance($this->pluginDefinition['config_translation_plugin_id'])->getTypeLabel());
    return $this->t('Translate @type_name', ['@type_name' => $type_name]);
  }

Die Zeile 31 Im speziellen enthält die Funktion mb_strtolower Und die sorgt dafür dass dass wort Ansicht kleingeschrieben wird.

Funktion und Zweck von mb_strtolower
mb_strtolower ist eine PHP-Funktion, die alle Buchstaben einer Zeichenkette in Kleinbuchstaben umwandelt – und zwar unter Berücksichtigung von Multibyte-Zeichencodierungen wie UTF-8. Das ist besonders wichtig für Sprachen und Zeichen, die außerhalb des klassischen ASCII-Bereichs liegen, etwa Umlaute (ä, ö, ü), kyrillische oder griechische Buchstaben.

Unterschiede zu strtolower
Die Standardfunktion strtolower() funktioniert nur zuverlässig mit einfachen ASCII-Zeichen. Sie wandelt beispielsweise das deutsche "Ä" nicht korrekt in "ä" um, wenn der String in UTF-8 kodiert ist. Hier versagt strtolower() und gibt das Zeichen entweder unverändert zurück oder es entstehen fehlerhafte Zeichen.

mb_strtolower() hingegen erkennt die Zeichenkodierung (z.B. UTF-8) und kann so auch mehrbyte-Zeichen korrekt umwandeln. Das macht die Funktion unverzichtbar für internationale Anwendungen und alle Strings, die nicht nur aus einfachen lateinischen Buchstaben bestehen.

Syntax
php
mb_strtolower(string $string, ?string $encoding = null): string
$string: Die umzuwandelnde Zeichenkette.

$encoding (optional): Die Zeichencodierung, z.B. "UTF-8". Wird kein Wert angegeben, wird die interne Standardcodierung verwendet.

Beispiel
php
$str = 'ÄäÖöÜü';
echo mb_strtolower($str, 'UTF-8'); // Gibt aus: ääööüü
Im Gegensatz dazu würde strtolower($str) das Ergebnis "ÄäÖöÜü" liefern, also keine Umwandlung der Umlaute.

Typische Anwendungsfälle
Verarbeitung von Benutzereingaben (z.B. E-Mail-Adressen, Suchbegriffe)

Einheitliche Speicherung von Daten in der Datenbank

Internationalisierte Anwendungen, bei denen verschiedene Zeichensätze vorkommen

Hinweise
Die Funktion ist nur verfügbar, wenn die PHP-Erweiterung mbstring installiert ist.

Die Umwandlung ist unabhängig von den lokalen Einstellungen (Locale) und funktioniert für alle Zeichen, die laut Unicode einen Kleinbuchstaben besitzen.

Performance
Multibyte-Funktionen wie mb_strtolower() sind langsamer als die Standardfunktionen, da sie komplexere Zeichencodierungen unterstützen. Wo ausschließlich ASCII-Zeichen verarbeitet werden, kann weiterhin strtolower() verwendet werden.

Zusammenfassung
mb_strtolower wandelt eine Zeichenkette unter Berücksichtigung von Multibyte-Zeichencodierungen wie UTF-8 in Kleinbuchstaben um. Sie ist essenziell für die korrekte Verarbeitung internationaler Zeichen und sollte immer dann eingesetzt werden, wenn Zeichen außerhalb des ASCII-Bereichs vorkommen

Das bedeutet, dass wir hier von unserer Seite aus nichts machen können. Es sei denn wir ürofen dass und finden heraus, dass die Funton an der Stelle nicht gebruacht wird.

Also ich hab jetzt mal in den Code gesehen.

Die Zeichenfolge, die hier verwendet wird ist https://localize.drupal.org/translate/languages/de/translate?sid=2066288
Jetzt muss ich bloß noch rausbekommen, wo die Type-Names sind und warum zum Geier der Type-Name für Ansicht klein geschrieben wurde. Ich drehe erst mal die fälschlicherweise verdächtigten Zeichenfolgen wieder zurück

joachim namyslo → created an issue.

Of course, we can.

1. Install Yourls and make it accessible under a subdomain of your server.
2. Don't forget to configure Yourls so that you can log in, and the value YOURLS_COOKIEKEY is generated in your config.php. You can find out how to do this in the excellent Yourls documentation: https://yourls.org/docs

Once you have installed Yourls and can log in to the UI via shorten.yourdomain.com/admin with the username and password you specified, you will need your API key.

If we stick with the example above, you can find your API key at shorten.yourdomain.com/admin/tools php in the section
Secure passwordless API call
under the heading
Usage of the signature token
There, in the API request example, you will find the token that was randomly generated for your Yourls installation.

An example:
https://shorten.yourdomain.com/yourls-api.php?signature=5344672a5f&action=...
Accordingly, the token you need is: 5344672a5f
After you have installed Shorten and activated the Shorten URLS custom services module next to the Shorten module, you are ready to save your Yourls installation as a custom service in the module configuration.

To do this, go to the page https://yourdomain.com/admin/config/services/shorten/custom.

In the Title field, enter Yourls, and in the API endpoint URL field, enter:
https://shorten.yourdomain.com/yourls-api.php?action=shorturl&format=sim...
Leave the response type set to Text.

Then click Save configuration.

Congratulations: You have just added a new service provider to the Service and Backup Service drop-down menus. If you entered Yourls in the Title field, you will now find the provider with the value Yourls in the two drop-down menus on the page https://yourdomain.com/admin/config/services/shorten
Note: Yourls can only be specified once, either as a service or as a backup service. Anything else makes no sense.

Select Yourls as the service and check that you have selected Curl in the Method section.

To test whether it works, you can add the shorten urls block under /admin/structure/block to the sidebar, for example, and save your new block layout. You can then switch to your website's home page and enter the address from your browser's address bar into the block.

You can also use https://drupal.org to test it.

Once you have entered the domain in the input field of the block, simply click on Shorten URL.
If everything has worked as desired, you will now find the shortened URL in the admin area of Yourls.
Please note: The module transfers the entered addresses to Yourls, and you can also view them in the admin area.

What it does not do is return the shortened version to Drupal so that a user can see the URL created in this way. This is unfortunate and makes using Yourls together with Shorten relatively pointless for most users. But it does what it is intended to do.
Have fun recreating it.

any updates on this?

Any updates oion this?

Thank you guys I do not know how this happened but I'll take a look at the patch and try to apply the change.

I am not sure if it'll fix it. That's why I opened the bug report. If it fix that I could use some help to get recipes back.

joachim namyslo → created an issue.

Dear Community, It's a bit of a shame that we're not pursuing this issue further. We now have Klaro! and can provide decent privacy notices, but our videos are still being loaded from youtube.com. Could we perhaps address this issue in Zewitnah and simply offer Youtube Nocookie as a third alternative Oembed provider for Drupal Core?

That would be so nice and simple. The easiest solution for users would be if they could simply paste normal URLs from YouTube Studio and the Oembed provider would have a checkbox in the formatter options to choose whether to use the normal YouTube version or no-cookie. I mean, if we're implementing data protection in Drupal, we might as well do it right, right?

joachim namyslo → created an issue.

joachim namyslo → created an issue.

Alles klar. Danke, dass ziehen wir gerade.

joachim namyslo → created an issue.

joachim namyslo → created an issue. See original summary → .

joachim namyslo → created an issue.

joachim namyslo → created an issue.

I know. I do not have a clue how to prove it. Suppose someone comes across this and has some Ubuntu/Debian server where Drupal Cms is running and automatic updates are enabled. Tell me if you got the same error when automatic updates is enabled. I posted that issue in case it doesn't happen exclusively when I set up a server.

So that Drupal CMS and automatic updates could be used on Ubuntu and Debian, too. So maybe someone tries to set up Drupal CMS on Ubuntu 22.04 with Drupal Core 11.6 and composer in /usr/local/bin.

I turned the module off for now, but maybe it's not just me getting this.

So I tried everything now. Even switching the whole server from Ubuntu 22.04 to Debian bookworm 12. And the error persists. So it is very unlikely that 3 different systems are all misconfigured. So what can I do to get automatic update to find Composer. That's very seldom

hm, I did that and it seems to me that everyting looks fine when I execute that via ssh only.

That is the reason why I reopened the Issue. I have no intention of annoying anyone with this, I would much rather know why the error message regarding the readiness test simply cannot be eliminated.

Because when you execute that via ssh everyting is fine. But when I try to re run redyness checks via the status report page link drupal is telling me that there is an error.

I updated the site with composer so now it is Drupal 11.16 with all latest module versions. But the rediness check still fails and the message simply does not give me any indication as to which requirement is not met so that the readiness check can pass again without errors. To be honest, I am a little at a loss.

In the meantime, I have also moved the page from the WSL to a normal web server with Ubuntu 24.04.2 LTS, PHP 8.3.20 (cli) (built: Apr 10 2025 21:33:50) and Mysql Ver 15.1 Distrib 10.11.11-MariaDB. The error message appears there as well.

That is the reason why I reopened that issue. Here is the output from the command mentioned in #9

🕙[ 21:46:36 ] onUbuntu ➜ /usr/bin/composer validate --check-lock --no-check-publish --with-dependencies --no-ansi --working-dir=/var/www/cms
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/project_browser : unbound version constraints (@beta) should be avoided
- require.drupal/webform : unbound version constraints (@beta) should be avoided
asm89/stack-cors is valid
carbonphp/carbon-doctrine-types is valid
chi-teck/drupal-code-generator is valid
clue/stream-filter is valid
commerceguys/addressing is valid
composer/installers is valid
composer/semver is valid
composer/spdx-licenses is valid
consolidation/annotated-command is valid
consolidation/config is valid
consolidation/filter-via-dot-access-data is valid
consolidation/log is valid
consolidation/output-formatters is valid
consolidation/robo is valid
consolidation/site-alias is valid
consolidation/site-process is valid
davedevelopment/stiphle is valid
dflydev/dot-access-data is valid
doctrine/annotations is valid
doctrine/collections is valid
doctrine/deprecations is valid
doctrine/inflector is valid
doctrine/lexer is valid
dragonmantank/cron-expression is valid
drupal/add_content_by_bundle is valid
drupal/address is valid
drupal/addtocal_augment is valid
drupal/ai is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/ai_agents is valid
drupal/ai_image_alt_text is valid
drupal/ai_provider_anthropic is valid, but with a few warnings
# General warnings
- require.wpai-inc/anthropic-sdk-php : unbound version constraints (>=0.1.0) should be avoided
drupal/ai_provider_openai is valid, but with a few warnings
# General warnings
- require.openai-php/client : unbound version constraints (>=v0.10.1) should be avoided
drupal/attribution is valid, but with a few warnings
# General warnings
- License "GPL-2-or-later" is not a valid SPDX license identifier, see https://spdx.org/licenses/ if you use an open license.
If the software is closed-source, you may use "proprietary" as license.
drupal/autocomplete_deluxe is valid
drupal/automatic_updates is valid
drupal/autosave_form is valid
drupal/better_exposed_filters is valid
drupal/book is valid
drupal/bpmn_io is valid
drupal/captcha is valid
drupal/checklistapi is valid
drupal/coffee is valid
drupal/content_planner is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/core is valid
drupal/core-composer-scaffold is valid
drupal/core-project-message is valid
drupal/crop is valid
drupal/ctools is valid
drupal/custom_book_block is valid
drupal/dashboard is valid
drupal/drupal_cms_accessibility_tools is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.3) should be avoided
drupal/drupal_cms_admin_ui is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.3) should be avoided
drupal/drupal_cms_ai is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_anti_spam is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_authentication is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.3) should be avoided
drupal/drupal_cms_blog is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_case_study is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_content_type_base is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_events is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_forms is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_google_analytics is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_image is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_news is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_olivero is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
drupal/drupal_cms_page is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_person is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_privacy_basic is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_project is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_remote_video is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_search is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_seo_basic is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_seo_tools is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/drupal_cms_starter is valid, but with a few warnings
# General warnings
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/easy_breadcrumb is valid
drupal/easy_email is valid
drupal/easy_email_express is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/easy_email_standard is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/easy_email_text_format is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/easy_email_types_core is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/easy_email_types_default is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/eca is valid
drupal/editoria11y is valid
drupal/estimated_read_time is valid
drupal/field_group is valid
drupal/filter_perms is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/focal_point is valid
drupal/friendly_captcha_challenge is valid
drupal/friendlycaptcha is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
- require.drupal/captcha : unbound version constraints (>=1 || <=2) should be avoided
drupal/geocoder is valid
drupal/geofield is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/gin is valid
drupal/gin_login is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/gin_toolbar is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/google_tag is valid
drupal/honeypot is valid
drupal/jquery_ui_autocomplete is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/jquery_ui_button is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/jquery_ui_checkboxradio is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/jquery_ui_controlgroup is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/jquery_ui_datepicker is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/jquery_ui_menu is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/jquery_ui_resizable is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/key is valid
drupal/klaro is valid, but with a few warnings
# General warnings
- No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
drupal/klaro_js is valid
drupal/leaflet is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/linkit is valid
drupal/login_emailusername is valid
drupal/mailsystem is valid
drupal/media_library_importer is invalid, the following errors/warnings were found:
# General errors
- name : Does not match the regex pattern ^[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]|-{1,2})?[a-z0-9]+)*$
- name : Media Library Importer is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "^[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]?|-{0,2})[a-z0-9]+)*$".
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/media_thumbnails is valid
drupal/media_thumbnails_video is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
- require.drupal/media_thumbnails : unbound version constraints (>=2.0) should be avoided
- require.php-ffmpeg/php-ffmpeg : unbound version constraints (>=0.14.0) should be avoided
drupal/menu_link_attributes is valid
drupal/metatag is valid
drupal/moderation_sidebar is valid
drupal/module_filter is valid
drupal/nouislider_js is valid, but with a few warnings
# General warnings
- License "MIT License" is not a valid SPDX license identifier, see https://spdx.org/licenses/ if you use an open license.
If the software is closed-source, you may use "proprietary" as license.
drupal/pathauto is valid, but with a few warnings
# General warnings
- require.drupal/token : unbound version constraints (*) should be avoided
- require.drupal/ctools : unbound version constraints (*) should be avoided
drupal/plyr is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/prismjs is valid
drupal/project_browser is valid
drupal/queue_ui is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/reading_progress_bar is valid
drupal/recipe_installer_kit is valid, but with a few warnings
# General warnings
- require.drupal/core : unbound version constraints (>=10.4) should be avoided
drupal/redirect is valid
drupal/robotstxt is valid
drupal/sam is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/scheduler is valid, but with a few warnings
# General warnings
- Key _comment is a duplicate in /var/www/cms/web/modules/contrib/scheduler/composer.json at line 44
drupal/scheduler_content_moderation_integration is valid
drupal/search_api is valid
drupal/search_api_autocomplete is valid
drupal/search_api_exclude is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/selective_better_exposed_filters is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
drupal/seo_checklist is valid
drupal/simple_sitemap is valid
drupal/sitemap is valid
drupal/smart_date is valid
drupal/smart_trim is valid
drupal/svg_image is valid
drupal/symfony_mailer_lite is valid
drupal/tagify is valid
drupal/token is valid
drupal/token_or is valid
drupal/trash is valid
drupal/views_slick_animate is valid, but with a few warnings
# General warnings
- License "MTL" is not a valid SPDX license identifier, see https://spdx.org/licenses/ if you use an open license.
If the software is closed-source, you may use "proprietary" as license.
drupal/webform is valid
drupal/yoast_seo is valid
drush/drush is valid
egulias/email-validator is valid
enshrined/svg-sanitize is valid
evenement/evenement is valid
geocoder-php/common-http is valid
geocoder-php/nominatim-provider is valid
goalgorilla/rtseo.js is valid, but with a few warnings
# General warnings
- License "GPL-3.0" is a deprecated SPDX license identifier, use "GPL-3.0-only" or "GPL-3.0-or-later" instead
- The version field is present, it is recommended to leave it out if the package is published on Packagist.
grasmash/expander is valid
grasmash/yaml-cli is valid
guzzlehttp/guzzle is valid
guzzlehttp/promises is valid
guzzlehttp/psr7 is valid
html2text/html2text is valid
illuminate/collections is valid
illuminate/conditionable is valid
illuminate/contracts is valid
illuminate/macroable is valid
illuminate/support is valid
itamair/geophp is valid, but with a few warnings
# General warnings
- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
laravel/prompts is valid
league/commonmark is valid
league/config is valid
league/container is valid
league/html-to-markdown is valid
masterminds/html5 is valid
mck89/peast is valid
mtownsend/read-time is valid
mtownsend/xml-to-array is valid
nesbot/carbon is valid
nette/schema is valid
nette/utils is valid
nikic/php-parser is valid
openai-php/client is valid, but with a few warnings
# General warnings
- require.psr/http-factory-implementation : unbound version constraints (*) should be avoided
pear/archive_tar is valid
pear/console_getopt is valid
pear/pear-core-minimal is valid
pear/pear_exception is valid
phootwork/collection is valid
phootwork/lang is valid
php-ffmpeg/php-ffmpeg is valid
php-http/discovery is valid
php-http/guzzle7-adapter is valid
php-http/httplug is valid
php-http/message is valid
php-http/multipart-stream-builder is valid
php-http/promise is valid
php-tuf/composer-stager is valid
phpowermove/docblock is valid
psr/cache is valid
psr/clock is valid
psr/container is valid
psr/event-dispatcher is valid
psr/http-client is valid
psr/http-factory is valid
psr/http-message is valid
psr/log is valid
psr/simple-cache is valid
psy/psysh is valid
ralouphie/getallheaders is valid
revolt/event-loop is valid
sebastian/diff is valid
simshaun/recurr is valid
spatie/temporary-directory is valid
symfony/cache is valid
symfony/cache-contracts is valid
symfony/clock is valid
symfony/console is valid
symfony/css-selector is valid
symfony/dependency-injection is valid
symfony/deprecation-contracts is valid
symfony/error-handler is valid
symfony/event-dispatcher is valid
symfony/event-dispatcher-contracts is valid
symfony/filesystem is valid
symfony/finder is valid
symfony/http-foundation is valid
symfony/http-kernel is valid
symfony/mailer is valid
symfony/mime is valid
symfony/polyfill-ctype is valid
symfony/polyfill-iconv is valid
symfony/polyfill-intl-grapheme is valid
symfony/polyfill-intl-idn is valid
symfony/polyfill-intl-normalizer is valid
symfony/polyfill-mbstring is valid
symfony/polyfill-php80 is valid
symfony/polyfill-php81 is valid
symfony/polyfill-php83 is valid
symfony/polyfill-php84 is valid
symfony/process is valid
symfony/psr-http-message-bridge is valid
symfony/routing is valid
symfony/serializer is valid
symfony/service-contracts is valid
symfony/string is valid
symfony/translation is valid
symfony/translation-contracts is valid
symfony/validator is valid
symfony/var-dumper is valid
symfony/var-exporter is valid
symfony/yaml is valid
tijsverkoyen/css-to-inline-styles is valid
twig/twig is valid
voku/portable-ascii is valid
webmozart/assert is valid
willdurand/geocoder is valid
wpai-inc/anthropic-sdk-php is valid
yethee/tiktoken is valid

reopened the issue because I got this even on a regular Ubuntu Server without WSL so that still seems to be valid.

Hello dear Drupal Community.

first of all I would like to thank Catch for taking the time to reference the issue I created yesterday.
I already thought so and therefore just took 25 € out of my wallet to test Drupal CMS on Plek. I can tell you with certainty that the error disappears as soon as you (if you can, because you have root access) delete the file composer.phar in the directories

./usr/lib/plesk-9.0/
./opt/psa/admin/plib/modules/composer/resources/composer/
./opt/psa/var/modules/composer/
has been updated to the current version 2.8.8. For many of you, this can probably only be done by the service provider.

Plesk wird nämlich auch heutzutage noch mit Composer version 2.2.5 2022-01-21 17:25:52 ausgeliefert. This version of composer is too old to work with Drupals Automatic Update Module and that is the root cause of the issue. Updateing composer would fix that. But this is something the control panel vendors or yor servcie providers have to do.

On the software side, you can only intercept this with a nice error message. You can find a suggestion for such an error message in the referenced issue.

joachim namyslo → created an issue.

joachim namyslo → created an issue.

joachim namyslo → created an issue.

Ist erledigt vielen Dank

Also hab mir dass jetzt mal kurz angesehen und musste leider feststellen, dass zwar der ober e Punkt, also die Shipping-Methods tatsächlich Versandarten meint, dass ich aber noch nicht so genau weiß, was der Untere Punkt, also die Shipping Types machen. Dies sind auch in keiner Dokumentation weder Version 1 noch Version 2 von Commerce dokumentiert.

Dass bedeutet ich muss mich jetzt durch die englische Demo wurschteln und versuchen herauszufinden, was durch diese erzeugt wird, um eine Benennung zu finden. Aktuell tippe ich auf Versandbestätigungen. Das ist aber nur ein Educated Guess., wie man so schön sagt und leider noch nicht begründet. Wenn dem so ist, müssen wir das auch hier noch irgendwo dokumentieren, weil sonst bestimmt wieder irgendjemand vorbeikommt, der's gut meint und das ganze wieder abändert :-D

Das ist jetzt so lange keinem aufgefallen, dass es auch noch ein paar Tage liegen bleiben kann, bis ich mir die englischsprachige Demo mal genauer ansehen kann. Solltest du wissen, was unter dem Punkt Shipment Types genau konfiguriert werden kann, sag einfach bescheid.

Hallo Renato,

kannst du mich bitte an diesem Punkt noch mal abholen. Die deutsche Post sagt ja offiziell Versandart.

- Päckchen
- Paket
- Brief
-usw.

Das Wort Methode beschreibt die Art und Weise wie man etwas tut

Wie genau unterscheiden sich die beiden Begriffe in Drupal Commmerce. Gibt es visuelle Beispiele (Screenshots, Videos) die das Problem illustieren?

Andernfalls müsste ich die komplette Distro installieren und mir dass ansehen. Ich hoffe du kannst hier weiterhelfen.

Grüße

Aktuell hinzugekommene Übersetzungen brauchen Review

https://localize.drupal.org/translate/languages/de/translate?project=pro...

Updates brauchen Review
https://localize.drupal.org/translate/languages/de/translate?project=kla...

joachim namyslo → created an issue.

Hallo Jan,

ich hab in der ersten Review nur zwei kleine Anmerekungen.

1. https://localize.drupal.org/translate/languages/de/translate?sid=2985416

Der Bindestrich ist eine Kann-Regel im Deutschen, wenn es darum geht deutsche Wörter miteinander zu verbinden.
Gott sei dank, denn auf diese Weise zusammengebundene Wörter sehen immer so deplatziert in der UI von Drupal aus. Also solange du nicht wirklich den alten Klassiker: Donau-Dampfschiffs-Fahrt-Kapitäns-Mützen-Aufdruck. verbinden musst, um die Lesbarkeit des Wortes zu gewährleisten, lass den Bindestrich weg. Es brennt beim Lesen in den Augen. (Voricht: Subjektive Meinung).

Eine weselntlich aufgeklärtere Meinung zu dem Thema könnt ihr hier nachlesen.
https://web.archive.org/web/20220629124720/https://www.textschoepfung.de... Es ist so schade, dass es diese Seite nur noch so gibt. Ich finde die sollte zur Pflichtlektüre eines jeden Übersetzers in diesem Projekt gehören. Deswegen verlinke ich sie hier noch mal.

Ansonsten habe ich die letzte nicht übersetzte Zeichenfolge, den Modulnamen einfach mitübernommen.

Es gibt in der Community die einen, die sagen, Modules müssen nie ganz übersetzt werden, weil zum Beispiel Modulnamen im Englischen und im Deutschen gelich sind und dadurch nur die Datenbank der Website die die eine Übersetzung importiert nur unnötig aufgeblkät wird. Deswegen gibt es das Modul: l10n-Tools ( https://www.drupal.org/project/l10n_tools → )

Und es gibt mich, der an die armem Übersetzer hier auf dem Übersetzungsserver denkt, die die Verantwortung dafür haben, dass neben dem Kernsystem alle von der Community bereitgestellten Zusatzmodule möglichst zu 100 % übersetzt sind, damit ihre Nachfolger, im Falle einer Aktualisierung der Strings eines Moduls, mit diesem möglichst wenig Aufwand haben.

Deswegen habe ich mir erlaubt, auch den Modulnamen mit zu übersetzen, was dafür sorgt, dass es für alle Originalzeichenfolgen innerhalb des Moduls eine Übeersetzung gibt. Und den Statusbalken für des Modula auf glatte 100 % hebt.

PS: Der Jan weeis dass natürlich, aber ich weiß ja nie, wer über diese Issues fällt, deswegen wollte ich das hier noch mal erwähnen.

Ich denke ich werde am Samstatg eine kurze UI-Review durch installation des Moduls und import der Übersetzungsvorschläge in einer frischen Drupal-Installation druchführen und mir die Zeichenfolgen noch mal innerhalb des Kontexts der Benutzeroberfläche ansehen. Wenn jemand schneller ist und etwaige ungereimtheiten hier meldet, bin ich auch nicht böse, dann hab ich am Samstag weniger zu tun..

Vielen Dank für die tollen Übersetzungsvorschläge.

First point: The installer. This belongs in a separate issue. I know that this would also go beyond the scope. If there is already an issue for this, please link to it on the right-hand side.

Nevertheless, I would like to briefly note here that the installer is the first point of contact with Drupal for many users. If we continue to allow the display language to be mixed between English and other languages (e.g. when selecting a time zone [country/city/state]), then users are likely to continue to wonder why, on the one hand, we advertise with first-class multilingual support but, on the other hand, show during installation that this does not always work. Everything else belongs in a separate issue.

Second point: Configuration translations (primarily views but also menu labels and descriptions).

As far as views and basically all other configuration translations are concerned, I understand that we are currently displaying the English originals here, even if a website is installed in a language other than English, but as an end user, I simply do not accept this.

If I put myself in the shoes of an international agency, I would say something like the following:
“We want labels of views, titles, filter options and the like to continue to be available in English even on sites installed in Spanish, for example, because our multinational employees must be able to make configurations on a site whose default language is Spanish. Therefore, it would be good if we could first import English-language values here, which would then have to be translated manually.”
I have read this elsewhere on Drupal.org, unfortunately, I can no longer find the reference issue.

From an agency's point of view, this is certainly true. However, as an end user, I will contradict this statement and say something like the following:

1. I have installed Drupal in my native language so that I understand what I am triggering when I activate or deactivate an option in Drupal.
2. I activate a module or recipe for Drupal that adds a new view, a new menu or a new dashboard and notice that I, as an administrator, or even at the frontend (for example, when a view does not yet contain any content or I activate a filter within the view), am suddenly shown English texts.

a. I don't understand this.
i. For one thing, I didn't install the site in English.
ii. Furthermore, there is a translation for the Drupal user interface in my language
iii. Furthermore, the translation of the relevant character string is available there.
iv. Nevertheless, the view provided by the newly added recipe/module is still partly in English.

1. My conclusion is: Drupal's multilingual support is not as good as it is made out to be.
2. So I'll just sit down and translate such standard messages and button texts myself, so that Drupal at least looks like it supports multilingualism perfectly on my website.
3. Now I have to spend time on something that the responsible translators have already done. What's the point? Why is that so?
Example: This page does not contain any content, yet. (Text if there is no Content in a View.
Add a Blog Post
Filter --> Button Label (Apply) ect. (Filter options in general, Buttons for exposed Filters, ect.)

This is exactly what many end users experience when they first start using Drupal.
This applies to view components, menu names, and much more in Drupal.

Guys, I understand both worlds. Really!

But we have to do something about it. From the view point of an end unser it is unacceptable for Drupal to display English strings in the user interface when it is displayed in a different display language.

Especially not if translations are already available for a particular part of Drual on localize.drupal.org. We as a community are no longer being properly informed about the fact that there could be a plausible reason for this. This is due to the expectations of many end users, who in the age of AI simply assume that it should no longer be the case that they encounter situations within a software in which there is a mix of different languages in the display language of a user interface, if this has not been explicitly specified by the end user.

Similarly, this can be applied, for example, to menu names and link labels within menus.

If a menu is named Welcome, as in the case of the Drupal CMS Dashboard recipe, or in the case of Drupal Corr Main Navigation, then as an end user I expect the name of the respective menu and its description to be in the default display language of the site that was selected when the website was installed.

Unfortunately, Drupal still doesn't do this well, even in version 11. We need to be careful here and write tests to help developers identify such problems early on.

Third and last point: We urgently need guidelines for developers on how to write translatable original strings, as well as technical control routines.

If you take a look at the translation server, you'll find a number of original strings that look something like this:

<div class=“messages messages--info”>Your CivicTheme (for Starshot) version: @version</div>

The point is that we do not get such translations translated because of the API function
https://api.drupal.org/api/drupal/core%21modules%21locale%21locale.modul...
not translated.

These are rejected when importing translations into Druapal because of the above-mentioned function that simply does not allow div tags. This means that Drupal is not 100% translatable by default, for the sake of security.

Developers who are not aware of this may inadvertently cause such translations to end up on the server. If we want to keep Drupal future-proof, then we need a solution that checks submitted original strings against the tags contained in the function locale_string_is_safe at the latest in the publication process of a module or theme and rigorously advises developers to modify the affected strings so that they are translatable before the POT file for a module can be deployed to the translation server.

This is half the battle with this problem. The other half is to find such strings in modules that have already been published and to point out to the maintainers which of your modules or themes contains original strings that could be improved.

At least since Drupal 7, these errors have become commonplace and as much as I like translating Drupal to make it more accessible to newcomers and interested parties, it is becoming increasingly difficult to keep track of which project maintainer has been informed that there is an incorrectly written original string in their module and whether or not the problem has been fixed. I can only speak for myself, but I can't do it in my free time. There are simply too many of the same kind of issues to manually track them.

I can imagine that especially the last point, which tends to fall into the areas of infrastructure and documentation teams, does not necessarily fit into this track. But I don't know where or with whom I should talk about it if I don't bring it up here. This is a big problem and one that we have been putting off since Drupal 7 and have not been able to get under control at any level. That's why I don't want to leave it unmentioned here.

Update.

It seems the business logig is there, And the issue occoures beacause the text arrea field looses focus after code was insertet. So if you don't feel the logig behind that should be changed this should be documented at least.

The Issue can be solved by
1. Insert code
2. Click into the text area again.
3. user the right or left arrow key depending on your reading direction. to get your corser back
4. hit return.

Theese are additional steps after inserting code while if a paragraph would be added here it'll more obvious to most users that they have to click below the code insert to continue writing.

joachim namyslo → created an issue.