Offset navigator and URL

Next topic

Author	Message
Rebecca Denham	Friday 20 March 2009 2:16:37 am We have a large multi-lingual site developed with eZ version 401 which includes forum topics and discussions. On the forum pages we display up to 50 discussions per page and then use the standard google navigator template for viewing subsequent pages. The URLs for the subsequent pages are displayed in the standard eZ format as ".../(offset)/50". Is it possible to modify this URL format for the subsequent pages to display just the page number instead of the user parameter name/value pair? For example, if a forum discussion includes 3 pages, the google navigator would display pages "1 2 3" with the URLs formatted as ".../(offset)/50" and ".../(offset)/100" for pages 2 and 3 respectively. I would like the URLs to be formatted as ".../2" and ".../3" for pages 2 and 3 respectively. Thanks in advance for any suggestions.
Jean-Yves Zinsou	Friday 20 March 2009 4:08:03 am Hi there, i don't know it this is possible in a simple way because the (offset) parameter in your url is used as view parameter in the template code to compute where to start the fetching of the nodes to list ;-( The only way i can think of achieving this , is to make an extension with a module that takes the offset as ordered parameters ... Is it worth it ? Any other suggestion someone ? Jey Do Androids Dream of Electric Sheep? I dream of eZpubliSheep.... ------------------------------------------------------------------------ http://www.alma.fr
Benjamin Lorteau	Wednesday 01 July 2009 6:32:15 am First of all you can change the way that offset is handled, by modifying the template to accept page numbers instead of offset number. You would have to compute the offset passed in the fetch function, and modify navigator/google.tpl behavior to display page numbers instead of offsets in the generated links. Then you could use Wilcards URL to transform something like /Forum/Topic/(page)/2 into /Forum/Topic/2 eZ Publish personal project : http://www.aeriesguard.com [fr]

Author

Message

Friday 20 March 2009 2:16:37 am

We have a large multi-lingual site developed with eZ version 401 which includes forum topics and discussions. On the forum pages we display up to 50 discussions per page and then use the standard google navigator template for viewing subsequent pages. The URLs for the subsequent pages are displayed in the standard eZ format as ".../(offset)/50".

Is it possible to modify this URL format for the subsequent pages to display just the page number instead of the user parameter name/value pair? For example, if a forum discussion includes 3 pages, the google navigator would display pages "1 2 3" with the URLs formatted as ".../(offset)/50" and ".../(offset)/100" for pages 2 and 3 respectively. I would like the URLs to be formatted as ".../2" and ".../3" for pages 2 and 3 respectively.

Thanks in advance for any suggestions.

Jean-Yves Zinsou

Friday 20 March 2009 4:08:03 am

Hi there,
i don't know it this is possible in a simple way because the (offset) parameter in your url is used as view parameter in the template code to compute where to start the fetching of the nodes to list
;-(

The only way i can think of achieving this , is to make an extension with a module that takes the offset as ordered parameters ...

Is it worth it ?

Any other suggestion someone ?

Jey

Do Androids Dream of Electric Sheep?
I dream of eZpubliSheep....
------------------------------------------------------------------------
http://www.alma.fr

Benjamin Lorteau

Wednesday 01 July 2009 6:32:15 am

First of all you can change the way that offset is handled, by modifying the template to accept page numbers instead of offset number.

You would have to compute the offset passed in the fetch function, and modify navigator/google.tpl behavior to display page numbers instead of offsets in the generated links.

Then you could use Wilcards URL to transform something like

/Forum/Topic/(page)/2

into

/Forum/Topic/2

eZ Publish personal project : http://www.aeriesguard.com [fr]

eZ debug

Timing:	Jan 31 2025 04:18:19
Script start
Timing:	Jan 31 2025 04:18:19
Module start 'layout'
Timing:	Jan 31 2025 04:18:19
Module start 'content'
Timing:	Jan 31 2025 04:18:19
Module end 'content'
Timing:	Jan 31 2025 04:18:19
Script end

Main resources:

Total runtime	0.0138 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	588.1250	151.2109
Module start 'layout'	0.0053	0.0022	739.3359	36.6328
Module start 'content'	0.0076	0.0049	775.9688	90.2188
Module end 'content'	0.0124	0.0013	866.1875	33.9922
Script end	0.0138		900.1797

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	17.2021	14	0.0002
Check MTime	0.0011	8.0308	14	0.0001
Mysql Total
Database connection	0.0007	4.8993	1	0.0007
Mysqli_queries	0.0023	16.7493	3	0.0008
Looping result	0.0000	0.0795	1	0.0000
Template Total	0.0010	7.1	1	0.0010
Template load	0.0008	5.8792	1	0.0008
Template processing	0.0002	1.1682	1	0.0002
Override
Cache load	0.0006	4.4725	1	0.0006
General
dbfile	0.0012	8.9346	8	0.0002
String conversion	0.0000	0.0588	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs