Automated Drupal 11 compatibility fixes for bibcite

Open on Drupal.org →

Created on 15 March 2024, 9 months ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes will be posted by the Project Update Bot → official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

Accept automated changes until this issue is closed
If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes will be posted periodically if new deprecation fixes are needed.

As the Drupal Rector project improves and is able to fix more deprecated API uses, the changes posted here will cover more of the deprecated API uses in the module.

Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.
Leave open but stop new automated changes.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.
Close it and don't use it
If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.

If the issue is reopened, then new automated changes will be posted.

If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

Apply the latest patch in the comments by Project Update Bot → or human contributors that made it better.
Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

Review the merge request and test it.
Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes posted by the Project Update Bot → , such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue → . For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue → .

📌 Task

Status

Needs review

Version

3.0

Component

Code

Created by

project update bot

Live updates comments and jobs are added and updated live.

ProjectUpdateBotD11

Drupal 11 compatibility

Sign in to follow issues

Merge Requests

!24Automated Drupal 11 compatibility fixes for bibcite
Open
project update bot
updated 24 days ago

Comments & Activities

Issue created by @project update bot
Comment 9 months ago →
project update bot
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request 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.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #11-120024

This patch was created using these packages:

drupal/upgrade_status: 4.1.0

mglaman/phpstan-drupal: 1.2.7

palantirnet/drupal-rector: 0.20.1
Merge request !24Automated Project Update Bot fixes → (Open) created by project update bot
Comment 9 months ago →
project update bot
This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.

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-137198

These packages were used to generate the fixes:

drupal/upgrade_status: 4.1.0

mglaman/phpstan-drupal: 1.2.10

palantirnet/drupal-rector: 0.20.1
Comment 6 months ago →
project update bot
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-199781

These 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
Comment 26 days ago →
🇦🇺Australia interlated
From Upgrade Status

web/modules/patched/bibcite/modules/bibcite_entity/config/optional/views.view.bibcite_contributor.yml 287 Support from all Views contextual filter settings for the default_argument_skip_url setting is removed from drupal:11.0.0. No replacement is provided. See https://www.drupal.org/node/3382316 → .

The change says remove it

"The Views setting default_argument_skip_url has been removed from all Views contextual filter settings. This setting has never worked and provided no clear use case that needed support in Drupal core.
First commit to issue fork.
Pipeline finished with Failed
24 days ago
Total: 389s
#352244
Comment 24 days ago →
🇺🇸United States mark_fullmer Tucson
To better establish that this is functionally compatible with Drupal 11, I added a generic .gitlab-ci.yml template to the existing merge request. Based on the output -- see https://git.drupalcode.org/issue/bibcite-3428258/-/jobs/3511898 -- there is still a significant amount of work to do here to make this D11 compatible.

Setting to "Needs work."
Pipeline finished with Failed
24 days ago
Total: 354s
#352259
Pipeline finished with Failed
24 days ago
Total: 367s
#352277
Pipeline finished with Failed
24 days ago
Total: 564s
#352299
Pipeline finished with Failed
24 days ago
Total: 357s
#352314
Pipeline finished with Failed
24 days ago
Total: 363s
#352415
Comment 24 days ago →
🇺🇸United States mark_fullmer Tucson
I worked through a number of D11 compatibility issues and got this merge request to a point where I think the remaining problems have to do with dependencies:

1. Failing test bibcite_entity/tests/src/Kernel/EntityCitationRenderTest outputs

TypeError: htmlspecialchars(): Argument #1 ($string) must be of type string, array given
, which is potentially due to a problem in the dependency seboettg/citeproc-php. See https://github.com/seboettg/citeproc-php/issues/184
2. Additionally, it appears that some logic has changed in Drupal's denormalizer: bibcite_import is not importing data in the way it did in Drupal 10 at /admin/content/bibcite/reference/import, with Symfony\Component\Serializer\Exception\UnexpectedValueException: Could not determine entity type bundle: "type" field is missing. in Drupal\serialization\Normalizer\EntityNormalizer->extractBundleData() (line 115 of /core/modules/serialization/src/Normalizer/FieldableEntityNormalizerTrait.php).. This can be reproduced in the UI.

At this point, probably a maintainer needs to weigh in.
Pipeline finished with Failed
24 days ago
Total: 458s
#352430
Pipeline finished with Failed
24 days ago
Total: 398s
#352452

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024