As I went through the module I came across a few issue.
- When anonymous user views the 'Claim' link it should be the user/register page, though it still is the claim link; hence claims by anonymous users are saved.
- After a claim is approved, users can still see the claim link, users you had previously applied for claiming the node still see 'Claim Pending'
- Saving the claim is triggered on registering a new user, where as it should be triggered when user has just logged in and then check if the $_SESSION variable has the key 'nodeownership' set
- There was no need of attaching the claim form with the register form since a site builder might already have similar fields in their register process. Besides the claim form can easily be shown after the user is logged in and then the claiming process will proceed as usual
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | nodeownership-multiple_fixes-1866532-5.patch | 5.3 KB | robcarr |
| #4 | nodeownership-multiple_fixes-1866532-4.patch | 5.31 KB | robcarr |
| #2 | nodeownership-multiple_fixes-1866532-1.patch | 6.07 KB | SGhosh |
| #1 | nodeownership-multiple_fixes-1866532-1.patch | 6.07 KB | SGhosh |
Comments
Comment #1
SGhosh commentedIncluding the patch in this comment.
Patch also contains -
Configuration settings from admin ui for - Claim and pending claim texts.
Comment #2
SGhosh commentedSubmitting patch for review. (Setting status to Needs Review)
Comment #3
robcarrPatch fails:
The version (7.x-1.3) I downloaded has the line (339)
Whereas the patch is trying to replace a line:
This module seems to have caused a lot of problems with the menu system. Lack of a DEV release and config control may also be a wider problem with this module too.
Will attempt a new patch later on.
Comment #4
robcarrUpdated patch attached.
Feeling less comfortable with the use of the View that comes as part of this module - it's not a particularly robust approach. If, for example, the site builder changes the path of the View (or clones the View for deeper customization) - all easy to do in the Views UI - then a lot of the
drupal_gotocalls will fail.It would be better if this module came with a disabled View (for cloning etc), but also came with a hard coded table fixed to the path /admin/content/claims
Comment #5
robcarrMy bad - disregard the last patch - URL typo.
Comment #6
SGhosh commentedI changed the redirect path to the list of claims, I suppose this should have been so in the first place and not redirect to the admin settings page, isn't it?
Comment #6.0
SGhosh commentedAdded another issue
Comment #8
grasmash commentedMost of this has been committed. However, I removed the check for claim status, as it prevents a node from being claimed more than once, which is a valid use case. Such a feature would need to be configurable.