🇩🇰Denmark @ressa

I am also seeing this:

Error message: User warning: Trying to overwrite a cache redirect with one that has nothing in common, old one at address "languages:language_interface, theme, user.permissions" was pointing to "url.path.parent, url.path.is_front, route", new one points to "url". in Drupal\Core\Cache\VariationCache->set() (line 138 of core/lib/Drupal/Core/Cache/VariationCache.php).

... randomly in a fresh Drupal 10.4 install for CiviCRM.

$ drush pm:list --no-core
 ---------------- ----------------------------------------------------------------------- ---------- ------------- 
  Package          Name                                                                    Status     Version      
 ---------------- ----------------------------------------------------------------------- ---------- ------------- 
  Administration   Admin Toolbar (admin_toolbar)                                           Enabled    3.5.1        
  Administration   Admin Toolbar Links Access Filter (admin_toolbar_links_access_filter)   Disabled   3.5.1        
  Administration   Admin Toolbar Search (admin_toolbar_search)                             Disabled   3.5.1        
  Administration   Admin Toolbar Extra Tools (admin_toolbar_tools)                         Disabled   3.5.1        
  CiviCRM          CiviCRM Core (civicrm)                                                  Enabled                 
  CiviCRM          CiviCRM Theme (civicrmtheme)                                            Enabled                 
  CiviCRM          CiviCRM Entity (civicrm_entity)                                         Enabled    4.0.0-beta4  
  Core             Claro Compact (claro_compact)                                           Enabled    8.x-2.1      
 ---------------- ----------------------------------------------------------------------- ---------- ------------- 

Thanks for giving Views Data Export a spring (or Winter!) cleaning @steven jones, and getting it ready for new Drupal, and even blogging about it. I agree about letting the D7 issues go, it is the correct decision.

I very much look forward to using the module in future projects!

ressa → created an issue.

You're welcome :)

This is just an observation, which shouldn't stop the feed from getting added. But as a Planet Drupal reader, it will be confusing to see a new DXPR article, but the same image again ("Didn't I see this one already?") ...

So maybe update the articles, to not use the same header image in all blog posts? It would also improve the https://dxpr.com/blog page, and make it easier to discern between the articles. Have a nice day!

Update title and summary.

Thanks for the application @jurriaanroelofs, it looks great, there are six recent articles all about Drupal since 18 Oct 2024, and the feed can be added to Planet Drupal.

Thanks! You're probably right that the change happened somewhere between version 2 and 3. And since it's a contrib module, that would explain there's no change record.

Thanks for sharing the changes, I think I found them:

• type: sequence >> type: ignore:
  https://git.drupalcode.org/project/migrate_source_csv/-/commit/7a49df289...
• Fields with out numbering:
  https://git.drupalcode.org/project/migrate_source_csv/-/commit/2036524e0...

I am adding a link to them test yml file, since it looks quite different to the example here in the docs.

I created https://www.drupal.org/docs/extending-drupal/module-shortcuts → , perhaps it can be added to the menu?

@rkoller: I created a Drupal documentation page for contrib module shortcuts under https://www.drupal.org/docs/extending-drupal/module-shortcuts → .

Add links to relevant code.

Update Admin Toolbar link

Add "Action" column.

ressa → created an issue.

ressa → created an issue.

Thanks @siramsay and @quietone for feedback and update. I'll add the consensus reached in the Issue Summary.

Perhaps https://www.drupal.org/project/eca → can do this?

Align header levels.

And the spam continues. Admin?

Thanks @jacobupal, that's so much easier. Do you know when this improvement happened? I tried looking for a change record for Migrate, but didn't find anything ...

Thanks for migrating documentation pages for modules @quietone.

@anybody, it looks like these pages are for Drupal 7? If you want, I could move them under a "Drupal 7" page, to make it clearer what they are for?

I still think this is relevant ... I looked at the documentation https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... → , but it says it is for the old version ("This page and its children are for old releases of the Custom Tokens module. See #2912199: Documentation").

Also, there isn't much in the README file ...

It would be great with a very simple example in the README or in a doc page, which shows what makes this module great, and how to set it up. Thanks!

As a side effect of 📌 Evaluate the whole idea of the Evaluator guide Active I tried the Quick Start command today, and it doesn't seem to hang any more, it just works. So I am closing the issue, but feel free to re-open, if you can reproduce the problem :)

I used DDEV with this method to check:

git clone https://git.drupalcode.org/project/drupal.git qs && cd qs
ddev config --project-type php
ddev start
ddev composer install
ddev php -d memory_limit=256M core/scripts/drupal quick-start demo_umami

It was ready here: https://qs.ddev.site/

Thanks for fast feedback @apaderno, it's great. And you know what, it actually looks like Drupal Quick Start command doesn't hang any longer ... It worked for several minutes. I went away and resumed, and everything seems to work well still, which is fantastic.

I used these commands:

git clone https://git.drupalcode.org/project/drupal.git qs && cd qs
ddev config --project-type php
ddev start
ddev composer install
ddev php -d memory_limit=256M core/scripts/drupal quick-start demo_umami

It was ready here: https://qs.ddev.site/

So I have added Drupal Quick Start to the Evaluator guide, at the last position. When the Drupal CMS online trial experience is launched, we can move it to the top, so the order is this?

1. Drupal CMS
2. Simplytest.me
3. Drupal core with DDEV
4. Drupal Quick Start

Getting the right PHP environment set up for the Quick Start command is also difficult, as is installing DDEV ... or should this eventually be the order -- or maybe not until the "Check for required PHP packages"-script is ready?

1. Drupal CMS
2. Simplytest.me
3. Drupal Quick Start
4. Drupal core with DDEV

Adding Quick Start command, since it doesn't seem to freeze anymore.

Restore simplytest.me to its original position, since it's only the "One Click Demos" that don't work.

Fix typo, and update the Summary.

Thanks @avpaderno. We can all get it up and running. The problem some of us see, is that it stops responding, after using it for some time.

I have added Simplytest.me as the first option on the Evaluator guide, since as you wrote, the Drupal core option works well.

Improve intro.

Add Simplytest.me as first option, specifying to use Drupal core.

Thanks @avpaderno. I should have made it clearer that I am referring to the Starshot and umami "One Click Demos", which I'll add in my comment above.

Placing Drupal CMS as first option, and adding DDEV as the second option.

@quietone, I agree with your list of descending technical user requirements, if only the tools worked ...

Simplytest.me is broken

Like I commented in #6 📌 Evaluate the whole idea of the Evaluator guide Active , Simplytest.me does not work, who knows for how long? So we shouldn't send new users there, see 🐛 quick-start installation stops responding Active .

Drupal Quick-start freezes

Like I also commented in #6, for you, me and others, Quick-start freezes after a minute, 🐛 quick-start installation stops responding Active .
@catch, @hansfn, and @avpadernod, does it work for you?

Drupal CMS is supposed to launch an online trial experience in a month, at January 15 2025, so that will be lowest barrier to entry, and we can add that to the evaluator guide, as the recommended method?

1. Easiest
   Drupal CMS online trial experience, launches January 15 2025
2. Needs CLI skill
   DDEV and a link to https://www.drupal.org/docs/getting-started/installing-drupal/install-dr... →

I am not sure that this page needs any sentences about the developer sections of the docs. For me, that is separate and besides that is in the block.

I would remove all the note-tips because three on a small page is overwhelming. And for me, that is distracting.

Great suggestion, I removed the tips, and rewrote the intro text.

Simplify instructions, removing three tips, see #3399873-12: Evaluate the whole idea of the Evaluator guide → .

Thanks for reviving this issue @quietone.

The agreement here by the users involved in documenting Drupal is to use just drush, so it seems like there is only one remaining task, which is to update the page https://www.drupal.org/docs/updating-drupal/updating-modules-and-themes-... → which is still using vendor/bin/drush.

Or what do you think, to settle this: vendor/bin/drush or drush? :)

Perfect! Thanks @poker10 and all the other D7 maintainers for keeping Drupal 7 updated, and expanding it with new features, like PHP 8.3 compatibility.

Speaking of .gitignore, there's also ✨ Add gitignore(s) to Composer-ready project templates Needs work , but maybe that would be too much change, to add to Drupal CMS at this point?

I have also recently not been able to get Simplytest to work ...

I wonder if it has not been working almost two months, since 18 October and until today 14 December?

Since not working is actually Critical ("Render a site unusable and have no workaround"), I'll update the Status.

Removing .gitignore lines, since the Git section should not be aimed at setting up Drupal for development, but mainly another way of installing Drupal. I linked to the  Setting up an environment to test Drupal patches and merge requests → page, for those who need more advanced tips for Drupal core development.

Separate out the final steps under "Using a local development environment", since both DDEV and a custom dev environment need to get a functioning .gitignore file, and follow the rest of the instructions.

Also, more often than not, when I try Simplytest.me it crashes ... So I have moved it to the bottom of the page and adding a note that it seems to not work. Note: I have previously created issues when I saw this.

The forums are still needed for technical support, and whereas Slack may serve fine as a chat, its walled garden nature and closed source/proprietary aspect, loss of community ownership of content, and requirement for a separate account not tied to Drupal.org are real obstacles.

Slack isn't designed for accumulating knowledge, making it difficult to find specific information from weeks prior, and doesn't get indexed by the search engines.

But we are preaching to the choir here... se 🐛 Feedback on Modern Drupal.org Design Active .

Recently, it seems like the Global Drush 8 is called, even when using vendor/bin/drush in a Drupal 10 site with Drush 13. The command hangs for more than 2 minutes, before completing. Or maybe something else is causing this?

See Document that global Drush 8 can detect Drush 12 in a local Drupal 10 installation #5741.

I agree, and other users mentioned the same thing in 🐛 Feedback on Modern Drupal.org Design Active .

Add Antibot.

Thanks!

It says on PHP requirements for Drupal 7 → that PHP 8.3 is supported "Yes, as of Drupal 7.103", so perhaps this issue could be included on the release page for Drupal 7.103 → ?

It looks like posts marked marked by us users as spam are not included in the "New forum topics" block, is that true?

If so, that would be a great little improvement, to at least hide spam posts from the entrance under https://www.drupal.org/forum → :)

This is essentially a rewrite of an old post from 21 dec 2023:

How to get started with Composer? Am I on the right track?

By robbnl → on 21 Dec 2023 at 13:52 CET

Hello, For many years I have managed a few Drupal sites from the UI backend. I would like to update my skills and also follow the software development and would like to start extending my Drupal installation through Composer because I see that is the prefered method to install modules.

My hosting provider allows me to deploy a new site with Installatron. That's really convenient because it installs a new site with Drupal, creating the database and such automatically.

However as soon as I install a module through composer (for example webforms) then immediately I loose access to my admin webpages. The newly installed site's main page remains working. Just when I try to access the admin backend I get an error message:  the website encountered an unexpected error. please try again later

My question now is: am I on the right track? I have read that when you manage modules and dependencies through composer you should not install modules manually through the UI. But on a fresh install?

I also do believe that the Installatron mechanism uses composer because I see a composer.json in the site's directory.

Any guidance on wether I am on the right track or should go down a different road would be much appreciated

With friendly greetings,
Rob Bastiaansen

From https://www.drupal.org/forum/support/installing-drupal/2023-12-21/how-to... →

This post:

Darshan Hiranandani : How do I begin working with Composer? I’m not sure if I’m approaching it correctly—any advice?

By darshanhiranandani24 → on 12 Dec 2024 at 10:30 CET

Hi everyone,

I’m Darshan Hiranandani, I've been managing a few Drupal sites from the UI backend for several years, and I want to update my skills by extending my Drupal installations through Composer, as I see it’s the preferred method for installing modules.

My hosting provider uses Installatron, which automatically installs Drupal and creates the database for me, which is very convenient. However, when I install a module (e.g., Webforms) via Composer, I immediately lose access to my admin pages. The main page of the site remains functional, but I get an error when trying to access the backend: 'The website encountered an unexpected error. Please try again later.'

I’ve read that managing modules through Composer means I shouldn’t install them manually via the UI, but I’m wondering if this rule applies on a fresh installation as well. I also noticed that Installatron seems to use Composer since I see a composer.json file in the site’s directory.

Am I on the right track with using Composer for module management? Or is there a different approach I should follow?

Any guidance or suggestions would be greatly appreciated!

Regards

Darshan Hiranandani

I didn't check out CCPA before, so thanks for sharing @jurgenhaas. Great that there are consumer protecting initiatives world wide.

I acknowledge that my approach has been EU/GDPR-centric, but in light of the different requirements from region to region, adding https://www.drupal.org/project/leaflet_more_maps → could make sense, since US-based web sites can then select to use US-served openstreetmap.org/fastly.net tiles, while EU-sites can choose to use tiles served from openstreetmap.de in Germany. Even more geographically diverse based tile servers can be added along the way.

This would remove the need for a consent form for Leaflet maps, if I am not mistaken, and a better user experience.

Thanks @spiderman, sounds good, and I do understand -- there is only so much time, and we all got to pay the bills :)

It's true that fastly.net can use servers from all over the world, USA-located servers were used, when I visited https://www.openstreetmap.org/ and checked with https://www.nslookup.io/

openstreetmap.org

IP address		Type	Hosted by	Location
104.21.88.66		IPv4	Cloudflare, Inc.	United States of America
172.67.173.161		IPv4	Cloudflare, Inc.	United States of America
2606:4700:3034::6815:5842	IPv6	Cloudflare, Inc.	United States of America
2606:4700:3030::ac43:ada1	IPv6	Cloudflare, Inc.	United States of America

https://www.nslookup.io/domains/openstreetmap.org/webservers/

fastly.net

IP address		Type	Hosted by	Location
151.101.1.6		IPv4	Fastly, Inc.	United States of America
151.101.65.6		IPv4	Fastly, Inc.	United States of America
151.101.129.6		IPv4	Fastly, Inc.	United States of America
151.101.193.6		IPv4	Fastly, Inc.	United States of America
2a04:4e42::262		IPv6	Fastly, Inc.	United States of America
2a04:4e42:200::262	IPv6	Fastly, Inc.	United States of America
2a04:4e42:400::262	IPv6	Fastly, Inc.	United States of America
2a04:4e42:600::262	IPv6	Fastly, Inc.	United States of America

https://www.nslookup.io/domains/fastly.net/webservers/

dualstack.n.sni.global.fastly.net

IP address		Type	Hosted by	Location
151.101.193.91		IPv4	Fastly, Inc.	United States of America
151.101.65.91		IPv4	Fastly, Inc.	United States of America
151.101.129.91		IPv4	Fastly, Inc.	United States of America
151.101.1.91		IPv4	Fastly, Inc.	United States of America
2a04:4e42:400::347	IPv6	Fastly, Inc.	United States of America
2a04:4e42:200::347	IPv6	Fastly, Inc.	United States of America
2a04:4e42:600::347	IPv6	Fastly, Inc.	United States of America
2a04:4e42::347		IPv6	Fastly, Inc.	United States of America

https://www.nslookup.io/domains/dualstack.n.sni.global.fastly.net/webser...

openstreetmap.de

IP address		Type	Hosted by		Location
138.201.247.34		IPv4	Hetzner Online GmbH	Germany
2a01:4f8:c17:ead7::1	IPv6	Hetzner Online GmbH	Germany

https://www.nslookup.io/domains/openstreetmap.de/webservers/

Adding https://techgdpr.com/blog/server-location-gdpr/ in Issue Summary, thanks @poker10 for sharing that link.

Thanks for fast replies from everyone. To respect user privacy, usage of external resources should be avoided or kept at a minimum, to avoid "Accept third-party" pop-ups as much as possible.

Drupal CMS should be as GDPR compliant by default as possible, and if openstreetmap.de tiles were used, EU-users would not need to consent to using a third-party service, as I understand it.

So I do think serving tiles from openstreetmap.de (Germany) would be better, than via openstreetmap.org+fastly.net (USA/Canada).

I updated the page, so changing Status to "Needs review" here and there.

Remove the manual steps, and just link to the Try Drupal CMS page or point the user to DDEV, see 📌 Evaluate the whole idea of the Evaluator guide Active .

Cool, thanks for sharing your solution and setting the post to Solved!

Sure, then let's point it to the Drupal CMS RC page, replacing everything below "Requirements" on the Evaluator guide → :

Try Drupal

Try Drupal CMS, or install Drupal locally with DDEV.

Thanks for creating the page @quietone, it will be a great resource for new Drupal users, going forward.

A little more than a month to launch, perhaps this can get looked at?

I agree on all counts @hansfn, I also think it was too difficult for an evaluator, not only on Windows, but also MacOS and Linux.

• Installing DDEV: Requires too many steps
• Manual PHP: Getting the right PHP packages is difficult
• Legacy PHP tools: XAMPP doesn't work out of the box
• Quick Start: Freezes 🐛 quick-start installation stops responding Active after a while for some users ... (maybe everyone?)
• Simplytest: Used to be great, but got unstable after the creator Patrick D left ... It may have been working well for a period? But I tried it right now, and it crashed, with "There was a build error -- This may be the error:"
  It's too bad that Simplytest don't have tests, to catch these recurring errors ... It looks like they have two sponsors, so in theory there is funding ... but maybe not enough?

I'm starting to think that the "quick-start" approach is only useful for people that already have a decent PHP setup.

I think we are "between chairs" here, since who is this evaluator page supposed to be for? For example, is it a CEO or non-developer person responsible for choosing the next CMS, not necessarily technically skilled, but happens to run a perfectly optimized PHP set up on their machine, with MySQL? This is like finding a unicorn, in my opinion.

Seasoned developers who writes Docker scripts in their sleep can get DDEV up and running easily. Also, who sets up manually a perfectly optimized PHP set up on their machine these days, and MySQL? Not the head of a small or medium sized company, who's not a developer. This person just needs to click somewhere in the browser, and then get Drupal, and check it out.

Since Drupal CMS will be launched January 15 2025 with an online trial experience, it can be used for evaluation. So maybe this issue can be set to postponed, and then January 15 2025, everything below "Requirements" on the https://www.drupal.org/docs/official_docs/evaluator-guide → can be replaced with a link to the Drupal CMS online trial experience?

Try Drupal

Try Drupal CMS in the browser, or install it locally with DDEV.

Just as long as the Drupal CMS online trial doesn't require registration, paying with credit card, etc. ... :)

Thanks @robloach, I still get an error, like @apaderno:

https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.kalamuna.c...

It looks like this is a web page, not a feed. I looked for a feed associated with this page, but couldn't find one. Please enter the address of your feed to validate.

Also, there is only a single recent article:

• <pubDate>Thu, 03 Oct 2024 20:54:16 -0400</pubDate>
• <pubDate>Wed, 29 May 2024 11:13:21 -0400</pubDate>
• <pubDate>Tue, 14 May 2024 14:25:22 -0400</pubDate>
• <pubDate>Tue, 30 Apr 2024 14:56:39 -0400</pubDate>

ressa → created an issue.

I agree, this definitely deserves to get highlighted in the Drupal 11.2 release, big thanks to everyone here who made it happen!

I tried with ~60 modules, and the module install time went down from around 24 seconds to just 10 seconds.

Drupal 11.1 vs. Drupal 11.2

For anyone who wants to try it, this gets a Drupal 11.2 installation ready for bench marking with ~60 modules:

# set it up to ignore all constraints
$ ddev composer require drush/drush drupal/backward_compatibility mglaman/composer-drupal-lenient
$ ddev composer config --json extra.drupal-lenient.allow-all true
$ ddev composer config --json minimum-stability false
$ ddev drush site:install -y
$ ddev drush install backward_compatibility

# get modules
$ ddev composer require drupal/address drupal/admin_toolbar drupal/antibot drupal/backup_migrate drupal/better_exposed_filters drupal/blazy drupal/block_class drupal/captcha drupal/colorbox drupal/config_filter drupal/config_ignore drupal/config_split drupal/crop drupal/csv_serialization drupal/devel drupal/diff drupal/ds drupal/easy_breadcrumb drupal/editor_advanced_link drupal/eu_cookie_compliance drupal/externalauth drupal/extlink drupal/feeds drupal/field_group drupal/field_permissions drupal/focal_point drupal/fontawesome drupal/geofield drupal/google_analytics drupal/google_tag drupal/honeypot drupal/image_widget_crop drupal/menu_block drupal/menu_link_attributes drupal/metatag drupal/migrate_tools drupal/mimemail drupal/module_filter drupal/pathauto drupal/rdf drupal/recaptcha drupal/redirect drupal/rules drupal/scheduler drupal/search_api drupal/seckit drupal/simple_sitemap drupal/slick drupal/smtp drupal/svg_image drupal/token drupal/twig_tweak drupal/video_embed_field drupal/views_bulk_operations drupal/views_data_export drupal/views_infinite_scroll drupal/views_slideshow drupal/webform drupal/xmlsitemap

# install modules, and time it
$ time ddev drush install -y address admin_toolbar antibot backup_migrate better_exposed_filters blazy block_class captcha colorbox config_filter config_ignore config_split crop csv_serialization devel diff ds easy_breadcrumb editor_advanced_link eu_cookie_compliance externalauth extlink feeds field_group field_permissions focal_point fontawesome geofield google_analytics google_tag honeypot image_widget_crop menu_block menu_link_attributes metatag migrate_tools mimemail module_filter pathauto rdf recaptcha redirect rules scheduler search_api seckit simple_sitemap slick smtp svg_image token twig_tweak video_embed_field views_bulk_operations views_data_export views_infinite_scroll views_slideshow webform xmlsitemap

Second attempt.

Fix missing line breaks

Let's format the lists as lists. Also, there's no need to define docroot, if it's the current:

$ ddev config -h | grep docroot
--docroot string   Provide the relative docroot of the project, like 'docroot' or 'htdocs' or 'web', defaults to empty, the current directory

This account has been spamming the forum for five days now ...

Thanks @rroose, about .gitignore, see also ✨ Add gitignore(s) to Composer-ready project templates Needs work . Wouldn't it be great if Drupal 12 came with a default .gitignore file?

Thanks @prem suthar, looks good.

Since 2.x is the target version for new code, perhaps it should be made the default version on Gitlab? Currently, it's 1.x:

• https://git.drupalcode.org/project/matomo/
• https://git.drupalcode.org/project/matomo/-/tree/2.0.x?ref_type=heads

All right, since it can't harm, I think we should just set both to -10 and 10. There's no reason to limit the users.

Thanks! Maybe you can set the comments to "resolved"?

I am not sure if -10 makes sense. But I don't see any harm in allowing it, in case someone want to use it at some point ... why limit the users?

Great, good luck with your project.

Those are great changes, but out of curiosity, did you try with absolute paths, like /home/public/www.example.com? If that works, it might make it clearer what's going on ...

But isn't https://www.drupal.org/docs/develop/using-composer/manage-dependencies#s... → fine as it is? Or what do you think needs to be added?

Adding all module files.

Moving to Migrate Plus, in case it might be solved here, perhaps with a plugin?

Thanks for this suggestion, I left two comments in the MR.

Thanks again for great feedback, I have added your mode proposal to the Issue Summary.

About recursion, I think maybe that's better addressed in another issue? Maybe you could create a Token issue dedicated to idea, if it doesn't already exist?

Thanks for the feedback @apmsooner, I really appreciate it.

1. About width, I envision it to automatically expand to the width of the screen. I'll add that in the Issue Summary. You're correct that edge cases could appear, where the structure of the fields might limit the max. width, like with paragraphs ...
2. The position could interfere with help text, and using something like a contextual link might be the solution. Or perhaps simply position the link right after the field? I'll add that as alternate position.
3. I think the modal feels dated, and I always need to expand and resize it, hope I clicked the right field first, check if the token got entered, etc. Also, for new users, it may take some time to understand how it works.

So, I tried and failed to switch to the new 2.x branch ... Someone needs to fix this via the command line, or we should create a new issue from 2.x:

Creating issue forks > Pulling in new branches from an issue fork's parent →

Thanks @akalam, but maybe you can update the existing MR? You may need to click Get push access → first.

It looks like Legacy will be removed soon ( 📌 Remove drupal/legacy-project as a starting point for Drupal 10 Postponed ), so hosting which supports the drupal/recommended-project template is probably the best strategy.

I added that issue to the  https://www.drupal.org/docs/develop/using-composer/starting-a-site-using... → doc page.

Tarballs are also going away: 🌱 [meta] Deprecate tarballs, because they are incompatible with Composer-managed dependencies, Automatic Updates, Project Browser, and release managers' health Active .

Adding link to 📌 Remove drupal/legacy-project as a starting point for Drupal 10 Postponed under "drupal/legacy-project" section.

@apmsooner I got great feedback from @rkoller in 📌 Token browser as expandable form, replacing modal Active , and I updated my proposal based on that. If you have time, feel free to check out the issue.

[...] one problem, with the token browser being in a modal you have the problem that the field the token is pasted into is the last clicked field

That's true, I forgot about that.

What if all Token-supported fields had their own innocuous, right-aligned "Token browser" link? That way, it will be available, non-obtrusive, and the system will always know where to insert the token.

When a user clicks the "Token browser" link, the Token tree is shown, and the user can expand and collapse it. When a token item is clicked, it is entered into the corresponding field. (I had to hit Tab in my crude prototype screencast, to focus in the field)

1. A field with the Token browser link

2. The Token browser expanded

3. The field is populated after clicking a Token

MP4 file: Token.browser-each-field-expandable.mp4 →

I am attaching the crude HTML and CSS, in case anyone else want to experiment with it as well, see "4-Token.browser-each-field-expandable-HTML-CSS.txt". Simply copy paste it into the browser.

PS. Another thought: An autocomplete option would be nice, so that the user can type "date", and then [node:date-created], [node:date-updated], etc. are presented as options, but maybe that's not possible, or discussed elsewhere?

Thanks for checking, it sounds great that Alt + A doesn't seem to be taken. And the rest of your answers make a lot of sense, so thanks for clarifying and expanding.

yep wouldnt hurt to have such an overview. the only question where to place it in the documention so people actually find it :D

Yea, that's always a challenge :)

Making a relocated web root work on shared hosting can be difficult, since, you are sometimes not allowed to set the DocumentRoot, either via configuration or the GUI ...

But there are reasonably priced web hotels which support SSH access and some of them also symlinks. It's a little bit complicated to set up, and I tried to document it here: https://www.drupal.org/docs/getting-started/system-requirements/relocate... →

More spam.

Sounds great @w01f, you and @anybody should feel free to expand the list with more items :)

@catch: Things would have been easier now if we'd done that at the time instead of won't fixing it

How is it the saying goes ... "hindsight is 20/20"? So many things could or should have been ... I am just grateful that Drupal exists in the first place, and that there are all these amazing, gifted people such as you, @dww, and @andypost working towards a common goal of making a great CMS. Which we are winning, by the way :) I'll add the issue as related, to connect them.

Thanks for sharing your solution @ladytekla, this could very well help someone else looking for a solution for that scenario. Feel free to add [Solved] first in the title, like here → .

Could it be issue #2352637: Remove the UI for installing/updating modules from update module if it is not fixed in time for release → ?