Posted by Oleksa on October 13, 2009 at 6:57pm
Jump to:
| Project: | Views attach |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
In profile settings there is option for new profile tabs and it is mentioned there:
The name of the profile tab this view should be listed in. If empty, it will be displayed on the main profile tab.
For me it works only if this option is empty and my views in this case is displayed on main profile page.
If I try to create new tab - nothing happens on profile page.
Comments
#1
Hm. That's because the UI is wrong. :-) Profile displays show up on the main user page, not on tabs. If you want a whole tab just to the view, just use a page display like normal.
#2
thx, a lot, Larry,
i added "Page display",
and in tab path i put :
user/%/pictures and i got what i needed )
#3
Can I attach tabbed views on node content display?
I have artist content type, which i am using as node reference in album and tracks. I need to show two views on artist detail page showing all his tracks and all his albums. So that would be two views in separate tabs, node content display doesnt allow you to create tab entries and I understand why. Any ideas on how can I go about it?
My artist detail page is laid out as follow:
Node Title (Artist name)
Node Body (Description)
Tab 1 (Albums) | Tab 2 (Tracks)
Thanks in advance and strange why this issue is not closed by usual 2 week updates :)
#4
dipen, that is a new issue. Please do not hijack threads. Open a new issue instead.
#5
Apologies, will be mindful of it in future. I thought it was sorted and searching on issue queue this was the only issue that closely resembled my query.
#6
Another request for changing the text in this Profile option for views. Lost some time figuring out that this did not imply creating a tab.
#7
Indeed, they only appear on different tabs when editing the user profile. I've committed a fix to the UI text. Thanks!
#8
Automatically closed -- issue fixed for 2 weeks with no activity.