devpci devpci
Registered Users
Nuke Active Member
Posts:42
 |
| 8/22/2007 8:09 AM |
|
HI all,
Any solution to navigate detailed page by detailed page in Full View Mode ?
Can we have the sames tokens in "View Header/Footer" Or "View Item" As in : "Listing Header/Footer"
As if View mode is a Listing mode displaying only 1 detailled page
Thanks for help.
Best Regards
devPCI Team
In the documentation :
View Header/Footer
There are no tokens for this type
Listing Header/Footer
Token Description
[CURRENTPAGE] The current page number of the listings.
[HASMULTIPLEPAGES]
[/HASMULTIPLEPAGES] A region that will only display when there is more then 1 page of listings.
[HASNEXTPAGE]
[/HASNEXTPAGE] A region that will only display when there is a next page.
[HASPREVPAGE]
[/HASPREVPAGE] A region that will only display when there is a previous page.
[LINKFIRST] A link to the first page of listings.
[LINKLAST] A link to the last page of listings.
[LINKNEXT] A link to the next page of listings.
[LINKPREVIOUS] A link to the previous page of the listings.
[PAGECOUNT] The total count of all pages
[PAGES] Displays a list of linked pages for the current listings. |
|
|
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:12446
|
| 8/23/2007 6:51 AM |
|
| You want to view a property and then navigate to the next property? |
|
Scott McCulloch
Site Administrator |
|
|
devpci devpci
Registered Users
Nuke Active Member
Posts:42
|
| 8/23/2007 8:37 AM |
|
Yes, It would be a good first step.
Thanks
|
|
|
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:12446
|
| 8/23/2007 8:33 PM |
|
Hmm, to do this, I would need to pass the search criteria to a detail page, meaning each detail page would have a unique url (based on search criteria).
When you say a good first step, what are the other steps? |
|
Scott McCulloch
Site Administrator |
|
|
devpci devpci
Registered Users
Nuke Active Member
Posts:42
|
| 8/24/2007 1:33 AM |
|
In fact, by "first step" I was meaning that the [NEXT] token should be based on the property id (next property will be current id +1, i.e if I'm on the Property with an id=34, the next would be the property with id=35).
The next step if efectively what you mean (based on a search list results).
To do this you can use search criteria in URL as you said, or perhaps store the id list of property in a session variable type array...
The idea of a unique URL per property is not so bad, cause you could have a more powerful url for search engines and so kill two birds with one stone.
|
|
|
|
|
avi a
Gold Membership
Nuke Master
Posts:651
|
| 8/24/2007 9:10 AM |
|
Posted By smcculloch on 8/23/2007 6:51 AM
You want to view a property and then navigate to the next property?
I think that will be great!
Also if possible a [RANDOMLINK].
Thanks. |
|
Avi A
Nukedesigners.com W3C valid skins for dotnetnuke |
|
|
avi a
Gold Membership
Nuke Master
Posts:651
|
| 8/24/2007 9:25 AM |
|
Also I'm not sure if that is what you are suggesting but a :
click to view all that member list [USERLINKS]
and once we were talking about the "hook" idea: [TEMPLATE:xxxx][USERLINKS]
thanks again.
|
|
Avi A
Nukedesigners.com W3C valid skins for dotnetnuke |
|
|
Ken
Silver Membership
Nuke Super Newbie
Posts:16
|
| 8/24/2007 9:51 AM |
|
Posted By smcculloch on 8/23/2007 8:33 PM
Hmm, to do this, I would need to pass the search criteria to a detail page, meaning each detail page would have a unique url (based on search criteria).
When you say a good first step, what are the other steps?
This might also address one of my requests, which is to allow the formatting of my Detail Page to be different than the Search Page.
|
|
|
|
|
gp
Silver Membership
Nuke Active Member
Posts:42
|
| 5/21/2008 2:15 PM |
|
I find myself on the VIEW page and wishing I had a VIEW.FOOTER TOKEN like [NEXT] or [PAGER]
Did this ever happen?
Thanks, Dave. |
|
|
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:12446
|
| 5/21/2008 5:09 PM |
|
There problem is where to go for next/previous? I don't think going to the next PropertyID is a good solution as this maybe in another portal.
When view a property, you may come from a search page, a view type page or another module such as latest.
You could always go to the next property in choosen type (based on default sort order). This maybe confusing however, if someone did a search and arrived at a page that has next/previous for the current type. |
|
Scott McCulloch
Site Administrator |
|
|
gp
Silver Membership
Nuke Active Member
Posts:42
|
| 5/22/2008 1:42 PM |
|
I vote for this. Idea is to keep user interest going and getting to see another similar property with one click! This is a winner.
You could always go to the next property in choosen type (based on default sort order). This maybe confusing however, if someone did a search and arrived at a page that has next/previous for the current type. |
|
|
|
|
Jose Maldonado
Gold Membership
Nuke Active Member
Posts:37
|
| 5/29/2008 4:18 PM |
|
last idea of smcculloch is good idea, to sail by categories would be very good. |
|
|
|
|