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.
I will submit a patch that implements og_moderation handling revisioning permissions. This patch depends on code that is in DEV branch of revisioning. It was added just after the last build was released.
Comments
Comment #1
pgillis CreditAttribution: pgillis commentedComment #2
pgillis CreditAttribution: pgillis commentedNeeded to make more resilient to the callers.
Comment #3
pgillis CreditAttribution: pgillis commentedCleaned up patch a bit. I realized some of the records weren't needed now that the Revisioning module has been updated.
Comment #4
shenzhuxi CreditAttribution: shenzhuxi commentedI add module_exists('revisioning') checking.
Please test it.
Comment #5
pgillis CreditAttribution: pgillis commentedHi,
Thanks for looking at this. If I understand what you were intending to do, shouldn't we also move the 'publish revisions of own " . $info->type . " content' permissions under the module_exists conditional?
Comment #6
pgillis CreditAttribution: pgillis commentedThe hook signature was updated in revisioning module, so the last two parameters are no longer passed in.
Comment #7
pgillis CreditAttribution: pgillis commentedUpdated patch, missed reference to $account after signature change.
Comment #8
pgillis CreditAttribution: pgillis commentedI've realized that this use case may be more specific than you want to include in your module. That is fine, I can implement these two hooks in my own module and just use what you already have released for og_moderation for the functionality it provides. Thanks...
Comment #9
shenzhuxi CreditAttribution: shenzhuxi commentedcommitted
Please test the latest dev carefully, because I committed 3 patches at the same time.
I'm sorry I was in vacation for one month and didn't pay attention to the project.
Comment #11
pgillis CreditAttribution: pgillis commentedHi, sorry for the late response! I had moved to implementing in local module because of how often the code would change with changes to other modules. I will open a separate request about integration with the node_clone module. That said, I ran into a few problems since my previous patch and have updated here.
Long story short, if you think this functionality belongs here, I am fine with that and will continue to supply patches where I think something is wrong. If not, I understand, and can maintain this hook in a separate module. Does that make sense? Thanks again for your help!
Comment #12
pgillis CreditAttribution: pgillis commentedCommitted code to 7.x-2.x branch.