Re #58: dries it not a child theme. I'm also not using Drupal CMS. I got the error before running drush updatedb, but I'm not sure that is related.
I didn't make any code changes.
I only had this problem on my localhost (using DDEV), but not in production (using Acquia Cloud), so it might be related to that.
I ran into this problem when upgrading my personal site, https://dri.es/, from Drupal 11.0.x to Drupal 11.1.x.
I did not apply the patch but was able to fix this by doing something like:
drush theme:uninstall dries
drush config:set system.theme default claro -y
drush theme:install dries
drush config:set system.theme default dries -yThank you! I was able to merge it now. Appreciate the help.
I'm +1 on this change, and tried to merge it. Unfortunately, I ran into an error, and also ran out of time.
Actually, it didn't merge so let me set this back to 'Needs work'.
This looks good. Merged. Thank you for updating this.
This looks good. Thank you for working on this. Merged!
Good feedback. I propose we explore four things:
- Build a prompt library: Can we create a collection of prompts with their expected outputs? This library would serve as a baseline to automatically test the performance and stability of AI agents. If a prompt fails in the real world, we can add it to the test library. While AI agents aren't fully deterministic, using some kind of fuzzy matching might work. This would create a good "feedback loop" that allows us to improve the accuracy of AI agents and it could be used to assess release readiness and quality of the AI agents.
- Make sure there is a "User review step": We should ensure that users can review what the AI agent will do before it takes action. Is this something we can enforce? While a review step isn't foolproof — users might not always know if the proposed solution is correct or best — it provides an opportunity to catch errors.
- Decide on the best permission policy: Today, the AI agents are bound to permissions. We can already disable permissions to prevent AI agents from making disruptive mistakes. However, we can debate the exact policy. AI agents could either be limited by the permissions of the current user or they could have their own permissions, possibly a subset of the users' permissions? We could discuss if the AI agent should inherit the user's permissions or if it should have additional restrictions?
- Explore rollback functionality using Workspaces: Can we use Workspaces to add rollback functionality? The AI module could create an automatic workspace, similar to how a content approval workflow might, giving users the ability to roll back changes. I'm not sure this is feasible, but if it is, it would offer an additional layer of control. This would probably take a lot of UX and development work.
I'd love to see (1) and (2) explored first, with (3) and (4) as a potential future additions. Option (3) may become unnecessary depending on the success of (1) and (2). Finally, I believe (4) can wait, as it may require significant development effort and comes with its own limitations. Option (1) seems the most important, and option (2) can only help.
To keep things in perspective, it's good to remember that AI agents will make mistakes — just like humans do when using our "manual UIs". The challenges AI agents bring aren't always new, nor are they always best addressed within the AI agents themselves.
For example, over the years, I've manually created many content types with various fields and made plenty of errors along the way. I've created fields, added content, only to realize I used the wrong field type or misconfigured it. Fixing these mistakes often required deleting fields and starting over, or, worse, "massaging" them with manual database queries. We've all been there, I think. Many new users face these issues today with our manual UI. It's not new, per se.
Two thoughts flow from this:
- Yes, an AI agent without a review step could potentially create more problems. It's why we should explore adding a "Review step". But the opposite might be true as well; an AI agent might actually reduce mistakes, as it has more and better knowledge than new users ... We might find that a "Review step" is mostly for expert users that know how to validate an AI's actions.
- For tasks like adding fields, an alternative solution could be to make it easier to fix mistakes, such as by allowing users to "transform" a field's type or configuration after it was created and used. Not easy to implement, of course, but it would help people making mistakes with either the AI agent or manual UI.
Food for thought!
pameeela → credited dries → .
gábor hojtsy → credited Dries → .
Automated message: Chapter 14. Final Thoughts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 14. Final Thoughts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 14. Final Thoughts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Appendix A. Appendix guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 1. Understanding Drupal guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 1. Understanding Drupal guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 1. Understanding Drupal guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 1. Understanding Drupal guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 1. Understanding Drupal guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 1. Understanding Drupal guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 2. Planning Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 3. Installation guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 4. Basic Site Configuration guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 4. Basic Site Configuration guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 4. Basic Site Configuration guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 4. Basic Site Configuration guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 4. Basic Site Configuration guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 4. Basic Site Configuration guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 5. Basic Page Management guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 6. Setting Up Content Structure guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 7. Managing User Accounts guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 8. Blocks guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 8. Blocks guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 8. Blocks guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 9. Creating Listings with Views guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 9. Creating Listings with Views guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 9. Creating Listings with Views guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 9. Creating Listings with Views guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 9. Creating Listings with Views guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 10. Making Your Site Multilingual guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 10. Making Your Site Multilingual guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 10. Making Your Site Multilingual guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 11. Extending and Customizing Your Site guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 12. Preventing and Fixing Problems guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 12. Preventing and Fixing Problems guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 12. Preventing and Fixing Problems guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 12. Preventing and Fixing Problems guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 12. Preventing and Fixing Problems guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
Automated message: Chapter 13. Security and Maintenance guide deleted. Moving its content one level up in the documentation hierarchy.
pameeela → credited Dries → .
pameeela → credited Dries → .
pameeela → credited Dries → .
pameeela → credited Dries → .
pameeela → credited Dries → .
pameeela → credited Dries → .
pameeela → credited Dries → .
Jean-Paul Vosmeer → credited Dries → .