Likewise, mylocaltrades. I uninstalled and removed contact storage. But it did not remove the contact_message table.
I manually deleted the table which removed the error message, of course.
This perhaps is another issue with the contact storage module which could be addressed here or in another issue. Perhaps it is desirable to maintain the message storage even after removal of the module, or the uninstallation of the module should remove the table.
I will probably revert to webform, so it is no longer of concern to me.
GrahamShepherd → created an issue.
GrahamShepherd → created an issue.
Likewise.
I am on Drupal 10.1.0 and getting the same result as #3
GrahamShepherd → created an issue.
Thanks @itamair. I notice that on the project page the link to the issue goes nowhere, ie it need an href="".
"This will allow the module to be automatically upgraded when you upgrade Drupal core.
(For more info refer to
this Issue Comment
✨
Drupal 10 compatibility: changing php-http/guzzle6-adapter dependency into php-http/guzzle7-adapter
RTBC
.)"
It's petty, I'm sorry, but for completeness.
I have added this issue to the upgrade status module: https://www.drupal.org/project/upgrade_status/issues/3363765 ✨ Recognize the availability of a valid later module release which is not backwards compatible Active
GrahamShepherd → created an issue.
Thanks for the feedback.
It would seem appropriate that upgrade_status should recognize the broadening of composer.json version requirements where appropriate. There are probably several modules in the geocoder and csv_serialization category where a new version is required for Drupal 10 which is not compatible with Drupal 9.
I wll put in a suggestion to that effect against that module.
GrahamShepherd → created an issue.
I followed the example of csv_serialization → :
"When preparing for an upgrade to Drupal 10 we recommend that you widen your Composer version constraints to allow either 2.x or 3.x: composer require drupal/csv_serialization:^2.0 || ^3.0. This will allow the module to be automatically upgraded when you upgrade Drupal core."
In the case of geocoder I edited composer.json to:
"require": {
...
"drupal/geocoder": "^3.20 || ^4.0",
...
}
Upgrade status continued to report that geocoder was incompatible.
Nevertheless, I ran:
composer require 'drupal/core-recommended:^10' 'drupal/core-composer-scaffold:^10' 'drupal/core-project-message:^10' --update-with-dependencies --no-update
Followed by:
composer update
Database updates proceeded correctly.
Drupal updated to 10.0.9 and geocoder updated to 8.x-4.9.
Success.
I suggest adding a paragraph to the project page:
"When preparing for an upgrade to Drupal 10 we recommend that you widen your composer version constraints to allow either 3.x or 4.x. Edit composer.json to require drupal/geocoder: "^3.0 || ^4.0". This will allow the module to be automatically upgraded when you upgrade Drupal core."
Patch #4 doesn't work either.
Patch #6 does not work for me.
Drupal 9.5.8
Login_destination 8.x-2.0-beta6
Redirect set to for login redirects to user page and logout to the home page.
If I try and use token: /[current-page:url:path] the website reports an error.