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.
Deprecated method urlinfo removed from codebase
Comment | File | Size | Author |
---|---|---|---|
#5 | interdiff.txt | 54.1 KB | deepakkumar14 |
#5 | tokens-merged_patches-2858253-5.patch | 62.2 KB | deepakkumar14 |
#4 | tokens-merged_patches-2858253-4.patch | 5.63 KB | rjjakes |
#2 | token-2.patch | 5.83 KB | pifagor |
Comments
Comment #2
pifagorComment #3
BerdirThere are a lot of issues about replacing deprecated function call replacements, some only change a single thing, that might make sense in core when there are lots of such calls, but not in a module like token. This is a lot of overhead for me and also for you and looks like gaming/mis-using the credits system.
I'd appreciate it if you combine all your current issues into one, close the others as duplicate and provide a single patch that combines them all. Thank you.
Comment #4
rjjakes CreditAttribution: rjjakes at Acquia Site Studio commentedI have merged all the open "deprecated" patches and fixed the service issue from here: https://www.drupal.org/node/2858274
Comment #5
deepakkumar14 CreditAttribution: deepakkumar14 as a volunteer and at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedThanks rjjakes i have reviewed the patch in #4 but its doesn't replace all the urlInfo() method with toUrl() and i also get the t() function deprecated in module so i create a patch for replacing all urlInfo() with toUrl() and t() with $this->t().
Comment #7
rjjakes CreditAttribution: rjjakes at Acquia Site Studio commented@deepakkumar14 - seems like a lot of the tests don't like $this->t() perhaps because they're being called as statics to $this doesn't exist? (A guess at this point).
I was under the impression that calling t() as a global was fine - it' definitely not deprecated: https://api.drupal.org/api/drupal/core%21includes%21bootstrap.inc/functi...
Comment #8
MatroskeenI would recommend closing this one. The issue is no longer persists, probably it was fixed somewhere else.
Comment #9
Berdiryeah, it was, must have missed this one as I was combining issues together.