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.
These date back from 7.x-2.x:
'description' => 'The flag type, usually one of "node", "comment", "user".',
...
'description' => 'The unique ID of the content, usually either the {cid}, {uid}, or {nid}.',
The flag type can be any entity type. We can say something like "for example, 'node' or 'comment'". For the ID, we should just say something like 'the unique ID of the flagged entity'.
Comment | File | Size | Author |
---|---|---|---|
#11 | antique_field_drupal7_backport-2466539-11.patch | 1.87 KB | joekers |
#6 | antique_field-2466539-6.patch | 769 bytes | joekers |
#2 | antique_field_drupal7_backport-2466539-2.patch | 1.86 KB | joekers |
#1 | antique_field-2466539-1.patch | 765 bytes | joekers |
Comments
Comment #1
joekersHere's the Drupal 8 patch. I've never done a backport before - I guess I just create a patch for 7.x-3.x and upload it to this issue?
Comment #2
joekersHere's the 7.x-3.x patch.
Comment #3
joekersComment #5
joachim CreditAttribution: joachim commentedGreat, thanks!
One thing though: curly braces go on table names, but not on table column names. So they're not needed here. I'd add a 'the' here too: 'for example, the uid, cid, or nid.'
And for backports: yup. It's sometimes best to wait till the first patch is committed, and then backport it though, as it can save work! :) Furthermore, there is a possibility that the commit for the current branch can be git cherry-picked, requiring no further patch work. I'd say that's fairly likely here.
Comment #6
joekersOk I've made the changes from above. I'll leave the backport for now.
Comment #7
joachim CreditAttribution: joachim commentedLet's get the testbot to look at it just to play safe :)
Comment #8
joachim CreditAttribution: joachim commentedCommitted.
Thanks again for working on this :)
Comment #10
joachim CreditAttribution: joachim commentedSadly, the cherry-pick doesn't work at all, so we'll need a backported patch.
Comment #11
joekersHere's the D7 patch - the fields are used on other tables (not just the flag_counts table) so I updated those descriptions too. Is it worth me adding a hook_update_N() to update these field descriptions for users that already have the module installed?
Comment #12
joachim CreditAttribution: joachim commented> Is it worth me adding a hook_update_N() to update these field descriptions for users that already have the module installed?
No, I wouldn't think so.
Comment #13
joekersI haven't checked back on this in a while - is there anything else I need to do?
Comment #14
joachim CreditAttribution: joachim commentedNothing except nudge the maintainer, which you've done :)
Committed to 7.x-3.x. Thanks again!