Closed (fixed)
Project:
Node Ownership
Version:
8.x-1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
18 Jul 2011 at 14:55 UTC
Updated:
5 Aug 2016 at 05:54 UTC
Jump to comment: Most recent
The claim link on the node is always there despite whether it has been claimed or not!
If ownership of a piece of content is granted to a user, then the claim link should not be displayed anymore.
Comments
Comment #1
franzkewd commentedSubscribe
Comment #2
vyasamit2007 commentedHello,
We have generalized this concept of claiming the node/content and allowed other users to claim the node also, I mean, If one user has claimed the node but another user came and wanted the ownership then Administrator has to look for who is the better option who can own the content and make one of them the owner. In this way the old owner will now not get permissions to own the content.
BUT I agree with you about the claim link, I'll keep this in our Feature request list and will give the setting for administrator to set for each content that it is one time claim or not. In this way we can keep any content type one time claiming or multiple times claiming.
I'm assigning this to the maintainer who is building a new release for node ownership.
Thanks!
Comment #3
gauravkumar87 commentedComment #4
asdLArs commentedIf the node is owned by the active user it should not display the claim link.
Comment #5
markusa commented+1 this would be a good feature.
Or if there was a per user node limit on claims....
Or if there was a way to set some property to differentiate unclaimed nodes and once they are claimed to not show link. Say you are importing 100000 nodes using one user. Then you may have users come and claim the nodes but once they are claimed not display or even allow claiming of that node.
For example say you are building a restaurant directory and build up basic listings for all the cities in texas...then you might invite the restaurant owners to create an account and claim their listing to update it.
Comment #6
vyasamit2007 commentedThis now works fine in D7 & D8 of this module. We're not fixing any issues for D6.
Thanks!!
Comment #7
vyasamit2007 commented