Active
Project:
Chaos Tool Suite (ctools)
Version:
7.x-1.2
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Oct 2012 at 19:15 UTC
Updated:
27 Oct 2012 at 06:15 UTC
Hi,
User: Bundle as Selection criteria in page manager not working at-all ... tell me how should I processed if one of my varient selection criteria is this...
Have a look the attachment of my implementation ...
as my page url is domain-name/testpage/1(simple admin user id) ... but it gives page not found only when that selection rule is assigned to this test variant of page manager..
It seems to me that User is not treated as bundle as far entity!
| Comment | File | Size | Author |
|---|---|---|---|
| user-bundle.png | 8.54 KB | roynilanjan | |
| seletion-rule-User-Bundle.png | 17.84 KB | roynilanjan |
Comments
Comment #1
merlinofchaos commentedThe 'user' entity doesn't really have bundles and as far as I know, attempts to make the user entity support bundles are doomed to failure. The test for entity bundle type, however, doesn't really actually know that.
So all users have the same bundle: "User". Which means that for any actually existing user, this test should always pass.
However, there is an extra wrinkle here: It's possible the "logged in user" might not actually even have a bundle, so it's vaguely possible this might entirely fail.
That said...because the user entity doesn't support bundles, it doesn't really matter. You can't actually test anything useful.
Given all that, I don't see how this could possibly be critical in *any* case, since this should be reserved for when a suite of software doesn't work at all or causes whitescreens or data loss. None of these is applicable.
Reducing to minor. It might be necessary to have this access rule test to see if there is more than one bundle available and not make the test available if that is the case; then you wouldn't actually see the test when it is not appropriate.
Comment #2
roynilanjan commentedSo all users have the same bundle: "User". Which means that for any actually existing user, this test should always pass
=> NO this test is still fails I'm giving you more details of my test,
In my scenario(which I mentioned before) admin is an existing user
what I try to pass user-id(used-id context is taken at argument) as a bundle(User: ID is bundle "User") in selection criteria
but still rule doesn't satisfy...in any circumstances as a bundle only selection criteria is not satisfied!
Important note if criteria = > NOT (User: ID is bundle "User") then rule satisfy means not bundle!
Comment #3
merlinofchaos commentedIn both of your images, the user you're passing is "Logged in user", not the user from the argument.
Comment #4
merlinofchaos commentedAnd for the reason that users can't have bundles, I'm reducing this to minor again, because whether or not this particular selection criteria functions is irrelevant. Whether it comes out true or false, it will always come out the same way.
Comment #5
roynilanjan commentedIn any case(Logged in user/or pass user-id from argument) which is related to Bundle is false => selection criteria not satisfy...because only reverse property(Reverse (NOT)) satisfy means bundle is not working at all