Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Be ready for Drupal 9.
Proposed resolution
- [ ] Create a patch which follow the Gabor documentation: http://hojtsy.hu/blog/2018-dec-17/how-automate-testing-whether-your-drup... to expose potential code flaws
- [ ] Test the module using umami and the Upgrade Status module
Remaining tasks
- [ ] Create a patch which follow the Gabor documentation: http://hojtsy.hu/blog/2018-dec-17/how-automate-testing-whether-your-drup... to expose potential code flaws
- [ ] Test the module using umami and the Upgrade Status module
Comment | File | Size | Author |
---|---|---|---|
#6 | 3090751-06.patch | 1.04 KB | wengerk |
#3 | nbsp-3090751-2.patch | 673 bytes | Tolyan4ik |
Comments
Comment #2
Tolyan4ik CreditAttribution: Tolyan4ik at EPAM Systems commented3/3 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
------ ----------------------------------------------------------------------
Line nbsp.install
------ ----------------------------------------------------------------------
16 Call to deprecated function drupal_set_message():
in Drupal 8.5.0 and will be removed before Drupal 9.0.0.
Use \Drupal\Core\Messenger\MessengerInterface::addMessage() instead.
------ ----------------------------------------------------------------------
[ERROR] Found 1 error
Comment #3
Tolyan4ik CreditAttribution: Tolyan4ik at EPAM Systems commentedComment #4
Tolyan4ik CreditAttribution: Tolyan4ik at EPAM Systems commentedComment #5
wengerkComment #6
wengerkHere a rerolled patch with the proper
drupalci.yml
file and the proper Drupal 9 core keycore_version_requirement: ^8.8 || ^9
.Let's see what is deprecated !!
Comment #7
wengerkclosed and fixed since release
8.x-2.0-alpha1
.