Closed (won't fix)
Project:
Role Expire
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
7 Mar 2010 at 19:34 UTC
Updated:
9 Jan 2018 at 19:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
adam_b commentedSubscribe... this is a real pain for my installation as I'm using it for multiple roles, and I can't find a way to work around it.
ETA: can't believe I subscribed to a thread without realising that I'd started in the first place...
Comment #2
stewsnoozeThis is committed to CVS HEAD.
Please review. I'll release soon but test if you can.
Comment #3
adam_b commentedAfraid I've no idea how to work with CVS HEAD, but will look at a dev release as soon as it's available :)
Comment #4
stewsnoozeI've enabled the dev release on the front page of the module but you'll probably have to wait for the packaged version (15th June) to get the views change in there.
Comment #5
adam_b commentedI've installed the 14 June dev version which has the new fields (role expiration name, role expiration time) so I assume it's the correct one.
Looks good in principle but I'm having a couple of problems:
1. It's sometimes showing expiry dates in the view for roles which have no expiry when I check the user
- see attachments view_shows_expiry.png and role_has_no_expiry.png
2. It's sometimes showing the same role multiple times, with different expiry dates in each instance
- see attachment multiple_role_instances.png
We're also having problems with the expiry date seeming to disappear when you try and edit the user. This looks like #561270: Expiration date vanishes if changes are made on other tabs but I haven't been able to replicate it consistently so haven't added it to that issue - I just mention it here in case it's relevant, since our user admin's had to enter the expiry dates over again in some instances.
Comment #6
adam_b commentedPNG's didn't work for some reason so am attaching JPGs
Comment #7
stewsnoozeCan you send me the SQL that Views produced (at the bottom near the Live preview) for this or export the view and send over the .inc file. Lets start with the SQL produced by views
Comment #8
adam_b commentedSQL query:
Views export file attached
Comment #9
stewsnoozeHi,
I realised that I hadn't exposed the relationship to the role table. You should rebuild your role and add the Role Expire Role ID field, then add the available role expiry rid relationship which will enforce the 1 to 1 match.
This should be in the new dev roll up which I hope is dated 21 June.
Feedback please?
Comment #10
adam_b commentedOkay, I'm not sure that I understood the instructions but here's what I did:
- added relationship "User: Role expiration Role ID" and made it compulsory
- added fields:
-- "User: Role expiration Role ID" (not displayed)
-- "(RoleID) User: Role expiration name" (using relationship)
-- "User: Role expiration time"
The result is much better and seems correct for most users. The only problem I've found so far is a couple of users which each have two roles listed although they're only subscribed to one.
SQL query is:
View export file attached -- let me know if you need more information.
Comment #11
stewsnoozeOK. I'll code to expose the relationship to users as well and you'll need to add that in the Relationship tab also. I'll update this later.
Comment #12
adam_b commentedThanks. Could I ask you to indicate specifically which fields need which relationships? I tried a few alternatives and this was the best setting that I could find.
Comment #13
teliseo commentedSee patch in #924976: Administration Report on Expiry Dates for a better solution.
Comment #14
sharplesa commentedPlease check out the patch at http://drupal.org/node/649256#comment-5291110 and see if it doesn't also address this problem.
Comment #15
rcodinaDrupal 6 version is unsupported!