Closed (fixed)
Project:
Real Name
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Dec 2019 at 22:39 UTC
Updated:
2 May 2021 at 17:52 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gnanagowthaman sankar commentedHi @gmangones,
Here by i attached the patch. Please review and let me know for changes.
Thanks & Regards,
Gnanagowthaman sankar
Comment #3
gnanagowthaman sankar commentedPatch
Thanks & Regards,
Gnanagowthaman sankar
Comment #4
manuel garcia commentedThe test has a more complete patch on https://www.drupal.org/project/realname/issues/3115617
Comment #5
mrpauldriver commentedIn addition to this issue, there are two othes tagged with Drupal 9 compatibility
Probably best if comments and contributions are focused here.
The project page says "Real Name 8.x-1.0-rc2+ supports Drupal 9. Enjoy."
However, when testing with Upgrade Status module, a number of problems are reported. Do these need further attention?
to │
│ manually │ │ realname.info.yml to designate that the module is compatible │
│ │ │ with Drupal 9. See https://drupal.org/node/3070687. │
│ │ │ │
└──────────┴──────┴──────────────────────────────────────────────────────────────┘
Comment #6
zvonimirrThis patch (when used in conjunction with https://www.drupal.org/project/realname/issues/3115617) passes both Upgrade Status and Drupal Check.
Comment #7
mrpauldriver commentedConfirm this passes tests by Upgrade Status module when used with the additional patch mentioned in #6
Comment #8
mrpauldriver commentedComment #9
edycarreyes99 commentedIt still has errors and deprecated codes and I fixed it on the next patch:
Comment #10
heddnCan someone manually run the tests on a D9 site? That would give me some greater assurance the module is functional in D9.
Comment #11
heddnIf we update the composer.json to include drupal/core ^8.0 || ^9.0, then the testbot will let us run tests on D9. This is a recent change as of yesterday.
Comment #12
eduardo morales albertiPatch #9 applied using composer, review using module upgrade status, add a new test to the patch for test on drupal 9.
Comment #13
heddnI've manually tested the patch. This is good to go now.
Comment #14
sutharsan commentedPlease create a new release that includes this patch. Much appreciated.
Comment #15
rp7 commentedI've tested the patch. Looks good. Can we get this in?
Comment #16
Christopher Riley commentedAny idea when this will actually be committed?
Comment #17
seanbWhen trying to update to D9 with the patch version I get the following error:
I suspect it is because of the composer.json in the module. Do we really need the composer.json file?
Comment #18
jplana commentedDocumentation states "Real Name 8.x-1.0-rc2+ supports Drupal 9" but the reality is that it currently doesn't.
Looking forward for this patch to be committed upstream 🤞
Comment #19
bohus ulrych+1
Comment #20
megachrizI think this module needs a new co-maintainer, because one of the current maintainers said that they are not actively monitoring issues: #3095041: Is Real Name still being maintained?.
The person who has been the most active maintainer for this module in recent years - hass - has been blocked.
Comment #21
sutharsan commentedLooking at the state of the issue queue and the activity of the maintainers I agree with @MegaChriz, good suggestion. Do you want to maintain this module MegaChriz? Lets start https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...
Comment #22
megachrizNot right now. I'm focussing on getting other modules ready for Drupal 9 first. After that, I'm happy to help to get a D9 compatible release out - and make sure that tests are passing on Drupal 9. In the long run, I'm not planning to actively maintain this module because I already have my hands full on other modules.
Comment #24
chaseonthewebMade a issue fork using the patch from #6. No further changes have been made.
I did not include the changes from #9 as they're already addressed in #3115617: Convert RealnameBasicTest to PHPUnit
This will help admins who want to use the Composer strategy from How to Fix the Catch-22 Problem of Drupal 9 Fixes in Composer. In brief:
edit: fixed #25
Comment #25
kristen polThanks for the steps but one typo:
dev-3150733-drupal-9-compatibilityshould be:
dev-3101961-drupal-9-compatibilityComment #26
philltran commentedGreat work everyone. I can't wait to see this committed to the module.
Comment #27
rp7 commentedWhat are the remaining steps to get this in? Are we missing a maintainer? If so I'm willing to step up.
Comment #28
sutharsan commented@rp7 I appreciate your offer. none of the past maintainers appear to be active, I suggest to contact them directly to see if they can provide you permissions. Either that or follow the abandoned module procedure.
Comment #29
rp7 commentedI just noticed #3201029: Offering to co-maintain Real Name. Apparently other people willing to step up as well. I contacted NancyDru directly to have a look at that ticket & make someone maintainer. Hopefully it gets noticed.
Comment #30
philltran commentedI was just added as co-maintainer. I will work to get a D9 version committed this weekend.
Comment #32
philltran commentedThanks for everyone's work on getting this D9 ready.
I will approve the merge request for patch 6 that was made into an issue fork by @chaseontheweb.
I will address in the update to the phpunit test in Issue #3031066
Comment #34
philltran commentedComment #36
P44T commentedHi Phil, thank you for your effort in making this module D9 compatible!
I'm just wondering, is there any chance that this module will see a release anytime soon? I noticed there's a dev version, but of course that's only usable for development scenario's as this particular version can be updated anytime. It would be very useful if there would be a at least one alpha/beta/rc release that's D9 compatible in the mean time.
Comment #37
philltran commented@P44T Sorry for the delay. I will try my best to get a beta release up this week.
Comment #38
megachrizWhile a new release would be great, I see that the latest commit introduced syntax errors:
https://www.drupal.org/pift-ci-job/2049005
Better to fix these first before creating a new release.
Comment #39
philltran commented@megaChriz Thanks for your attention to detail.
I plan on running coding standards listing and switching to somatic versioning for a D9 beta release.