🇮🇳India @KumudB

I have raised the MR for filter/tips page access permission.
MR : https://git.drupalcode.org/project/drupal/-/merge_requests/9617/diffs

kumudb → changed the visibility of the branch 3063877-add-page-access-permissions to hidden.

kumudb → changed the visibility of the branch 3063877-add-access-control to active.

Here are the Screenshot attached for issue which is not reflected on file listing page.

As per the review, I have learned that the permissions for "Edit any file" and "Edit own file" are correctly listed under file permissions; however, they are not reflected on the file listing page. Currently, only the delete option is visible for the admin role. When permissions are granted to other roles, the edit options still do not appear on the file list or usage page. These changes are not being reflected as expected.

Resolution: Issue Not Reproducible in Drupal 10.2.3

After further testing, I was unable to reproduce this issue on a site running Drupal version 10.2.3. The warnings related to the mkdir(): Permission Denied error when attempting to create the php/twig folder in sites/default/files are not occurring in this version.

Given that the issue does not persist in 10.2.3, I am marking this issue as resolved and closing it.

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

I have verified the changes and have raised a MR to address the issue of inconsistent plugin representation in the CKEditor configuration interface. Please review the PR at your convenience. Thank you!

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

It appears that this issue has been resolved in the latest version of Drupal 11. I have tested the scenario and verified that the error message no longer includes the "(all languages)" suffix.

I have attached a screenshot for reference. Given that the problem is no longer present, I believe we can close this issue.

Thank you!

I have closed this issue as I was unable to reproduce it with the latest pull from the 11.x branch. It appears that the issue has been resolved with recent fixes.

If anyone encounters a similar issue in the future, please feel free to open a new issue.

Thank you!

I wanted to update regarding the issue we discussed. I pulled the latest code from the 11.x branch, and I was unable to reproduce the issue locally. This behavior was consistent with the problem we encountered previously, so it seems to be resolved with the recent changes.

For reference, I’ve attached recording that demonstrate the current state of the application.

Please let me know if you need any further information or if there’s anything else I should look into.

In Drupal 11.x, I have attempted to reproduce the issue by creating a content type and adding fields such as a paragraph field and a date field (which is not required). I applied the validation function to this setup, but I am currently unable to reproduce the error. It seems that the issue might be related to an incorrect validation function name, which could lead to AJAX errors when collapsing or editing paragraph fields in the content type.

To reproduce the issue, follow these steps:

1. Create a Content Type: Add the necessary fields, including a paragraph field and a date field.
2. Apply the Validation Function: Implement the custom validation function to check the fields as per the requirements.

/**
 * Implements hook_form_alter().
 */
function customTweaks_form_alter(&$form, FormStateInterface $form_state, $form_id) {
  if ($form_id == 'node_product_form' || $form_id == 'node_product_edit_form') {
     $form['#validate'][] = 'customTweaks_node_form_validate';
  }
}

/**
 * Custom validation handler for the product node forms.
 */
function customTweaks_node_form_validate(&$form, FormStateInterface $form_state) {
    // Only validate if the form is being submitted with published status.
    if ($form_state->getValue('status')['value'] == 1) {
      // Check for the product publish date field.
      if (empty($form_state->getValue('field_prod_publish_date')[0]['value'])) {
        $form_state->setErrorByName('field_prod_publish_date', t('The publish date field must be completed before publishing.'));
      }
    }
  }

3. Test the Form: Attempt to collapse or edit the paragraph field in the content type and observe if AJAX errors occur. in this code it does not occur.
4. If the validation function is incorrect or not properly implemented, it may lead to errors during these actions.

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

There is an issue occurring when clicking on the entity used for the logo from the file system.

1. Upload a custom logo:
Navigate to Administration > Configuration > User Interface > Navigation > Settings.
Upload and save your custom logo.

2. Save the configuration:
Ensure the changes are saved properly.

3. Verify the issue:
Go to Administration > Content > Files.
Locate your most recently uploaded logo file.
Click on the Usage link for this file.
Observe the error that appears.

The website encountered an unexpected error. Try again later.

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "logo" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 138 of core/lib/Drupal/Core/Entity/EntityTypeManager.php).

My apology, issue is exist. here change status

this issue is resolved on this

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

and its working as expected.

MR has been created and merged for Drupal 10.x.1MR !1864 mergeable Please review it.

KumudB → created an issue.