- Issue created by @project update bot
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
10 months ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
10 months ago Waiting for branch to pass - Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
7 months ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
7 months ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-217342These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- First commit to issue fork.
-
larowlan →
committed 940fd236 on 8.x-1.x authored by
Project Update Bot →
Issue #3435061: Automated Drupal 11 compatibility fixes for tome
-
larowlan →
committed 940fd236 on 8.x-1.x authored by
Project Update Bot →
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Gah I merged that by mistake, E_TOO_MANY_TABS
Going to revert it and reopen
-
larowlan →
committed 76e31bbf on 8.x-1.x
Revert "Issue #3435061: Automated Drupal 11 compatibility fixes for tome...
-
larowlan →
committed 76e31bbf on 8.x-1.x
- First commit to issue fork.
- First commit to issue fork.
- ivnish Kazakhstan
After applying the path from MR I get
Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "router.route_provider", path: "options_request_listener -> router.route_provider -> cache_tags.invalidator -> cache.tome_static -> maintenance_mode_subscriber -> url_generator". in Drupal\Component\DependencyInjection\Container->get() (line 147 of core/lib/Drupal/Component/DependencyInjection/Container.php).
TypeError: Drupal\Core\Cache\DatabaseBackend::__construct(): Argument #4 ($serializer) must be of type Drupal\Component\Serialization\ObjectAwareSerializationInterface, int given, called in /var/www/web/modules/contrib/tome/modules/tome_static/src/StaticCache.php on line 30 in /var/www/web/core/lib/Drupal/Core/Cache/DatabaseBackend.php on line 88 #0 /var/www/web/modules/contrib/tome/modules/tome_static/src/StaticCache.php(30): Drupal\Core\Cache\DatabaseBackend->__construct(Object(Drupal\mysql\Driver\Database\mysql\Connection), Object(Drupal\Core\Cache\DatabaseCacheTagsChecksum), 'tome_static', -1)
#1 /var/www/web/core/lib/Drupal/Component/DependencyInjection/Container.php(259): Drupal\tome_static\StaticCache->__construct(Object(Drupal\mysql\Driver\Database\mysql\Connection), Object(Drupal\Core\Cache\DatabaseCacheTagsChecksum)) - Assigned to sourav_paul
- Status changed to Needs work
3 months ago 7:11am 21 October 2024 - 🇮🇳India sourav_paul Kolkata
Even after creating an instance of serializer, as the 4th parameter in the DatabaseBackend::__construct method must be an instance of ObjectAwareSerializationInterface, facing this issue
ArgumentCountError: Too few arguments to function Drupal\tome_static\StaticCache::__construct(), 2 passed in /app/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 259 and exactly 3 expected in Drupal\tome_static\StaticCache->__construct() (line 33 of /app/web/modules/contrib/tome/modules/tome_static/src/StaticCache.php).
- First commit to issue fork.
- 🇸🇰Slovakia mirom
Hi @sourav_paul and @ivnish, can you please share steps to replicate your issues? I installed the module into clean-ish Drupal site and after pushing my fixes, I was able to perform all operations through drush as well as in the UI.
- 🇦🇺Australia realityloop
@mirom
Getting the following error locally, the node in question doesn't have any added fields that are date fields:
brian@drupal-foundry-web:/var/www/html$ drush tome:install -y // You are about to DROP all tables in your local database and re-install Tome. Do you want to continue?: yes. In SiteProcess.php line 214: The command "/var/www/html/vendor/bin/drush tome:import --yes --uri=https://drupal-foundry.ddev.site" failed. Exit Code: 1(General error) Working directory: Output: ================ [ERROR] Errors encountered when importing content: [ERROR] Error when running "'/var/www/html/vendor/bin/drush' 'tome:import-content' 'node.92365dea-5736-4f30-8b0b-c7e6b5585b98'": [warning] Undefined array key "end_value" SmartDateNormalizer.php:40 [error] Error: Call to a member function getTimestamp() on null in Drupal\serialization\Normalizer\TimestampNormalizer->denormalize() (line 39 of /var/www/html/web/core/modules/serialization/src/Normalizer/TimestampNormalizer.php) #0 /var/www/html/web/modules/contrib/smart_date/src/Normalizer/SmartDateNormalizer.php(40): Drupal\serialization\Normalizer\TimestampNormalizer->denormalize() #1 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\smart_date\Normalizer\SmartDateNormalizer->denormalize() #2 /var/www/html/web/modules/contrib/smart_date/src/Normalizer/SmartDateItemNormalizer.php(45): Symfony\Component\Serializer\Serializer->denormalize() #3 /var/www/html/web/core/modules/serialization/src/Normalizer/FieldItemNormalizer.php(33): Drupal\smart_date\Normalizer\SmartDateItemNormalizer->constructValue() #4 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\serialization\Normalizer\FieldItemNormalizer->denormalize() #5 /var/www/html/web/core/modules/serialization/src/Normalizer/FieldNormalizer.php(47): Symfony\Component\Serializer\Serializer->denormalize() #6 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\serialization\Normalizer\FieldNormalizer->denormalize() #7 /var/www/html/web/core/modules/serialization/src/Normalizer/FieldableEntityNormalizerTrait.php(152): Symfony\Component\Serializer\Serializer->denormalize() #8 /var/www/html/web/core/modules/serialization/src/Normalizer/EntityNormalizer.php(59): Drupal\serialization\Normalizer\EntityNormalizer->denormalizeFieldData() #9 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\serialization\Normalizer\EntityNormalizer->denormalize() #10 /var/www/html/web/modules/contrib/tome/modules/tome_sync/src/Importer.php(272): Symfony\Component\Serializer\Serializer->denormalize() #11 /var/www/html/web/modules/contrib/tome/modules/tome_sync/src/Importer.php(215): Drupal\tome_sync\Importer->loadEntityFromStorage() #12 /var/www/html/web/modules/contrib/tome/modules/tome_sync/src/Commands/ImportContentCommand.php(34): Drupal\tome_sync\Importer->importContent() #13 /var/www/html/vendor/symfony/console/Command/Command.php(279): Drupal\tome_sync\Commands\ImportContentCommand->execute() #14 /var/www/html/vendor/symfony/console/Application.php(1047): Symfony\Component\Console\Command\Command->run() #15 /var/www/html/vendor/symfony/console/Application.php(316): Symfony\Component\Console\Application->doRunCommand() #16 /var/www/html/vendor/symfony/console/Application.php(167): Symfony\Component\Console\Application->doRun() #17 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(110): Symfony\Component\Console\Application->run() #18 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(40): Drush\Runtime\Runtime->doRun() #19 /var/www/html/vendor/drush/drush/drush.php(139): Drush\Runtime\Runtime->run() #20 /var/www/html/vendor/drush/drush/drush(4): require('...') #21 /var/www/html/vendor/bin/drush(119): include('...') #22 {main}. Error: Call to a member function getTimestamp() on null in /var/www/html/web/core/modules/serialization/src/Normalizer/TimestampNormalizer.php on line 39 #0 /var/www/html/web/modules/contrib/smart_date/src/Normalizer/SmartDateNormalizer.php(40): Drupal\serialization\Normalizer\TimestampNormalizer->denormalize() #1 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\smart_date\Normalizer\SmartDateNormalizer->denormalize() #2 /var/www/html/web/modules/contrib/smart_date/src/Normalizer/SmartDateItemNormalizer.php(45): Symfony\Component\Serializer\Serializer->denormalize() #3 /var/www/html/web/core/modules/serialization/src/Normalizer/FieldItemNormalizer.php(33): Drupal\smart_date\Normalizer\SmartDateItemNormalizer->constructValue() #4 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\serialization\Normalizer\FieldItemNormalizer->denormalize() #5 /var/www/html/web/core/modules/serialization/src/Normalizer/FieldNormalizer.php(47): Symfony\Component\Serializer\Serializer->denormalize() #6 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\serialization\Normalizer\FieldNormalizer->denormalize() #7 /var/www/html/web/core/modules/serialization/src/Normalizer/FieldableEntityNormalizerTrait.php(152): Symfony\Component\Serializer\Serializer->denormalize() #8 /var/www/html/web/core/modules/serialization/src/Normalizer/EntityNormalizer.php(59): Drupal\serialization\Normalizer\EntityNormalizer->denormalizeFieldData() #9 /var/www/html/vendor/symfony/serializer/Serializer.php(238): Drupal\serialization\Normalizer\EntityNormalizer->denormalize() #10 /var/www/html/web/modules/contrib/tome/modules/tome_sync/src/Importer.php(272): Symfony\Component\Serializer\Serializer->denormalize() #11 /var/www/html/web/modules/contrib/tome/modules/tome_sync/src/Importer.php(215): Drupal\tome_sync\Importer->loadEntityFromStorage() #12 /var/www/html/web/modules/contrib/tome/modules/tome_sync/src/Commands/ImportContentCommand.php(34): Drupal\tome_sync\Importer->importContent() #13 /var/www/html/vendor/symfony/console/Command/Command.php(279): Drupal\tome_sync\Commands\ImportContentCommand->execute() #14 /var/www/html/vendor/symfony/console/Application.php(1047): Symfony\Component\Console\Command\Command->run() #15 /var/www/html/vendor/symfony/console/Application.php(316): Symfony\Component\Console\Application->doRunCommand() #16 /var/www/html/vendor/symfony/console/Application.php(167): Symfony\Component\Console\Application->doRun() #17 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(110): Symfony\Component\Console\Application->run() #18 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(40): Drush\Runtime\Runtime->doRun() #19 /var/www/html/vendor/drush/drush/drush.php(139): Drush\Runtime\Runtime->run() #20 /var/www/html/vendor/drush/drush/drush(4): require('...') #21 /var/www/html/vendor/bin/drush(119): include('...') #22 {main} [warning] Drush command terminated abnormally. Error Output: ================
- 🇦🇺Australia realityloop
Tome maintainer has made a d11 fork here https://git.drupalcode.org/project/tome/-/merge_requests/29
- Issue was unassigned.
- Status changed to Needs review
16 days ago 11:44am 12 January 2025 This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-392907These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.6
- mglaman/phpstan-drupal: 1.3.2
- palantirnet/drupal-rector: 0.20.3