lalustine → created an issue.
lalustine → created an issue.
lalustine → created an issue.
lalustine → created an issue.
lalustine → created an issue.
@safetypin i am not using any kind of patches. Can it be due to permission issues?
lalustine → created an issue.
Hi all, i am also facing issues like after running "drush updb" command, its not listing all the groups and when you view groups, lots of tabs are missing.
Hi jsacksick, its not the issue with webform_product module. I have reverted back drupal from 10.2.5 to 9.5 with all modules and database as well. The issue is not there and when I tested $shipping_profile->isNew(), its giving false for already existing shipping profile which was not the case in drupal 10.2.5.
Either drupal 10.2.5 have issue or my database had an issue as $shipping_profile->isNew() was giving true for already existing shipping profile every time. I will try to upgrade drupal once again and see if the issue comes again.
Hi tBKoT, all i can see is commerce_checkout,commerce_order which is commerce core module and commerce_shipping only.
Hi jsacksick, as i debugged I found that the shipment needs a shipment profile and when you are logged in already created shipment is passed. And I found another interesting thing that $shipping_profile->isNew() is giving true or 1 for the already existing shipping profile. Currently orders with shipment are only failing for me.
With anonymous users, it's not breaking and everything is fine and new shipping profile is created.
I don't think I have used any custom code which is affecting it. I can see whenever order is trying to save shipment with existing shipping profile, its failing in commerce shipping module. May be $shipping_profile->isNew() giving true or 1 for the already existing shipping profile can be the culprit which is telling to create profile for already existing profile. I experienced the same issue with other orders but I found the place to fix it by checking profile exit or not. But in this shipment scenario, I could find the place to add logic for that.
lalustine → created an issue.
lalustine → created an issue.
lalustine → created an issue.
I can see the similar issue raised by another person.
https://www.drupal.org/project/commerce_shipping/issues/3309439
🐛
Race condition: new profile gets saved twice in ShippingInformation::validatePaneForm(), resulting in duplicate UUID exception
Active
I checked it but could not find any custom code that's causing an issue. It's just pointing me to commerce shipping code as you can see in above errors.
Above solution did not fixed the issue. And I found that now I am not able to access group entities even I am assigned webmaster role.
lalustine → created an issue.
Hi #jsacksick, i am using Commerce Shipping 8.x-2.8
lalustine → created an issue.
lalustine → created an issue.
Thanks @ressa, once i deleted composer.lock and run "composer install", its upgraded drupal core. After upgrade there are new issues but no problem. Finally drupal core upgraded. Hurray!!
lalustine → created an issue.
Thanks jsacksick for the suggestion.
Hi @ressa, i get below result after using updated composer.json with composer install
# composer install
Gathering patches for root package.
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.
- Required package "drupal/core-composer-scaffold" is in the lock file as "9.5.11" but that does not satisfy your constraint "10.2.5".
- Required package "drupal/core-project-message" is in the lock file as "9.5.11" but that does not satisfy your constraint "10.2.5".
- Required package "drupal/core-recommended" is in the lock file as "9.5.11" but that does not satisfy your constraint "10.2.5".
This usually happens when composer files are incorrectly merged or the composer.json file is manually edited.
Read more about correctly resolving merge conflicts https://getcomposer.org/doc/articles/resolving-merge-conflicts.md
and prefer using the "require" command over editing the composer.json file directly https://getcomposer.org/doc/03-cli.md#require-r
so i run below command and got the output.
$ composer require drupal/core-recommended:10.2.5 drupal/core-composer-scaffold:10.2.5 drupal/core-project-message:10.2.5 --update-with-all-dependencies
./composer.json has been updated
Running composer update drupal/core-recommended drupal/core-composer-scaffold drupal/core-project-message --with-all-dependencies
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/core-recommended 10.2.5 -> satisfiable by drupal/core-recommended[10.2.5].
- drupal/core-recommended 10.2.5 requires drupal/core 10.2.5 -> found drupal/core[10.2.5] but these were not loaded, likely because it conflicts with another require.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
So i tried to see what causing drupal/core 10.2.5 not able to install using below command and got output.
composer why-not drupal/core 10.2.5
drupal/civicrm_entity 3.5.0 requires drupal/core (^8.8 || ^9)
drupal/core-recommended 9.5.11 requires drupal/core (9.5.11)
drupal/csv_serialization 3.0.1 requires drupal/core (^9.4)
drupal/linkit 6.0.2 conflicts drupal/core (>=10.1)
drupal/sparkpost 2.2.0 requires drupal/core (^8 || ^9)
drupal/core 10.2.5 conflicts drush/drush (<12.4.3)
drupal/core 10.2.5 requires symfony/console (^6.4)
drupal/recommended-project dev-master does not require symfony/console (but v4.4.49 is installed)
drupal/core 10.2.5 requires symfony/dependency-injection (^6.4)
drupal/recommended-project dev-master does not require symfony/dependency-injection (but v4.4.49 is installed)
drupal/core 10.2.5 requires symfony/event-dispatcher (^6.4)
drupal/recommended-project dev-master does not require symfony/event-dispatcher (but v4.4.44 is installed)
drupal/core 10.2.5 requires symfony/filesystem (^6.4)
drupal/recommended-project dev-master does not require symfony/filesystem (but v4.4.42 is installed)
drupal/core 10.2.5 requires symfony/http-foundation (^6.4)
drupal/recommended-project dev-master does not require symfony/http-foundation (but v4.4.49 is installed)
drupal/core 10.2.5 requires symfony/http-kernel (^6.4)
drupal/recommended-project dev-master does not require symfony/http-kernel (but v4.4.51 is installed)
drupal/core 10.2.5 requires symfony/mime (^6.4)
drupal/recommended-project dev-master does not require symfony/mime (but v5.4.13 is installed)
drupal/core 10.2.5 requires symfony/routing (^6.4)
drupal/recommended-project dev-master does not require symfony/routing (but v4.4.44 is installed)
drupal/core 10.2.5 requires symfony/serializer (^6.4)
drupal/recommended-project dev-master does not require symfony/serializer (but v4.4.47 is installed)
drupal/core 10.2.5 requires symfony/validator (^6.4)
drupal/recommended-project dev-master does not require symfony/validator (but v4.4.48 is installed)
drupal/core 10.2.5 requires symfony/process (^6.4)
drupal/recommended-project dev-master does not require symfony/process (but v4.4.44 is installed)
drupal/core 10.2.5 requires symfony/yaml (^6.4)
drupal/recommended-project dev-master does not require symfony/yaml (but v4.4.45 is installed)
drupal/core 10.2.5 requires twig/twig (^3.5.0)
drupal/recommended-project dev-master does not require twig/twig (but v2.15.6 is installed)
drupal/core 10.2.5 requires doctrine/annotations (^1.14)
drupal/recommended-project dev-master does not require doctrine/annotations (but 1.13.3 is installed)
drupal/core 10.2.5 requires guzzlehttp/guzzle (^7.5)
drupal/recommended-project dev-master does not require guzzlehttp/guzzle (but 6.5.8 is installed)
drupal/core 10.2.5 requires guzzlehttp/psr7 (^2.4.5)
drupal/recommended-project dev-master does not require guzzlehttp/psr7 (but 1.9.1 is installed)
drupal/core 10.2.5 requires asm89/stack-cors (^2.1)
drupal/recommended-project dev-master does not require asm89/stack-cors (but 1.3.0 is installed)
drupal/core 10.2.5 requires psr/log (^3.0)
drupal/recommended-project dev-master does not require psr/log (but 1.1.4 is installed)
Not finding what you were looking for? Try calling `composer update "drupal/core:10.2.5" --dry-run` to get another view on the problem.lalustine → created an issue.
lalustine → created an issue.
Hi ressa, i have updated my above queries with latest commands and composer packages.
I have followed steps in the documentation but could not resolve. I can not uninstalled the modules which do not supports as they are being used in many places.
I have created a patch so anyone can use it
lalustine → created an issue.
lalustine → created an issue.
Hi @dench0 & @Pablo_Pukha, thanks for your great help but since i am using drupal module recaptcha v3 module, i dont see any js inside module. I could find only recaptcha_v3.js with below codes
/**
* @file
* Recaptcha v3 behaviors.
*/
(($, Drupal) => {
function updateTokenElement(element) {
let timer;
// Wait for grecaptcha to be loaded.
if (typeof grecaptcha === 'undefined') {
timer = setInterval(() => {
if (typeof grecaptcha !== 'undefined' || !element) {
clearInterval(timer);
if (element) {
doUpdateTokenElement(element);
}
}
}, 500);
}
else {
doUpdateTokenElement(element);
}
}
function doUpdateTokenElement(element) {
let $element = $(element);
grecaptcha.ready(() => {
if (!element) {
return;
}
grecaptcha.execute($element.data('recaptchaV3SiteKey'), {
action: $element.data('recaptchaV3Action')
}).then((token) => {
$element.val(token);
$element.trigger('change');
});
});
}
/**
* Attach recaptcha response token from google with form.
*
* @type {{attach: Drupal.behaviors.reCaptchaV3.attach}}
*/
Drupal.behaviors.reCaptchaV3 = {
attach: (context) => {
once('recaptcha-v3-token', '.recaptcha-v3-token', context).forEach(
(element) => {
let interval;
updateTokenElement(element);
// Update the recaptcha tokens every 90 seconds.
// This seems to be the most robust way to always have valid recaptcha
// tokens when you don't have control over how the forms are being
// submitted. For example normal form submits are synchronous while
// Google Recaptcha v3 is asynchonous.
// A recaptcha token has a maximum lifetime of 120 seconds.
// https://developers.google.com/recaptcha/docs/v3
interval = setInterval(() => {
if (!element) {
clearInterval(interval);
} else {
updateTokenElement(element);
}
}, 90000);
}
);
}
};
})(jQuery, Drupal);
lalustine → created an issue.
Hi @COBadger,thanks for your revised patches. Now i am able to install the upgraded zoom api module but i am getting below issue while making post request with zoom api.
Failed to complete Zoom API Task "Client error: `POST https://zoom.us/oauth/token` resulted in a `400 Bad Request` response: {"reason":"unsupported grant type","error":"unsupported_grant_type"} "
I have filled Client Secret , Client ID and other details as suggested in the given link https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →