station/programs/schedule cannot be added to primary links through views interface
cookiesunshinex - June 6, 2009 - 11:52
| Project: | Station |
| Version: | 6.x-2.x-dev |
| Component: | Other |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
After I upgraded from 5.x to latest 6.x dev, I edited the default view station/programs/schedule
I made a couple of modifications: (even after reverting to view default in case there were problems upgrading the view itself).
1. Enable the program Title to link to it's node (I think this should be a default).
2. Added Time - Day Time Range
When I tried to add the view to the primary links, it updated ok and I saved the view, but when I went back to the main page, the item wasn't there.
I manually went in through the menu's interface and added it.
I tried this 2 or 3 times to make sure that it wasn't just me.
#1
Yeah that view is kind of broken (the linked to node is really annoying I keep forgetting to commit a fix for it) pending #477712: View - Station Program: Scheduled filter no longer available in 6.x-2.x-dev since there should be two views, scheduled and unscheduled. Scheduled would have the air date and unscheduled would not.
#2
actually I'm not sure why you wouldn't be able to add it since that's exactly the way that I put it into the menu system...
I've just committed the attached which fixes the problem with the program title not linking to the node. I did a little testing and couldn't get the scheduled times working the way I'd want. I need to work on the Views support some more before I can finish that.
#3
I applied that...and I see what you mean regarding the times.
Originally, I added the "Time - Day Time Range" as the last column on the right in the view. I realized that it made more sense to add it as the first column on the left (as the default station/day view does).
When I viewed station/programs/schedule I realized that they were not in sequential order for some reason.
#4
i think this was fixed in some other issues/commits.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.