Manual steps to reproduce this issue with 11.1.0-dev
Module Configuration:
- The 'Content Moderation Workflows' module should not be enabled.
- The 'Workflow' module should be enabled.
Content Type Setup:
For the 'Article' content type, navigate "admin/structure/types/manage/article" to the "Publishing options". For the "Default options" ensure that 'Published' is unchecked.
Role Permissions:
- The 'Content editor' role should have the 'View published content' permission.
- The 'Content editor' role should have the 'Article: Edit own content' permission set.
- The 'Content editor' role should not have the 'View own unpublished content' permission set.
Steps and access :
- Create a user with the 'Content editor' role.
- Create an Article node with a custom URL alias.
- When accessing 'node/X' as a user with the 'Content editor' role, an 'Access denied' message should be displayed.
- When accessing 'node/X/edit' as a user with the 'Content editor' role, an edit form should be presented.
- When attempting to save the content of this node again, the user should receive the error message: "Either the path '/node/X' is invalid or you do not have access to it."
Additional Considerations:
Test user should not have additional permissions that could mask the issue: The 'Link to any page' and 'View any unpublished content' permissions should not be granted.
A functional test was implemented to address this issue:
https://git.drupalcode.org/issue/drupal-3167732/-/blob/3167732-non-admin...
It would be nice if someone could provide feedback on this failing test to confirm if continuing in this direction is recommended.
Thank you!
I have created a new ticket https://www.drupal.org/project/ai/issues/3479837 📌 Improve UX for AI Logs collection view Active to address these improvements. I'll be working on that.
Should "Response" and "Extra data" be trimmed in "en/admin/config/ai/logging/collection"?
Hi both, my question isn't directly related to the original issue, so please let me know if I should create a new ticket for it.
I'm wondering whether the "edit-form" = "/admin/config/ai/logging/collection/{ai_log}/edit" is necessary for the logs, or if users should not have the ability to edit logs?
vesnag → created an issue.
Hi,
Just for your information, I did a clean install of Core 11.0.5, when I ran ddev composer require drupal/event_platform:1.0.x-dev@dev --with-all-dependencies I encountered the following error:
Your requirements could not be resolved to an installable set of packages.
Problem 1:
- Root composer.json requires drupal/event_platform 1.0.x-dev@dev -> satisfiable by drupal/event_platform[1.0.x-dev (alias of dev-1.0.x)].
- drupal/event_platform dev-1.0.x requires drupal/maxlength ^2.1 -> satisfiable by drupal/maxlength[2.1.0, 2.1.1, 2.1.2, 2.1.3].
- drupal/maxlength[2.1.0, ..., 2.1.2] require drupal/core ^9.2 || ^10, but these versions were not loaded, likely due to a conflict with another requirement.
- drupal/maxlength 2.1.3 requires drupal/core ^9.5 || ^10, but these were also not loaded due to a similar conflict.
- drupal/event_platform 1.0.x-dev is an alias of drupal/event_platform dev-1.0.x and needs it installed.
I've put together a PR to tackle the PHPStan errors that were previously ignored.
Would love for someone to take a look at the PR when you get a chance. I'm happy to make any changes based on your feedback.
As already reported here https://www.drupal.org/project/drupal/issues/3403077 🐛 media_library_opener leads to massive GET requests that break varnish etc. Active , GET requests also break Varnish.
With the clean install of 10.2.3, the Media Library URL may extend beyond 2000 characters when navigating through pages.
Thank you IliaNoz for this patch. It works fine.
Hi John,
Thank you for this fix.
I tried to validate your patch, but unfortunately, it couldn't be applied to version 8.x-1.12.
The proposed solution is to implement a custom validation process that throws a custom exception. This exception will then be caught and handled by an EventSubscriber.
An alternative approach could be to implement custom validation and a custom submit handler, similar to the username enumeration prevention module → .
I am working on the exception-throwing approach.