- chances to have a front end paging, whereas a very long text can be automatically splitted in several pages
- a backend paging: 100 articles in the same level are virtually unreadable
- a back end search engine; if i have 1000 pages, remembering where is what it's a bit hard
more to come
some requests from fulvio
- Fulvio Romanin
- Posts: 394
- Joined: Thu 4. Dec 2003, 11:12
- Location: Udine, Italy
- Contact:
some requests from fulvio
Completeness is reached through subtraction, not through addition
I agree Fu - since you have worked on monster sites using wcms
- the backend suggestions are from your own experience.
With regards to frontend pagination -
this is a feature that has been requested for sometime (2years ago).
pSouper put it succinctly,
namely some kind of tag that can be placed inside the article, not unlike
Having said that, the logic to implement it may be outside the scope of standard external reptag logic -
guessing it would have to go into front.func.inc.php or thereabouts.
Your suggestion for auto-pagination is well taken -
but i would like better a auto/manual pagination option.
if page is set to manual pagination
on first visit to full article, wcms looks for {pagebreak} rep tags
if it finds then generates a footer nav scheme:
with "1" highlighted to show current page state.
hrefs would be genenrated in code: index.php?articleparams&page=1, etc
the print version of page would have to disregard this logic and show full article to print out. (Something like macromedia/adobe website and tons of others).
I really think this is an important feature request to make wcms more usable
Also interested in input from others as to where one would start to deving a solution,
since I have a client asking for this feature and i might have to give it a go....even if it requires a hack
(1) Would rewrite rules need to be in effect for this to work?
(2) Where in code would the appending of url be done?
(3) Could frontend init be used to declare a $global, based on intercepted $_GET['page'} ?
(4) How would print this page version logic bypass this in order to printout full article?
Any suggestions would be appreciated.
- the backend suggestions are from your own experience.
With regards to frontend pagination -
this is a feature that has been requested for sometime (2years ago).
pSouper put it succinctly,
namely some kind of tag that can be placed inside the article, not unlike
Code: Select all
{pagebreak}
guessing it would have to go into front.func.inc.php or thereabouts.
Your suggestion for auto-pagination is well taken -
but i would like better a auto/manual pagination option.
if page is set to manual pagination
on first visit to full article, wcms looks for {pagebreak} rep tags
if it finds then generates a footer nav scheme:
Code: Select all
Page: 1 | 2 | 3 >> next
with "1" highlighted to show current page state.
hrefs would be genenrated in code: index.php?articleparams&page=1, etc
the print version of page would have to disregard this logic and show full article to print out. (Something like macromedia/adobe website and tons of others).
I really think this is an important feature request to make wcms more usable
Also interested in input from others as to where one would start to deving a solution,
since I have a client asking for this feature and i might have to give it a go....even if it requires a hack
(1) Would rewrite rules need to be in effect for this to work?
(2) Where in code would the appending of url be done?
(3) Could frontend init be used to declare a $global, based on intercepted $_GET['page'} ?
(4) How would print this page version logic bypass this in order to printout full article?
Any suggestions would be appreciated.
Hi Fulvio, hi John,
please insert such feature request not only here in this forum, insert it also at the phpwcms tracker site at Sourceforge:
http://sourceforge.net/tracker/?atid=60 ... unc=browse
I think OG will scan this tracker site more often than the forum feature request site...
Joachim
please insert such feature request not only here in this forum, insert it also at the phpwcms tracker site at Sourceforge:
http://sourceforge.net/tracker/?atid=60 ... unc=browse
I think OG will scan this tracker site more often than the forum feature request site...
Joachim
Hi Guys,
Well - i created a way to paginate using contentparts
- a little bit of work
- but the flexibility that it allows outweighs the modest requirements.
You can see the post here:
http://www.phpwcms.de/forum/viewtopic.php?t=11956
All best,
-john-
Well - i created a way to paginate using contentparts
- a little bit of work
- but the flexibility that it allows outweighs the modest requirements.
You can see the post here:
http://www.phpwcms.de/forum/viewtopic.php?t=11956
All best,
-john-