Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 10.
To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects
Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches 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 "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.
The patches 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 patches 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 "ProjectUpdateBotD10" tag is left on this issue, new patches 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 patches 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 patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" 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 patches will be posted here.
If the issue is reopened, then new automated patches will be posted.
If you are using another issue(s) to work on Drupal 10 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.
Providing feedback
If there are problems with one of the patches 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.
Issue fork fast_404-3287465
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.12.0, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #3
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.13.0, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #4
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.13.1, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #5
shamir.vs commentedHi, Patch #4 applied successfully, but the patch was incompatible with Drupal 10.
Providing a patch to make the module compatible with Drupal 10.
Please review
Comment #6
robloachInstalled properly! Nicely done.
Comment #7
kristen pol@shamir.vs and/or @RobLoach Curious if you were working on this as part of the Drupal 10 Global Porting Day?
Comment #8
project update bot commentedComment #9
rajab natshahComment #10
rajab natshahThank you for having time to maintained the Fast 404 module.
an important module for performance.
Hoping for a soft commit on the
8.x-2.xbranch. To ease with further testing under Drupal 10Testing now with
git clone git@git.drupal.org:project/fast_404.gitHad real physical testing round for Fast 404 with Drupal ~10
Get the patch and apply it under Drupal 10 site. ( to be able to enable )
Change file/directory mod and ownership of files:
Install with Drush
Rebuild the cache:
Open a browser and change the address to:

http://localhost/sandboxes/drupal10fast_404__test/web/no-pageThe following Page not found page will show up
On having the following in the
settings.phpfileRebuild the cache:
Navigate to

http://localhost/sandboxes/drupal10fast_404__test/web/no-pageor reload the URL in the browserThe following fast 404 page will show up
Comment #11
rajab natshahComment #12
rajab natshahHoping for a soft commit and a soft tag release (
pre-release), to speed up update testing with Drupal 10Comment #13
rajab natshahComment #14
pcate commented+1 RTBC. The patch applied cleanly and fixed D10 compatibility issues.
Comment #16
jeremy.sloan commentedPCate which fast_404 version are you using? I am using 2.0.0-alpha6 and the patch doesn't apply.
Comment #17
pcate commentedI applied it the 8.x-2.x branch.
Comment #20
yahyaalhamadI created an issue fork using the patch, to use it:
Use this in your composer.json:
Install fast_404 from the issue fork.
composer require 'drupal/fast_404:dev-3287465-automated-drupal-10'Comment #21
fabsgugu commentedThis MR can be accepted?
It would be nice to release a new version with this commit.
Comment #22
edmund.dunn commentedPosting the static patch because using the MR doesn't allow pinning to a specific commit, so anyone can submit pretty much anything and inject it into our codebase IIRC. This also fixed our issue.
Comment #23
edmund.dunn commentedNever mind, it doesn't apply using composer. My apologies.
Comment #24
edmund.dunn commentedThis applies cleanly via composer. I had to take out the portion that applied to fast_404.info.yml. If anyone can get that working via composer it would be super helpful!
The relevant change would be:
core_version_requirement: ^8.8 || ^9 || ^10Comment #25
edmund.dunn commentedFound the solution. https://www.drupal.org/project/drupal/issues/3036459#comment-14836380 I had to add it in a separate patch file. But it installs cleanly.
Comment #26
ershov.andrey commentedFix for
8.x-2.0-alpha6Comment #27
joseph.olstad#3363607: Offer to maintain fast_404
Comment #29
joseph.olstad