🇬🇧United Kingdom @dunx

dunx → created an issue.

Understood. It is getting increasingly difficult to know where to target issues. I'm looking at Drupal CMS to try and suggest improvements to that as a product, but it's a bit of a Frankenstein's Monster, with parts taken from all over.

I know Adam has already referenced :) but I raised this a week later with some suggested changes.
https://www.drupal.org/project/drupal_cms/issues/3508207 🐛 Updates and Update Extension tabs don't belong under Appearance Active
Exactly the same observations, but with my "I am a new marketer using Drupal CMS for the first time" hat on.

phenaproxima → credited dunx → .

dunx → created an issue.

dunx → created an issue.

I've never used Wordpress, but did come across this video linked from another article, that gives an ex-Drupal-and-now-Wordpress-developer's opinions on Drupal CMS. I found it quite interesting how much they seemed to like the new Drupal CMS interface. Some of the comments are also informative.

https://www.youtube.com/watch?v=NipyycdGPvw

dunx → created an issue.

dunx → created an issue.

Even AWS Lightsail is talking about Drupal 7 and 8 installation via Bitnami :|

https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-...
https://docs.bitnami.com/aws/apps/drupal/configuration/install-plugins/

If Drupal CMS is going to succeed, it needs to be as easily installed as Wordpress on "cheap" hosting.

This feels like a major blocker to uptake for me right now. Sure, I could probably get it working somewhere cheap as others already have, but we're Drupal experts. What about these marketers we're talking about?

I appreciate I'm not offering answers or solutions.

Can we get this merged?

You don't even need ddev config --project-type=drupal11 --docroot=web because ddev config --project-type=drupal --docroot=web will work as ddev recently changed the drupal alias from drupal10 to drupal11. We are assuming some ddev defaults here that ddev might change. I don't know what oversight or warning we might get of those.

I think --create-docroot is also now a default and I don't think it was before.

Related to https://www.drupal.org/project/drupal_cms/issues/3500075 📌 Test (and then possibly document) installing on shared hosting Active , but what about PHP version? A shared hosting provider might only offer PHP8.3 and Drupal Core 11.1 supports PHP8.4. What happens when PHP8.3 is no longer supported (by Drupal or PHP).

No action required, just a reminder that what works now might easily change. I'm not suggesting we re-enable that installation script, but a more intelligent installation script might be exactly what we need in the future to help more people install Drupal CMS more easily.

pameeela → credited dunx → .

A bit of feedback related to my secondary minor issue with the commands. The script I'd created to spin up Drupal CMS dev version was running composer require cweagans/composer-patches because usually I'm applying patches to test under the issue queue.

That was causing the Recipes browser to show a "View Commands" button rather than an "Install" button. If you click on a "View Commands" button, close the modal to see the Recipe browser and scroll back to the top, you'll see an error message displayed:

Unable to download modules via the UI: Problems detected related to the Composer plugin cweagans/composer-patches. The composer-exit-on-patch-failure key is not set to true in the extra section of composer.json.

If you add that config to the composer.json extra stanza, then "View Commands" is replaced by "Install". The same occurs if you don't require composer-patches in the first place too of course.

I was hoping that was why I wasn't seeing the other Recipes within the Installer, but no joy. However, it's now possible for me to install Recipes via the browser, so if the decision to remove them from the Installer was intentional, I'm more than happy for this to be closed as Working as intended and hope the above is useful to the next person. The change threw me that's all.

Thanks :)

dunx → created an issue.

Yes to the ideal world of @chrisatredfin :)

Do the Drupal Association have any bandwidth to speak to the any of the big cheap hosting providers to help us help them?

Many of them already say they can host Drupal, whilst still using the old Drupal 8 logo for example. Perhaps it's in their interest to be more proactive in this respect. They would also be doing some marketing for Drupal CMS in getting their solutions out in front of their massive user base

dunx → created an issue.

I'm seeing the same as you @pameeela. Four focusable elements when tabbing through:

1. Skip to content
2. Email field
3. Password field
4. Finish button

But... there is a visually hidden "Regional settings" between the password and button. This is on -dev. I don't know under what circumstances these are supposed to display and I know the language selection stuff has been removed. Again, I don't have context on that.

I'm using Chrome on Mac and that's not focusable for me, so perhaps a browser issue and we suspect rkoller was using Windows due to mention of High Contrast Mode is the parent ticket.

I raised this from somebody else's larger issue. Can anybody provide screenshots from Windows High Contrast Mode for this issue?

Sorry, I'm on a mac, so can't use Windows High Contrast Mode. Hopefully, some kind soul can provide some screenshots.

Great topic.

The three hosting providers being recommended by Drupal at https://new.drupal.org/drupal-cms/trial under the Ready to launch? Find a Drupal host heading (Acquia, Pantheon and Platform.sh) are very unlikely to be the sort of service that somebody who wants to knock up a quick website can afford. I know there's some free/time-limited options, but these are typically £$€100s per month, when users are probably looking for that per year. We risk putting new users off immediately and losing them very quickly and forever if they believe those are the necessary or typical costs for hosting Drupal CMS.

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

I've created 6 child issues with this as parent.

Point 1 https://www.drupal.org/project/drupal_cms/issues/3500930 🐛 Improve a11y of Drupal CMS installer - recipe checkbox contrats Active
Points 2 and 6 not raised as language selection no longer present.
Point 3 https://www.drupal.org/project/drupal_cms/issues/3500931 🐛 Improve a11y of Drupal CMS installer - focus clarity Active
Points 4 and 9 https://www.drupal.org/project/drupal_cms/issues/3500932 🐛 Improve a11y of Drupal CMS installer - missing focus Active
Point 5 https://www.drupal.org/project/drupal_cms/issues/3500935 🐛 Improve a11y of Drupal CMS installer - missing icons in high contrast Active
Point 7 https://www.drupal.org/project/drupal_cms/issues/3500933 🐛 Improve a11y of Drupal CMS installer - low contrast on buttons Active
Point 8 https://www.drupal.org/project/drupal_cms/issues/3500934 🐛 Improve a11y of Drupal CMS installer - buttons with poor focus Active

Hopefully I've included all the required info. I re-used the same images and alt text ;)

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

Steps to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Skipped majority of config (no option to install SEO Recipe anyway).

Applied SEO tools recipe:

• This wasn't presented as an option on installation for dev, which confused me and it took a while (far too long in fact as the "commands" shown didn't work not matter what paths I was using under ddev) to figure out how to install it using the drupal script.
• I installed drush and from web, ran ddev drush recipe ../recipes/drupal_cms_seo_tools -v

View page source:

• Plenty of og and twitter tags present so recipe is installed.
• Both og:description and twitter:description are missing, presumably because they have null values before the patch.

Removed container, to start again, so repeated all of the above with the above recipe patched before I installed it.

View page source:

• Both og:description and twitter:description now have the vale "This is the home page of your new site. Start by editing this page, or creating new pages.".

All looks good to me.

For us Euro lot, it meant we were in a loop until the launch in the evening for us. Nice to see you launch it live though :)

"d.o" as in via the website if you'd come in via the press release. Was temporary and all resolved now of course.

@mrdalesmith that's a different issue on the page before you reach this one. I tested and made comments on that yesterday. This issue is not resolved by that solution. This issue should be re-opened.

Could easily become the longest issue queue ever ;)

I think getting the EOOTB/no/low-code tag in there would be beneficial. So here's mine...

Drupal Core pre-configured with best-in-class enterprise-grade solutions and smart defaults. Ready for content creators, designers, and marketers to build sites easily via a no-code AI-powered interface.

I can't see any changes in your fork, so I've not been able to install and test this. I'd very much like to see the Access Denied error resolved.

I've made some text change suggestions on that other issue 📌 Make selection of AI Provider clearer on module homepage Active , which just adds a new Warning message and doesn't address the Access Denied error.

If those suggestions are picked up, then perhaps your new message could read:

There are no AI providers available. Choose at least one AI provider module from those listed on the AI module homepage, add to your project, install and configure it here. Then update the AI Settings.

With links to:

1. "AI module homepage" to https://www.drupal.org/project/ai →
2. "AI Settings" to /admin/config/ai/settings

Steps to reproduce...

1. Install latest D11 Umami plus drush
2. Download admin_toolbar and key modules.
3. ddev composer require 'drupal/ai:^1.0.x-dev'
4. ddev drush en ai ai_translate key admin_toolbar admin_toolbar_tools -y
5. Create an Article in English.
6. Click translate tab.

I see an error message:

I click on the link in the error to /en/admin/config/ai/providers and the text there tells me to "Choose a provider from the AI module homepage, add it to your project, then install and configure it first."

I ignore the first instruction to "Choose a provider" and click on the link to "configure it first" instead, which goes to /en/admin/config/ai/providers

I see an Access Denied error.

Issue reproduced.

Let's install this fix...
ddev composer config repositories.ai vcs https://git.drupalcode.org/issue/ai-3499412.git
ddev composer require drupal/ai:3499412-no-provider-warning-dev

Back at /en/admin/config/ai/settings I now see a new Warning message: "You have no AI providers enabled. Please install and enable a provider module."

This is an improvement as it makes it clear you have an immediate issue you need to deal with.

I think clarity would be further enhanced by changing the second sentence shown on screen from:

Choose a provider from the AI module homepage, add it to your project, then install and configure it first.

to

Choose at least one AI provider module from those listed on the AI module homepage, add to your project, install and configure it. Then update the AI Settings on this page.

There's some related chat over at https://www.drupal.org/project/ai/issues/3499412#comment-15944839 📌 Make selection of AI Provider clearer on module homepage Active too.

Text at #2 is perfect.

I think the other issue was discussed at https://www.drupal.org/project/ai/issues/3498757#comment-15939611 🐛 Installation/configuration resilience (ai_translate) Active , which you pointed to an existing ticket at https://www.drupal.org/project/ai/issues/3498887#comment-15944828 ✨ Add useful message on providers page when no provider enabled Active

I'll try to test that patch and the above patch today.

I raised the same issue over in https://www.drupal.org/project/ai/issues/3498757#comment-15939611 🐛 Installation/configuration resilience (ai_translate) Active , so I'm in a position to test this patch later today.

dunx → created an issue.

I had a similar issue installing a patch to project_browser yesterday. Full steps at https://www.drupal.org/project/project_browser/issues/3498901#comment-15... 🐛 Recipe description appears twice in modal Active

Error was

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/drupal_cms_starter 1.x-dev -> satisfiable by drupal/drupal_cms_starter[1.x-dev].
    - drupal/drupal_cms_starter 1.x-dev requires drupal/project_browser ^2-alpha7 -> found drupal/project_browser[2.0.0-alpha7, 2.0.x-dev] but it conflicts with your root composer.json require (3498901-recipe-description-appears-dev).

@wouters_f you said "What you're describing has nothing to do anymore with the ai_translate module. You can't configure providers that you haven't installed so the 404 makes sense in some way."

Where should I raise this access denied issue then if it's not against this module?

It's not a 404, it's an access denied. But I hear you. Happy to make some improvement with the first issue and much appreciated of course.
I can raise the second issue separately.

Will update this to RTBC.

Okay, I tried this:
ddev composer require drupal/project_browser:"dev-3498901-recipe-description-appears as 2.0.7-alpha7" (Thanks the_g_bomb)

A quick refresh and now the Recipe modal looks like this:

Looks fixed to me so another for RTBK.

Tested on drupal_cms dev.

Steps using ddev to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Followed be skip of available recipe installation and minimum setup.

Visit project recipes page at /admin/modules/browse/recipes and then click on a recipe.
The *modal* looks like this:

Applied patch:
ddev composer require 'drupal/project_browser:2.0.x-dev'
ddev composer config repositories.project_browser vcs https://git.drupalcode.org/issue/project_browser-3498901.git
ddev composer require drupal/project_browser:dev-3498901-recipe-description-appears

Hmmm... MR not applying:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/drupal_cms_starter 1.x-dev -> satisfiable by drupal/drupal_cms_starter[1.x-dev].
    - drupal/drupal_cms_starter 1.x-dev requires drupal/project_browser ^2-alpha7 -> found drupal/project_browser[2.0.0-alpha7, 2.0.x-dev] but it conflicts with your root composer.json require (3498901-recipe-description-appears-dev).

Is that an issue with the MR or (more likely I'll happily admit), a problem with me?

Tested on drupal_cms dev.

Steps using ddev to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Followed be skip of available recipe installation and minimum setup.

Project recipes page at /admin/modules/browse/recipes currently looks like this:

Ah, looks like this is already fixed in dev! Well, I'll leave this here just in case. Nice work. Looking forward to the launch party in London tomorrow :)

Testing this issue with the patch at the above issue:

1. ddev composer config repositories.project_browser vcs https://git.drupalcode.org/issue/project_browser-3499406.git
2. ddev composer require drupal/project_browser:dev-3499406-fix-fallback-logic

Unfortunately didn't fix anything for me.

I've just raised https://www.drupal.org/project/project_browser/issues/3499630 🐛 Some mandatory parameters are missing ("source") to generate a URL for route "project_browser.browse" Active which is a different error message experienced on a fresh D11.1 install, which looks to be related to project_browse.browse

Different error message, but looks to be in a similar area to https://www.drupal.org/project/project_browser/issues/3499406 🐛 Fix fallback logic for empty $source in browse() method to ensure config validation with improved fallback logic Active

I updated to dev with ddev composer require 'drupal/project_browser:^2.0.x-dev' and get the same error.

dunx → created an issue.

For me it makes the distinction between what I can see as an admin (or content editor or whatever admin-y role I have) and what the user will see much clearer. I appreciate there's outliers with the View / Edit / Delete... toolbar, but one of my original screenshots would be a good example.

Nice @bojanz and thanks for the timely update for Drupal CMS 1.0 :)

dunx → created an issue.

Steps to set up for test

1. Installed D11 Umami
2. Installed and enabled key module at current
3. (Installed and enabled admin_tools)
4. ddev composer require 'drupal/ai:1.0.x-dev'
5. ddev composer config repositories.ai vcs https://git.drupalcode.org/issue/ai-3498757.git
6. ddev composer require drupal/ai:349875-aitranslate-resilience-dev
7. ddev drush en ai ai_translate -y
8. No configuration of the ai module or sub-module has been performed.

Steps to test

I created an article and then clicked on the Translate tab.
An error is no longer displayed :)
Instead I see this helpful error message, which is an improvement.

I clicked on that link (/en/admin/config/ai/settings).
There's nothing in any of the Dropdowns as expected as I haven't set Open AI up yet (or any other provider).
So I click on the "configure" link here.

And I get the same "Access denied" error as before.

What I need to do is download and enable the ai_provider_openai module. But I should not see an access denied error, just because I haven't.

Summary

The first issue has been fixed, but the second issue remains unresolved.

I'll test this today.

My motivation for raising was 100% based on the UX for the target audience of Drupal CMS.

If we're not keen on making "admin mode" more obvious, then perhaps we could add it as something a new user might want to consider after they've initially launched it. I know there's some "welcome" type pieces already delivered with Drupal CMS, so perhaps we could add to that content.

Happy to review with a fresh pair of non-maintainer, barely-a-dev-any-more, new eyes if you would like.

I can't see pameeela in any of those changes, just pavlosdan, _doyle_ and mglaman.

For info, there are now patches for both missing icons. This is a screenshot from a fresh D11 installation, rather than Drupal CMS.

I just tested this.

1. Fresh install of current D11.
2. Applied that patch via https://git.drupalcode.org/issue/geofield-3498685.git
3. Clock the "+ Create new field" on any content type.

The new icons appears as it should (in orange). [I've just tested the Address icon patch too (in yellow).]

Both of these contrib modules are part of Drupal CMS, which I why I'm keen to get both icons in place before the launch next week :). Thanks.

Tested and successful.

1. Installed current D11.
2. Added the address module composer require drupal/address
3. Installed this patch with composer.
4. Visit /admin/structure/types/manage/article/fields/add-field

The address field now has a suitable icon.

I raised this issue against Drupal CMS 📌 Create unique Address and Geofield field type icons for better UX Active as Geofield is one of only two field types that does not have its own icon within the new field UI. As this impacts the initial Drupal CMS user experience it would be great to have this fixed before the launch of Drupal CMS is 5 days :)

I will try and test this patch today.

I raised this issue against Drupal CMS 📌 Create unique Address and Geofield field type icons for better UX Active as the Address field is one of only two field types that does not have its own icon within the new field UI. As this impacts the initial Drupal CMS user experience it would be great to have this fixed before the launch of Drupal CMS is 5 days :)

I will try and test this patch today.

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

dunx → created an issue.

I can confirm that if you perform a ddev restart on your container then this status warning goes away.

I came to this issue because I was seeing the warning after running the launch-drupal-cms.sh script that "we" had provided for people to "Try it out locally" at https://new.drupal.org/drupal-cms/release-candidate.

I'm not sure how we'll be asking people to install Drupal CMS 1.0, but if we can add a ddev restart to any script provided that would be good. Does anybody know here whether the same script-based launcher will be used or something else, so I can raise this as a separate issue for that script?

Fine by me and agree that an event requires more info to be displayed and a different format with shortened months is sensible.

My main point was with the rest of the date format inconsistencies, but these have been addressed, so thanks to whoever did that :)

• The "After" shot on #OP shows Mon, Mar 24 - Thu, Mar 27 2025
• My screenshot on #18 shows Sun, 23 Mar 2025, 2pm - Thu, 27 Mar 2025, 1:59pm

The styling itself has been fixed and date formats have also been addressed.

I can raise those tomorrow.

That icon means "external website" not "new window", so it looks correct in this context.
As noted, it's not considered good UX to open links in a new window. If people want to do that, they can choose to do so.

I was also able to delete the Spanish translation, which I couldn't do before the patch was applied. I don't think that's strictly related, but an improvement anyway.

After I applied that patch, it worked as expected:

1. Created some English content - not published.
2. I used the AI translate to Spanish link on the Translate tab.
3. That created the Spanish content - also unpublished.

I think that change is ready to go.

I tested it with AI (Artificial Intelligence) 1.0.0-beta7 as noted above. I was asked to retest in beta5 at #7. The issue is still present in beta7. The patch is not present in beta7. Shall I apply and retest?

I know ticket not active, but just feeding back for those that come after. Latest build now has the following Warnings displayed, so improvements have already been made.

I can confirm that after fresh install of current dev, this SVG warning is no longer displayed :)

I performed a latest install from git:

git clone https://git.drupalcode.org/project/drupal_cms.git
cd drupal_cms
ddev config --project-type=drupal11 --docroot=web --php-version=8.3
ddev start
ddev composer install 
ddev launch

Now admittedly, it did take a few attempts to get what I wanted, but the final build was preceded by a:
ddev stop --omit-snapshot --remove-data
which I think should have resulted in a clean install.

On completing the installation and visiting the Status Report page, I still see the "Transaction isolation level" warning.

Yes... but we should be implementing best practice, so those marketing-types can follow our lead. Agree otherwise.

I thought I'd check out the date formats, beyond the actual styling, which I agree is fixed.

TLDR: Formats still not consistent on latest build. Perhaps we don't care, but it looks odd to me.

Steps to reproduce:

git clone https://git.drupalcode.org/project/drupal_cms.git
cd drupal_cms
ddev config --project-type=drupal11 --docroot=web --php-version=8.3
ddev start
ddev composer install 
ddev launch

• Complete initial installation.
• Create simple block view of "Latest" to include Blogs, News and Event content types (see screenshot).

• Use Layout Builder to add new Section to homepage.
• Add my "Latest" block view to that Section and save.

Date formats are still inconsistent.

I created the first piece of news content for the site. The date format for that matches the Blog format.

dunx → created an issue.

I performed a fresh install from git:

git clone https://git.drupalcode.org/project/drupal_cms.git
cd drupal_cms
ddev config --project-type=drupal11 --docroot=web --php-version=8.3
ddev start
ddev composer install 
ddev launch

On visiting /admin/content/media I can confirm the Scheduled Media tab is no longer present.

This looks like a fix to me.

I was using the zip file @pameeela. I'lll re-test all of these Status Report Warning issues today using the latest 1.x. I'll have a play around with ddev rebuild and ddev restart and report back.

Not sure I agree with this:

We should encourage any future content types that need a date field use field_event__date

Field naming is important, so using an "event" date for anything other than an event content type is counter to best practice (code and config readability being top of the list for me on that one).
We can certainly encourage similar date field configuration, but for new fields.

Can test tomorrow no problem. Speedy speedy :)

I tried to duplicate my original issue on Umami with just the following core and modules enabled:

• Drupal Core 11.1.1 - long list
• Admin Toolbar 3.5.1 - toolbar and extras
• AI (Artificial Intelligence) 1.0.0-beta7 - AI Core and AI Translate
• Key 8.x-1.19

I'm logged in as the admin account.

I created an unpublished article and then clicked on the Translate tab.

I see the following errors:

• Error message - Please set a default chat provider & model in the AI module settings.
• Error message - Warning: Undefined array key 1 in Drupal\ai_translate\Form\AiTranslateForm->buildForm() (line 116 of modules/contrib/ai/modules/ai_translate/src/Form/AiTranslateForm.php).

Stack trace is:

TypeError: Drupal\Component\Utility\Html::escape(): Argument #1 ($text) must be of type string, null given, called in /var/www/html/web/core/lib/Drupal/Component/Render/FormattableMarkup.php on line 238 in Drupal\Component\Utility\Html::escape() (line 431 of core/lib/Drupal/Component/Utility/Html.php).
Drupal\Component\Render\FormattableMarkup::placeholderEscape() (Line: 187)
Drupal\Component\Render\FormattableMarkup::placeholderFormat() (Line: 195)
Drupal\Core\StringTranslation\TranslatableMarkup->render() (Line: 15)
Drupal\Core\StringTranslation\TranslatableMarkup->__toString() (Line: 203)
Drupal\Core\Utility\LinkGenerator->doGenerate() (Line: 180)
Drupal\Core\Utility\LinkGenerator->generate() (Line: 164)
Drupal\Core\Link->toString() (Line: 128)
Drupal\ai_translate\Form\AiTranslateForm->buildForm()
call_user_func_array() (Line: 528)
Drupal\Core\Form\FormBuilder->retrieveForm() (Line: 279)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 219)
Drupal\Core\Form\FormBuilder->getForm() (Line: 19)
Drupal\ai_translate\Controller\ContentTranslationControllerOverride->overview()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 593)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 183)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)

I want to use Open AI, but visiting the link displayed under "Default providers" at /en/admin/config/ai/settings to /en/admin/config/ai/providers gives me an access denied error. I am admin.

Ooops... so I'd missed the ai_provider_openai module, but an access denied error doesn't seem very helpful.
I installed and enabled that module.
I added my Open AI key via /en/admin/config/system/keys and configured ai_provider_openai to use that key at /en/admin/config/ai/providers/openai

That access denied error has gone away :)

I click on the Translate tab again. Same two errors.

Ooops... I haven't configured AI Translate to use Open AI yet.
Dropdown at /en/admin/config/ai/ai-translate says to use the "Default from AI Module (chat)", which is just as well as there's no AI option under "Translate Text" at AI settings (/en/admin/config/ai/settings) which is what I was expecting to have to configure.
So I configure the Chat at that same URL to use Open AI and gpt-3.5-turbo.

I click the Translate tab again. Hoorah, no errors.

I click on "Translate using gpt-3.5-turbo" to create a Spanish translation. That works.

But, it's still Published when the original English is Not published.

This feels like a fail to me.

Should I raise the other errors as separate issues?

pameeela → credited dunx → .

Thanks. It's hard to provide feedback on Drupal CMS as a product when it's based on Core with its own separate issues. I'm just providing feedback on the product as requested given it's launching in a few days and we all want to see it at its best give the fanfare around its launch. It's probably very annoying for you, but I appreciate the responses.

Thanks.

I can't *see* any way to schedule media, only a way to view a list of those things I can't set up, haha.

As you note, who needs that on a simple website anyway? Probably not a good requirement for Drupal CMS out of the box.

Perhaps wrap it in to a "Publishing" Recipe as noted by Tony.

Gets a mention here too Tony.
https://www.drupal.org/project/drupal_cms/issues/3497655 📌 Status report showing warnings on clean installation Active

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.