Forums / General / Offset Links Not Working

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Offset Links Not Working

Author Message

Alex Jones

Tuesday 24 August 2004 3:14:15 pm

I'm sure this has been answered before, but I cannot find anything via search. I am helping out with a site that I didn't set up, so I don't know what changes have been made that might have caused this problem, please be patient. :)

<b>Problem:</b> In the admin area, I am presented with the exact same set of results for every page when I click on a Next>> link. The offset is reflected in the URL, but the list of children does not change. Nothing shows up in debug mode, and the public-facing Web site doesn't have this pagination problem, so I'm sure it is a template or override setting somewhere, but I don't know where.

<b>System Info:</b>
Exponential 3.4.1
PHP 4.34

A pointer in the right direction would be much appreciated!

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

kracker

Tuesday 24 August 2004 10:25:50 pm

I've had this problem on several occasions before as well.

I experienced this breakdown with the Admin -> Set up -> Advanced -> Templates -> At the bottom the Template List ( Next » 1 2 3 4 5 6 7 ...43 )

Though I've never found a reasonable solution, I also would very much like to hear from others who have encountered this problem before and know just how they resolved the problem.

//kracker
The Way Of The Gun : The Setup

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Alex Jones

Wednesday 25 August 2004 6:22:14 pm

Note, even if I type in the URL manually it doesn't work. For example, if I input the URL: https://mysite.com/PathToAdmin/content/view/full/87/(offset)/15 I am presented with the first fifteen options instead of the next group of items.

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Alex Jones

Wednesday 25 August 2004 6:54:10 pm

Hrrrrm, the problem appears to be due to the parentheses used in the URL, when I hit https://mysite.com/PathToAdmin/content/view/full/87/<b>offset</b>/15 I have no problems.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Alex Jones

Wednesday 25 August 2004 7:23:12 pm

To further answer my own question / ask another one... The issue appears to crop up depending on the value of <i>AllowUserVariables</i> under <i>[ControlSettings]</i> within template.ini. The standard tempalte <i>navigator/google.tpl</i> checks this ini setting and outputs a link format according to the value. If it is set to <i>true</i> then it includes parentheses in the URL, if set to false, they are left out:

offset_text=eq( ezini( 'ControlSettings', 'AllowUserVariables', 'template.ini' ), 'true' )|choose( '/offset/', '/(offset)/' )}

Is this how it is supposed to work? If so, how do we use offset while allowing user variables? If not, what other things could be causing this?

Thanks!

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

kracker

Wednesday 25 August 2004 8:11:56 pm

Boy do I feel dumb,

Alex, (this is all way to familiar)
Only now do I remember replacing /(offset)/ with /offset/ the first time I solved this bug on the eZ Pub.

At the time it seemed like I had done something else wrong. cause . . .

After some searches and reading on ez.no it seemed that eZ systems had internationally switched from /offset/ to /(offset)/ on <b>purpose</b>.

Which I didn't understand, why the new style didn't work for me or why others didn't have the same problems . . . . so the debug session and results didn't stick / make it over into my long term memory.

So . . . Does anyone else care to comment on which style works for them?
Or . . . Possible reasons why the /(offset)/ style would not work?

//kracker

memento

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

kracker

Wednesday 25 August 2004 8:43:41 pm

Well then . . .

Today I was able to place a template.ini.append.php file in the settings/override/ directory which seemed to change the offset link style used in /navigator/google.tpl

It was interesting to find that I could get this file to work if the template.ini.append.php file was in the /settings/override/ it didn't seem to work when the override was only in /settings/siteaccess/YourSiteDesign_admin/ or /settings/siteaccess/admin/ .

-kracker
Eminem : Tylenol

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

kracker

Wednesday 25 August 2004 9:27:26 pm

Then I . . .

Realized that if I could not set the AllowUserVariables for just the admin site design (see above problem posts about the problem) the user site would also get /offset/ style as well which just so happens to break the user site...

Seems like the User site needs the /(offset)/ style and the Admin site needs the /offset/ style. Why can't they use the same style? Why would one style work but the other style would not?

So I avoided the problem by changing my full_folder.tpl's page_limit from 11 to 20 (override: /node/view/full.tpl) which I had planed to earlier anyway to make the site more readable (20 may be a bit large but then i'm avoiding the for mentioned problem with the offset links.

And I still don't quite understand why . .

//kracker

Ice Cube : You Can Do It

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Alex Jones

Thursday 26 August 2004 6:30:22 am

Perhaps it is related to the use of nice URLs as well? I think there may be a correlation. So, for example, the parentheses are used if your URL is mysite.com/blog/(offset)/20 but wouldn't be used for mysite.com/PathToAdmin/content/view/full/87/offset/20

Thoughts?

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>