Given patch failed to apply.
keshavv → created an issue. See original summary → .
There is no deprecation in this module. Please release it for Drupal 11.
Is there any plan for the release?
There is no deprecation in the module, We can release it for Drupal 11.
Added Drupal 11 Dependency in sub-modules as well. Coull someone please review the patch and prepare the release?
Thanks.
keshavv → changed the visibility of the branch drupal-11-compatibility to hidden.
The Dev version of this module is ready for Drupal 11 Release. Could someone please release it?
This module is functioning well with Drupal 11. Could someone please proceed with releasing it?
Patch for Drupal 11
Created patch for 3.0.x branch
The changes look good.
Looks good, Thank you.
I am encountering the same issue on Version 4.1.9. In my local DDEV environment, everything works perfectly without any issues.
However, on the production server hosted on AWS, a blank page is displayed on /sitemap.xml
. If I uncheck the option Add styling and sorting to sitemaps in the module settings, then the XML file is displayed.
Could someone please look into this?
We can ignore the patch added in https://www.drupal.org/project/lightning_workflow/issues/3389692 🐛 Creation of dynamic property Drupal\lightning_scheduler\Time::$_serviceId is deprecated RTBC because it will be addressed by the temporary fix in patch #77 for now.
The same issue mentioned in https://www.drupal.org/project/lightning_scheduler/issues/3297525#commen... 📌 Automated Drupal 10 compatibility fixes Needs work
I am getting the same error today on Drupal 10.2.6 and not able to resolve it.
lussoluca → credited keshavv → .
Same issue with the URL Alias section https://www.drupal.org/project/rabbit_hole/issues/3006187 ✨ Alias section is missing and don't work. Active
I have the same issue when I install the module and Enable the Allow these settings to be overridden for individual entities setting in the content configuration.
The Url Alias section is gone from the node add/edit page.
Please please provide the solution.
I have increased the max length to 1024 characters Because it is stored as a blob in the database.
Please review.
Given MR !3 Not worked.
I have rerolled the #3 patch and it works well with Drupal 10.1
The solution is to add the hook to your custom theme and add the offset from the top accordingly.
/**
* Implements hook_preprocess_views_view_bootstraptable().
*/
function template_preprocess_views_view_bootstraptable(&$variables) {
$view = $variables['view'];
$style = $view->style_plugin;
$options = $style->options;
if ($options["extension"]['sticky_header'] == 1) {
if (\Drupal::currentUser()->hasPermission('access toolbar')) {
// Set the Header offset from the top.
$variables["attributes"]['data-sticky-header-offset-y'] = 80;
}
}
}
Released, Thank you!
Hello @gdana, Please try this https://www.drupal.org/project/address/issues/3412241#comment-15408612 🐛 Mismatched field definitions after address upgrade Needs review
LGTM
Also, the quick solution is to update the definitions. https://www.drupal.org/project/address/issues/3412241#comment-15408612 🐛 Mismatched field definitions after address upgrade Needs review
Please look into this comment.
https://www.drupal.org/project/address/issues/3412241#comment-15408612
🐛
Mismatched field definitions after address upgrade
Needs review
Here is the solution for the problem
https://www.drupal.org/project/address/issues/3412241#comment-15408612
🐛
Mismatched field definitions after address upgrade
Needs review
@bserem Here is the solution for the same problem.
https://www.drupal.org/project/address/issues/3412241#comment-15408612
🐛
Mismatched field definitions after address upgrade
Needs review
Here is the patch to fix the warning.
@markdc No, It will not cause the issue, But if you want to fix this warning. Just execute this code using update_hook in a custom module or using the drush ev command
$entity_type_manager = \Drupal::entityTypeManager();
$entity_type_manager->clearCachedDefinitions();
$change_summary = \Drupal::service('entity.definition_update_manager')->getChangeSummary();
foreach ($change_summary as $entity_type_id => $change_list) {
$entity_type = $entity_type_manager->getDefinition($entity_type_id);
\Drupal::entityDefinitionUpdateManager()->installEntityType($entity_type);
}
Created patch for Mismatched entity and/or field definitions.
Please review.
Execute the following code in an update_hook or using drush ev. It will fix all the issues related to the Mismatched field definitions for all entities.
$entity_type_manager = \Drupal::entityTypeManager();
$entity_type_manager->clearCachedDefinitions();
$entity_type_ids = [];
$change_summary = \Drupal::service('entity.definition_update_manager')->getChangeSummary();
foreach ($change_summary as $entity_type_id => $change_list) {
$entity_type = $entity_type_manager->getDefinition($entity_type_id);
\Drupal::entityDefinitionUpdateManager()->installEntityType($entity_type);
$entity_type_ids[] = $entity_type_id;
}
I have found the same issue on Drupal 10.2.2. The site is hosted on Windows IIS Server.
Is this a critical issue?
Removed unused variables and fixed issues. Please review the patch.
Created patch, please review.
Created patch. Please test.
Patch #2 LGTM. We can merge it.
I have created the patch and fixed the Dynamic property creating deprecation.
Please review.
I have reviewed the #5 patch and confirmed that it solved the issue. We can merge this patch.
Moving to RTBC.
I have created the MR. Please review.
I faced the same issue in the date range field and the #75c patch works for me.
Added a comment in the MR. If someone review and update?
https://git.drupalcode.org/project/admin_toolbar/-/merge_requests/51
I can reproduce the issue.
Set the menubar vertical.
Reload the page.
Change the menubar position to horizontal and try to hover on the menu without reloading the screen.
Hover will not work.
However, The given patch failed to apply to me on version 3.4 so I have created a new for it.
Please review.
Thank you.
In the given MR! 20. There is a simple code refactor and it's working perfectly.
We can merge this MR if needed. It won't impact any issues.
Confirmed that the configure button is missing in the module.
Given MR works perfectly.
We can merge the MR.
Confirmed that there is a bug and given MR works perfectly.
We can merge the MR.
Hello @rudolfbyker
It will be good if we add a help page.
I have created a patch and added basic instructions.
Please review and update accordingly.
Thank you.
The issue is with README HELP module
https://www.drupal.org/project/readmehelp/issues/3412092
🐛
Fatal error on help page. Argument #2 ($name) must be of type string, array given.
Needs review
Closing issue.
I have created a patch for the same.
This issue only occurred in Drupal 10.2.0.
So please release it only for Drupal ^10.2
keshavv → created an issue.
I can reproduce the issue by following the steps, The given #2 patch works perfectly for me.
Rerolled patch #7.
This patch will only work for Drupal ^10. Please create a separate release for it.