🇩🇰Denmark @ressa

I created 📌 Use internally hosted analytics for drupal.org such as Matomo, to respect user privacy Active .

ressa → created an issue.

Thanks @drumm, it's so nice to see the beautiful fonts in the headers, even with third-party resources blocked.

The final step to make drupal.org fully GDPR compliant, would be to replace GA with for example Matomo, so that the domains below don't get contacted, and sensitive user data shared:

• google.com
• google-analytics.com
• googletagmanager.com

Luckily, the https://www.drupal.org/project/matomo → module exists, and migrating from GA4 is fairly trivial, see for example Why we switched from GA4 to Matomo and How to set up Matomo in Drupal.

Perhaps Specbee can help Drupal Association with this last GDPR-task?

Fantastic, thanks @grevil!

Thanks for the clean up @hansfn!

It looks interesting, thanks for working on it @hswong3i! Perhaps you can make a GIF or a movie, to highlight and clarify which features are added?

Thanks for being open to my suggestion! I left a comment in the other issue.

I suggested in 📌 Document using local library file, with CDN as fallback Needs review to pragmatically include the library in the module, making life easier for the end user, and got positive feedback.

@grevil:

@ressa, that would probably be the best approach for the end user I agree! But we would need to manually update the js library once in a while.

Although I am quite confused, as to why the npm-asset package and the gihub latest github release are version-vise out of sync! (3.0.5 vs. 1.0.0), seems like they point to two different repositiories. I'll comment that in the parent issue.

It's great that you are open for this suggestion, thanks!

Since JavaScript Cookie Version 3 was released in July 2021, more than three years ago, there were just a few NPM-related releases ... So it's updated quite rarely.

I think that's a pretty strong argument for bundling the library inside the module.

Then, not only would the CDN/GDPR-issues be solved, installation and maintenance of the module would also be much easier for the end user. Especially if the package versions are out of sync. This would be yet another argument for taking the burden of figuring this out off the shoulders of the end users.

What do you think?

That's great @grevil, but what about the idea of pragmatically including the library in the module, making life easier for the end user?

You probably only need one reference, from star to constellation. Then create a view block:

• Filter criteria: Content: Content type (= Star)
• Contextual filters: Content: Constellation (Default: Content ID from URL)

Now, if you enter "1" under "Preview with contextual filters", only stars referring the constellation with node #1 will be listed. Show the block only on Constellation content type.

Under the individual star, simply show the Reference field to the Constellation. No more effort needed :-)

Thanks for the link. You could consider reaching out to the maintainers (or create an issue) and ask them for an estimate to get the module covered by the Drupal Advisory Policy? This is Open Source after all, and the free software we all enjoy, doesn't write itself :-)

Specifically, ask which issues need to get fixed for a stable release, and an estimate on the budget. That way, you can both help improve Drupal, maybe even get new features you want added, while getting the module covered by the Drupal Advisory Policy.

For an example on the process, see 🌱 Plan for stable release Fixed , where Simplenews was made ready for a stable release by a kind sponsor, think modular - digital solutions GmbH.

After sponsoring this improvement, Alberta Energy Regulator can be included under "Supporting organizations" as "Sponsor of 3.x stable release" for the Bibliography & Citation module.

If you have followed the directions on the sub-theme page, I would create an issue in issue queue:

https://www.drupal.org/project/issues/d8_blog_theme →

It's literally the second sentence:

The folder name is the machine name

Perhaps you can add a link to the module?

See https://www.drupal.org/docs/develop/theming-drupal/defining-a-theme-with... →

You probably need to use the machine name. I have updated the documentation to emphasize this. Perhaps you can verify if that solves it?

https://www.drupal.org/docs/develop/theming-drupal/defining-a-theme-with... →

Clarify that you should "Use the machine name of the base theme."

Thanks all! This is great, and will help many users install Drupal CMS much more easily.

Thanks for clarifying @phenaproxima.

I do think we should post somewhere (README? documentation page?) how to get Drupal CMS up and running, for developers and curious users, such as me and @spuky, even during this development phase. There are surely many others who also would like to give Drupal CMS a test spin.

Aside from experiencing Drupal CMS, they can also help catch regressions, such as #3470145: To respect user privacy and comply with GDPR, use openstreetmap.de for Leaflet maps → .

Thanks, I of course know this :-)

I just wonder why the admins don't block this user?

Great that it helped, and thanks for the update! I notice "Brwoser" in the new text (should be "browser"), maybe it can be fixed?

Hopefully someone else can review and change to RTBC, if they think it is.

I don't remember, sorry. I would open a new issue, if I were you, since many things might have changed.

It is fairly straightforward to create a sub-theme ... did you follow the steps in this guide?

https://www.drupal.org/docs/develop/theming-drupal/creating-sub-themes#s... →

Why do you post your name three times?

1. In the title
2. At the start of the question
3. At the end

We can already see it under "By darshanhiranandani23 on 27 Aug 2024 at 09:48 CEST"

marcus_johansson → credited ressa → .

I agree, a README file would be great, to help users try out Drupal CMS more easily. Here's a rough sketch, based on the Starshot README.

The composer quick-start command doesn't quite complete, and does not install Drupal. So until that's fixed, the user needs to manually install, so I have added those steps, as well as how to create a log in link.

I don't think the "Not using DDEV?"-installation method works any more, so I removed it.

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

I created the follow up issue #3470145: To respect user privacy and comply with GDPR, use openstreetmap.de for Leaflet maps → , since the changes here have already been committed.

ressa → created an issue.

It's great to see all the activity, though it looks like using openstreetmap.de as map (as opposed to openstreetmap.org and fastly.net) was lost in the process. It was added in this issue, to respect GDPR for European users:

To respect user privacy, use Geocoder & Leaflet on the event content type #125

... and was added in the update Use OSM DE:

- leaflet_map: 'OSM Mapnik'
+ leaflet_map: osm-de

The issue was originally created in the Olivero issue queue but moved, so it's not clear now that the issue is about a specific theme, so adding Olivero in title.

Perfect, thanks @xmacinfo. It would be awesome to get date formats standardized in Drupal.

The default date format were changed ...

@xmacinfo: I know, I am the one who created the issue and updated the code :-)

That change does not affect the date picker in the form, as far as I can tell it's non-configurable ...

Also, in my opinion, using letters for month in the date picker would be a bad idea, and another potentially confusing GUI design choice.

Like I wrote -- and you both seem to agree -- it would be preferable to use ISO 8601 YYYY-MM-DD format for use cases with compact and number-only options, such as the date picker.

The HTML Date format (from "Date and time formats" page) uses ISO 8601, in fact:

HTML Date 2024-08-21

Feel free to visit the issue I created, which proposes setting a Drupal date standard for "human readable"- and "number"-dates:

#3467914: Define a standard for Date formats →

If you both add your support to the proposal, we just need one more supporter to get ISO 8601 approved for "number"-dates (compact), and we could perhaps then do 📌 Use ISO 8601 format in Authored on field date picker Active , if you agree?

Setting the total hours as a variable, and then checking the value should work:

• https://twig.symfony.com/doc/3.x/tags/set.html
• https://twig.symfony.com/doc/3.x/tags/if.html

I recently created 📌 Use ISO 8601 format in Authored on field date picker Active , which may be a duplicate of this issue ... but if it's possible, perhaps it might be simpler to use ISO 8601 format for dates represented by numbers (i.e. YYYY-MM-DD) and hard code it that way, to make dates less ambiguous? Adding possibly relevant issues.

This is great, thanks! I recently proposed a date standard in #3467914: Define a standard for Date formats → and 📌 Use ISO 8601 format in Authored on field date picker Active after the human readable Drupal core date formats were updated in 📌 Use easily recognizable date format RTBC . Perhaps defining a standard could help this issue move forward?

Thanks! I do see an overlap between this issue and 🐛 Date picker only works with US date and time formats Active ...

But I propose a simpler solution here, simply using ISO 8601 format, with no configuration options.

Maybe that other issue stalled, because it was trying to do too much?

It sounds great that DDEV can eventually be added as well. Thanks for all the great work you are doing on getting the User Guide Drupal 11 ready!

Why are you adding your name in the title?

You could consider creating a DDEV issue?

https://github.com/ddev/ddev/issues/

I created an issue about adding DDEV.

ressa → created an issue.

I agree @eojthebrave, it makes sense to remove content about using .tar.gz files completely and focus on Composer only, since the option to install tarballs was removed in Drupal 10.4 and Drupal 11 via 📌 Remove adding an extension via a URL Fixed .

I was looking for the Drupal 10 User Guide in PDF format, and landed on this page, saw the heading and x.tgz-files, and was not sure if I needed to look elsewhere ... it wasn't until I diligently read the text on the page, that I realized that the x.tgz-files contain the PDF.

Maybe we can update the title to make it clearer which formats are included? E-book was probably used previously, since the file also contained azw3 and mobi formats, removed since Drupal 10.

That's great, thanks for confirming. Hopefully the patch can get included before too long, and help others with this challenge.

You need to use Composer: 📌 Remove adding an extension via a URL Fixed .

You should uninstall Composer from your host machine, together with PHP, and all other local dev environment program, and only use those from DDEV. Otherwise, you can get weird conflicts.

40 old posts flooded in today, filling up page 1 and 2.

Great that you got DDEV up and running. It's a very battle tested tool, and most tasks can be done with the basic set up -- like you write, the task is to find the documentation. Like with Drush, the fastest method is to just run ddev, find the command (import-db) and then add -h add the end, and all should be clear.

$ ddev import-db -h

@annmarysruthy: But that is this issue ...

The recommended Drupal dev tool is DDEV, perhaps try that? Running your own LAMP stack often leads to "strange issues", it's difficult to have different PHP-versions between projects, etc.

• ✨ Recommend DDEV as the default Drupal local development environment Active
• https://ddev.com/

I have created #3467914: Define a standard for Date formats → to get a Drupal Coding Standard.

@greggles:

Is there a reference page on drupal.org about formatting dates?

It doesn't look like there is, so I have created #3467914: Define a standard for Date formats → .

ressa → created an issue.

Thanks for the feedback @quietone, I removed mentions of standard in the text and moved the page to https://www.drupal.org/docs/develop/creating-modules/date-formats → .

Remove mentions of standard in the text, since it is not a standard, and move to Creating modules → .

Perfect, thanks for maintaining this wonderful module!

I created a follow up issue 📌 Use ISO 8601 format in Authored on field date picker Active .

ressa → created an issue.

A single item should not be a list.

Thanks everyone! It's impressive that this improvement went from idea to completion in less than a week, and already see it in effect in lists under "Content" and "Recent log messages", and node edit under "Last saved".

I agree, DDEV is an amazing tool, I am glad you also like it! And great that you found the error, feel free to add [Solved] first in the title.

I have created the documentation page Date formats under "Coding standards", since I couldn't find a page dedicated to this subject ...

Perhaps someone can review it, and add it to the menu, or place it somewhere else, if it doesn't belong in that section? Thanks!

Thanks for looking at this @catch and @Gábor Hojtsy.

I noticed that there is no comma in the recommended format on Wikipedia, and found few more sources with the same format. So I updated the MR, and removed the comma. I also updated the Olivero date format, which also had a few extra spaces.

Thank you @DYdave, it's great to hear! I try my best to help out where I can -- though I have to leave the hard core coding to the experts, such as yourself and @japerry 🙂

ressa → created an issue.

Adding "7th of August" in issue summary to clarify why "08/07/2024" can be opaque.

Yes @smustgrave, I realized that the right method was to update all the dates :-)

And by the way, let me just repeat that I am eternally grateful that you started and lead the Needs Review Queue Initiative → initiative. In my opinion, it's among the most important initiatives, together with Drupal Starshot.

Thanks for the feedback @xaa, I added the sentence.

Feel free to edit it, if it could be improved, or add a mention about @alpha, @beta, as you suggest, which would be a nice addition.

Thank you @japerry for updating the MR, and all the other recent work on the module, and thanks @DYdave for the update here, and all the other great work you have done getting Admin Toolbar Drupal 11 ready. I very much appreciate it!

About your suggestions, they are great and I agree with all of them, so feel free to go ahead. Maybe someone can add the test you suggest?

That's a great question. I think you should consider opening an issue, and request that the steps required for going from using the Book module as a Drupal core module to contrib module are documented, and added in the README and on a new documentation page.

• https://www.drupal.org/project/issues/book →
• https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →

These steps could also be added to the Statistics and Tour module, also removed from Drupal core in version 11.

• https://www.drupal.org/project/tour →
• https://www.drupal.org/project/statistics →

Occasionally, a maintainer will tag first version with zero as the first number, like 0.x. But it is so rarely done in Drupal, that perhaps we could consider adding a recommendation, like this to streamline the version numbering a bit?

While it is possible to use a zero as first number (for example 0.1.0) the convention is to start from 1, for example 1.0.0.

Actually, ISO 8601 doesn't cover month names (jan, feb, etc.) so this is issues aim to switch to a rapidly recognizable date format, the same as drupal.org issues uses:

Created: 7 Aug 2024 at 11:24 CEST

So updating the title.

I tried updating the date formats and tests, maybe some more tests need to be updated? Let's see!

And about this:

Is there a reference page on drupal.org about formatting dates?

I am not sure, but it would be great to have one, if only just stating that the date format in the ISO-8601 standard should be followed in Drupal.

Thanks for a fast and positive reply @greggles.

Some of Drupal's date formats were actually set to use the ISO-8601 standard in 2004 ( Drupal 4.5.0 → ) by Dries, but they must have been lost somewhere along the way ...

Maybe we should update Drupal core instead, and then perhaps it will also fix Security Review's date format? It looks like it might be using a Drupal core date format:

$ grep -iR "Review results from last run" .
./templates/run_and_review.html.twig:    Review results from last run {{ date }}

I have updated the Issue Summary, and moved it to Drupal core instead.

I hope you succeed! It may not fix it, but then it could be the DB export you need to look at? For example, I need to use phpMyAdmin for a web site I maintain to export the DB, and I need to enable this under "Export > Custom":

x Add DROP TABLE / VIEW / PROCEDURE / FUNCTION / EVENT / TRIGGER statement

Otherwise the import into DDEV fails, see https://civicrm.stackexchange.com/questions/15860.

I never experience any problems importing files and DB's from the server with DDEV. It is the officially recommended local development environment for Drupal, so perhaps try that? https://ddev.com/

Check the log under Reports > Latest log messages for details ( https://www.drupal.org/docs/user_guide/en/prevent-log.html → ) or with Drush via the command line:

$ drush watchdog-show

ressa → created an issue.

Got here after getting the error, and can confirm that going to "Security Review Settings" (/admin/config/security-review) and saving configuration fixed it. I didn't catch there was a patch which I could have tested, sorry.

Yes, thanks everyone for landing this feature with great tenacity. This is one of the things which makes so Drupal so great -- while an issue may take some time, many will eventually be resolved, and make Drupal even greater.

ressa → created an issue.

Thanks! @kopeboy is now credited for this contribution in this issue:

Credited on 40 fixed issues

• Drupal core, 4 issues
• Claro Compact, 1 issue
• [...]

https://www.drupal.org/u/kopeboy →

Those checkboxes, unless I'm mistaken, only work when accepting a PR, don't they?

No, they are in fact on an issue basis ... You could consider skimming the "Granting credit to issue contributors" page?

https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett... →

I feel no animosity at all, quite the opposite. I am very grateful that you created this project in the first place, it serves an important role for those of us who like a compact administration theme. And you should run this project how you see fit. All I am saying is that if the regular, boring processes were used, things would be more transparent, and some processes taken care of by the system, we as users can follow along in the changes and where they happened, and so on.

It's unfortunate that mass MR's ("credit gaming") resulted in automatic crediting for MR's and similar getting removed ... Anyway, all this will soon be history, when the Drupal issue system migrates to Gitlab, which has automatic crediting, and more elegant tools for project administration.

In the issue where I commented yesterday, you can see how I add a legend 💬 how to load faster or load a static image while loading map Active . In fact, all legends on arst.dk are inserted with that method, for example the latest for bird species per municipality: https://arst.dk/kort?data=fuglearter

As opposed to the solution suggested by @itamair, it's not dynamically created, but a manually defined SVG-image.

Another option would be to extract the values from the filter in the left side (under "FUGLEARTER"), and create it dynamically based on those values, but I just needed a quick solution, and it does the job.

ressa → created an issue.

Thanks everyone for making Claro Compact compact!

@djg_tram: Maintainers need to actively add credit to community members helping out in issues. This was previously done automatically. You can follow the "Granting credit to issue contributors" link under "Credit & committing" at the bottom of this page for details.

All you need to do is probably check the three "By" boxes under "Credit & committing" and click "Save", and the credit will be given to those, who made this improvement happen.

For example, as you can see under his profile https://www.drupal.org/u/kopeboy → , has not been given any Claro Compact credit.

As a user, it would have made the changes more transparent, if you had created a separate issue and MR for your improvements, and had simply committed this MR. But I can also see how this could seem like too much effort, for too little.

I put it into a JavaScript file in my theme. I don't know how to remove it, since I don't do that.

I also had a dataset with a lot of data points, which were better served as an image. So I created a PNG in QGIS and overlaid it on my map, as you can see here: https://arst.dk/luft

I inserted it with this JavaScript (there are two files here, also the legend in the upper right corner):

if (window.location.pathname == '/luft') {
  map.setView([56.2, 11.65], 8);
  var pm25Url = '/themes/custom/arst_2024/assets/pm25.png', imageBounds = [[54.443459480, 8.018099313], [57.761847116, 15.575382821]];
  var pm25RangeUrl = '/themes/custom/arst_2024/assets/pm25-range.png', imageBoundsRange = [[56.2, 12.6], [57.2, 13.5]];
  var imageOverlays = L.layerGroup();
  L.imageOverlay(pm25Url, imageBounds).setOpacity(0.6).addTo(imageOverlays);
  L.imageOverlay(pm25RangeUrl, imageBoundsRange).setOpacity(1.0).addTo(imageOverlays);
  imageOverlays.addTo(map);
}

Add link to Node.js install page, since this is a requirement.

Thanks for looking at this @Anybody and @klidifia for updating the patch. It's a great idea to add Token support for even more flexibility -- maybe @klidifia is able to add this feature?

2. Your feed must have at least two posts already so we can evaluate the content and make sure it is appropriate for the Planet.

There are now two great and relevant Drupal articles, so this requirement has been met.

This will be a great addition to Planet Drupal, and I am looking forward to see your articles there @darvanen!

Just adding a note, that removing [current-page:title] | [site:name] under "Global" (/admin/config/search/metatag/global) and leaving it empty, allowed a custom Views title from a hook_views_pre_render function to get used instead.

Yes, that would be the right strategy. I did a quick search in Change Records and didn't find anything, but it may not qualify as that ...

It would also be nice if someone can verify if the stated situation for Drupal 10.2 / 10.3 / 11 in the Issue Summary is correct.