Re: Extension - Next Page
mmm maybe this can be done with catalog extension module. Scare, Thyon what do you think?
Re: Extension - Next Page
Well, using catalog would require too much work with little added value. Adding new inserttags would be better IMHO. Something like {{link::firstchild}}, {{link::lastchild}}, {{link::nextsibling}}, {{link::prevsibling}}, {{link::firstsibling}}, {{link::lastsibling}}, {{link::parent}} and corresponding {{link_url}} tags.
Re: Extension - Next Page
I believe Leo already implemented this?
Re: Extension - Next Page
Did he? I looked at the last version and it is not implemented there. Maybe in trunk?
Re: Extension - Next Page
scare, I wasn't talking about the inserttags, but the feature in general.
Have you looked at the 2.7 feature:
- Added module "book navigation"
This generates a page-like nav, e.g. UP, Prev, Next. So you can navigate pages like well, pages in a book.
Re: Extension - Next Page
Hi Thyon,
I think Valentin means something different: when you set up an internal redirect page, you have to choose a target page for the redirect (else you'll get an error in the frontend calling the redirect page). Valentin wants the redirect to aim automatically at the first child page of the redirect page, when no target is chosen.
Not a bad idea, could be done with an extension, I think. frontend > PageRedirect would have to be extended and possibly backend > dca > tl_page (to make it an option in the backend). I have a customer, who has difficulties with that. Maybe I give it a try...
cheers
Antipitch
Re: Extension - Next Page
But that module already contains the code to retrieve the next page, eg child. It can just be hacked out.
Re: Extension - Next Page
Sorry, I meant the frontend > PageForward class. Can't see any child-page fallback in there though, generate() looks for the jumpTo entry or dies. So where would that
Quote:
that module already contains the code to retrieve the next page
be (didn't look at the dca code yet)?
cheers
Antipitch