I'm not sure how to explain this, but it makes more sense for a project I'm working on. This way a view of bio nodes can be created, and when clicking on a node, the user is not redirected, but rather end up on bio node, but if they stumble on the user page, they get the same view as the bio node.
Not sure if it's viable to do this the other way around (redirect profile to node) since there would no option to edit actual user settings, such as email and username, plus missing tracker tabs would be a negative. I'll spend some time and think about that option as well.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | bio_redirect_2.patch | 1.75 KB | mikey_p |
| bio_redirect.patch | 1.7 KB | mikey_p |
Comments
Comment #1
dwwI don't quite understand why you need/want this. Sorry if I'm being dense. The bio node is a tab on the user's profile page. If you select the right box, the bio is displayed directly on the user's page. Why would you ever need to see the bio node "floating" in space, unrelated to the user the bio corresponds to?
Also, shouldn't bio_profile_redirect default to 1 if not defined? Seems like turning this off is the weird use-case. That setting defaulting to 1 won't change anything if bio_profile remains 0, so it seems to be more usable if you change the default, no?
Comment #2
mikey_p commentedHad a reply typed up and I lost it :(
Long story short, my project requires bio fields to be used in path to bio node, and I don't see a way to use those as tokens for users in path auto.
I fixed the patch to match previous behavior, and the 'redirect' option will be disabled unless 'take over profiles' is enabled.
Comment #3
mikey_p commentedstatus change....
Comment #4
mikey_p commentedSo uhh yeah, I think this is a dead end...