dawn at dawnthots
Jun 27, 2011, 10:52 AM
Post #13 of 13
(854 views)
Permalink
|
On 2011-06-27, at 7:25 AM, Zdravko Balorda wrote:
> Dawn,
> thanks. I haven't got that far yet. I'm still at concept level. I've always had one
> cover page. Having more requires some defined context to distinguish which stories
> apply to each page. Chronologically setting two dates, or a date and time period is
> simple, then perhaps author context comes handy, too. And perhaps other. And maybe
> the most difficult issue would be navigating through all these (possibly quite many)
> cover pages.
Well you could do anything to navigate all these cover for issues (I assume) -
first load an array with all the cover story objects (sort by cover date perhaps)
my @issues = $story->list({
element_key_name => 'cover_story',
# category_id => $category_id,
unexpired => 1,
publish_status => 1,
Order => 'cover_date',
OrderDirection => 'DESC',
});
then output this lists as you like, a story with thumb nails of their cover images?, a drop down options list, ect.
You can see what I did for the LRC http://reviewcanada.ca/magazine/archive/
These are actually broken in to sub-arrays - sorted by year.
Dawn
> So, a hint or two is invaluable.
> Zdravko
>
> Dawn Buie wrote:
>> Let me know if you want some template code to demo how to do and relate things.
>> Dawn
>> On 2011-06-24, at 1:30 AM, Zdravko Balorda wrote:
>>> Hi,
>>> yes, you gave me a good starting point. You have segmented issues
>>> by dates, so every issue has it's own cover page with current stories.
>>> I don't use dates in OC so I forgot all about it. :)
>>>
>>> Dawn Buie wrote:
>>>> Or set up your output channel url to show /vol/issue/ numbers.
>>> I don't know how to put there any other number except %d, %m, %y, in OC.
>>> My first thought was to use subdomains for vol/issue in front: vol.issue.pub.com/...
>>> and make a site copy every time an issue is published. But using many
>>> cover pages is more clever.
>>>
>>>
>>>> Is that helpful?
>>> Thanks, Zdravko
>>>
>
|
