🇵🇭Philippines @mjgruta

FYI, if you already have a composer.lock file. The patch will not work so you need to override it by adding this code to your composer.json or better if you have composer.libraries.json file then add this on the require section "jquery/icheck": "1.0.2".
After this just run composer require drupal/webform:^6.2 or what ever version you would like. This will generate the correct composer lock hash.

"jquery.icheck": {
"type": "package",
"package": {
"name": "jquery/icheck",
"version": "1.0.2 ",
"type": "drupal-library",
"extra": {
"installer-name": "jquery.icheck"
},
"dist": {
"url": "https://api.github.com/repos/drgullin/icheck/zipball/8a6eb37bd7dab1e843c...",
"type": "zip"
},
"license": "MIT"
}

+1 RTBC

If you already run database update. You can run below command to re-execute the database update.
Make sure you already applied the patch.

drush ev "\Drupal::service('update.update_hook_registry')->setInstalledVersion('block_class', 20016);";
drush updb;

We upgraded from Drupal 10.1 to 10.2.7 and had a WSOD

Twig\Error\RuntimeError: The "Drupal\Core\Template\TwigExtension" extension is not enabled. in Twig\ExtensionSet->getExtension() (line 35 of docroot/core/themes/claro/templates/admin/admin-block-content.html.twig).

We also had an old version of twig_extender.

Applying the patch #6 and using twig_extender 5.1.0 works fine.

+1 RTBC

mjgruta → created an issue.

To upgrade from Drupal 9 to Drupal 10 try to follow below list:

• Make sure all your modules version are compatible with Drupal 9 and Drupal 10 in your composer.json
• If the module doesnt have D10, you can force install it using Drupal Lenient. Follow the instructions here https://www.drupal.org/docs/develop/using-composer/using-drupals-lenient... → Make sure to add the module in the allowed list.
• Delete composer.lock core modules/contrib themes/contrib
• Run composer require drupal/core-recommended:^10.0 drupal/core-composer-scaffold:^10.0 drupal/core-project-message:^10.0 -W to make sure we can upgrade to Drupal 10.
• Run drush updb -y until everything is OK.
• Upgrade drupal to latest version then run drush updb again.

I am also confirming that the module works fine.
In my case, I used the grouping processor but needed to apply a patch from https://www.drupal.org/project/search_api_grouping/issues/3204272 🐛 Grouping not working with search_api_solr Needs review

Hoping to have a stable release version available soon.

Attaching the patch from MR.

Changing grouping_fields to fields fixes the issue.

Regarding #6
Make sure to use search_api_solr >= 4.3.4
A fix is already merged. https://www.drupal.org/project/search_api_solr/issues/3197641 →

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

The latest MR breaks. We have been using this URL as patch: https://git.drupalcode.org/project/content_sync/-/merge_requests/10.diff

[Drupal\Core\Extension\InfoParserException]
Unable to parse modules/contrib/content_sync/content_sync.info.yml yaml_par
se(): scanning error encountered during parsing: could not find expected ':
' (line 8, column 1), context while scanning a simple key (line 7, column 1
)

The patch in MR6 works fine. Adding the code here just in case someone modifies the code.

The same error is happening with entity_browser_table. The patch in this issue works for us.
https://www.drupal.org/project/entity_browser_table/issues/3408217 🐛 Error: Call to a member function getStorage() on null RTBC

2.x-dev is now available which is Drupal 10 ready. https://www.drupal.org/project/views_dates/releases/2.x-dev →
Closing this ticket

2.x-dev is now available which is Drupal 10 ready. Should we close this ticket? https://www.drupal.org/project/views_dates/releases/2.x-dev →

Patch works! it allows me to continue the import. Using Drupal 10.1.6, feeds_para_mapper 8.x-1.1, paragraphs 1.16, and feeds 3.0.0-beta4

Thanks, Vishal, I can confirm that enabling "Use Graph API otherMails property for email address" resolves the issue.
I think we should add a check if $profile_data[$upn] does not exist then we add an extra message to consider enabling the option above.

Thanks for the patch. Works well with v1.4
We now need to create a patch for the latest version. 2.0.0-beta7

When are we going to release a new version of D10? it is hard to install the dev version via composer.

Fixed error in phpstan validation.

@josh Sorry, the fix needs to be done on the field formatted viewElements as it is trying to pass the $item->format directly which will return null if the item doesn't have a format.
I have updated the code.

fixes $text_format type from null to string.

Created another patch file from commit 975c9a47. This should fix the comments from James.

Created a diff from commit 0779410f while fixing MR #60 to prevent the composer from failing to apply the patch.

It looks like you have a deleted user.
Regarding the code, maybe we should add the username from the exception to at least know the account that is failing.

                // There is no account by that name.  Log this as an exception.
                else {
                  throw new MaestroGeneralException(t('Unknown account name (@account) identified when attempting a notification.', ['@account' => $accountName]));
                }

I just noticed the comment from mike. Reverting the status to Needs work.

Updates from #30 break the patch. I have merged the latest code.

mjgruta → created an issue.

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

Hi @Sandip, we had similar issues but we upgraded from Drupal 8 to 10. in our case, the user id 0 was missing in the users table. I just created one and it seems to work fine now.

mjgruta → created an issue.

mjgruta → created an issue.

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

We cannot install this because ACL D10 is only available for ^2.0. Created a patch for this at
https://www.drupal.org/project/forum_access/issues/3354309#comment-15334749 🐛 Cannot install in Drupal 10 Active

We cannot install the module as it requires ACL ^1.1 in composer.json. ACL Drupal 10 is only available for ^2.0@beta
I created a patch, but I am not sure if this will work. I cannot test it as https://github.com/mglaman/composer-drupal-lenient only handles Drupal modules and not the composer dependencies of the module.

Another temporary solution is to revert ACL to ^1.1 and apply a D10 patch.

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

I'm getting the error below when running composer install.

In RemoteFilesystem.php line 108:
                                                                                                                                                                                                 
  [TypeError]                                                                                                                                                                                    
  Composer\Util\RemoteFilesystem::copy(): Argument #1 ($originUrl) must be of type string, null given, called in /home/ide/project/vendor/cweagans/composer-patches/src/Patches.php on line 388  

Using 1.x-dev and cweagans/composer-patches:1.7.3
composer require "drupal/leaflet_mapbox:1.x-dev@dev"
Added this module in drupal-lenient in composer.json and globally.

+1 RTBC, patch works on "drupal/webform_views": "^5.2"

Subscribing to this topic. We also need to have the D10 version. We really appreciate if this can be done ASAP so we have time to test.

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

re-rolled patch #15 to 2.1.x-dev

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

Patch #13 failed to latest 8.x-1.x-dev (Last updated: 23 Mar 2023 at 05:37 UTC)

mjgruta → created an issue.

mjgruta → created an issue.

Patch failed on the latest beta and dev. Attaching the updated patch please test.

Having the same issue. Using the following:
Drupal: 8.9.19
PHP: 7.3.28
openid_connect: 8.x-1.2
openid_connect_windows_aad: 8.x-1.4
openid_connect_login_redirect: 1.0.0-beta2

LogicException: The controller result claims to be providing relevant cache metadata, but leaked metadata was detected. Please ensure you are not rendering content too early. Returned object class: Drupal\Core\Routing\TrustedRedirectResponse. in Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (line 154 of /var/www/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php).

Sorry my bad, the site was using an old version. I have updated openid_connect to 1.2 and the error is gone.

mjgruta → created an issue.

Patch #29 doesn't work with Drupal Commerce. It's still asking for variations SKU and Price.