1
ferr
help with [pagebreak]
  • 2005/3/4 8:05

  • ferr

  • Just popping in

  • Posts: 5

  • Since: 2002/10/17


if i use [pagebreak] tag with wf-channel automatically in the page appear the numbers for navigation (page 1,2,3 >> ) but that does not happen with wf-section.
The page turns out interrupted in the point of insertion of the[pagebreak] tag, but then, I do not know how move between the segmented pages.
The same thing happens with [title]TitleText[/title]
What I can do?
TKS again
PG Ferr

2
rowdie
Re: help with [pagebreak]
  • 2005/3/4 8:52

  • rowdie

  • Just can't stay away

  • Posts: 846

  • Since: 2004/7/21


Two questions :
- Which version of WF-section are you using?
- Have you made changes to the article template?

3
ferr
Re: help with [pagebreak]
  • 2005/3/4 18:17

  • ferr

  • Just popping in

  • Posts: 5

  • Since: 2002/10/17


i use 2.01 version.
i have not made changes to the article template, can you tell me what i must do?
TKS
Pgf

4
Mithrandir
Re: help with [pagebreak]

Are you sure WF-Sections supports [pagebreak] tags?

5
ferr
Re: help with [pagebreak]
  • 2005/3/5 8:48

  • ferr

  • Just popping in

  • Posts: 5

  • Since: 2002/10/17


i have read that both 2.01 and 2.07 version support [pagebreak].
But i think that it is necessary to change article template.I am not sure and i like somebody's help
PGFerr

6
rowdie
Re: help with [pagebreak]
  • 2005/3/5 10:47

  • rowdie

  • Just can't stay away

  • Posts: 846

  • Since: 2004/7/21


I haven't had any problems using pagebreak with the WF-section betas, and I've just installed and tested WF-Section 2.1 which works too. So I'm a bit confused as to why it's not working for you

You don't need to change any templates, the ones included with wf-section have this:

<{if $pagenav !=''}> 
<
div align "right"><b><{$lang_page}>:</b>&nbsp;<{$pagenav}></div><br /> 
<{/if}>
which is the bit that shows the page navigation.

Some more questions...
- Are you using the maintext area to input your article text? Or are you using the html doc bit? I'm asking because I saw that the page nav code only checks the maintext area...

- Have you tested it with a very simple text?
This is the first page...

[
pagebreak]

And 
this is the second

If that works then the problem must have something to do with your article text... then it's just a matter of working out exactly where it goes wrong.

- Which version of XOOPS are you using? The page navigation class wasn't included in earlier versions of XOOPS, just wondering if that could be the problem.