Getting a Strange Error
Permalink Browser Info Environment
Using the pagination on this block and the first page (1-10) displays fine but the second and third throw an error...
An unexpected error occurred.
Page "2" does not exist. The currentPage must be inferior to "1"
Am I doing something wrong?
An unexpected error occurred.
Page "2" does not exist. The currentPage must be inferior to "1"
Am I doing something wrong?
Type: | Pre-Sale |
---|---|
Status: | In Progress |
I know this is long forgotten but I think I figured it out or at least what is causing it. The error occurs when there is more than one block that uses pagination on a page. I am currently having the same issue with ProBlog List Block and ProEvents List Block on the same page. I am not sure how to fix this but maybe greater minds than mine can take this info and run with it. I currently have a support ticket submitted for this error (and others within the ProSomething packages) but I have not heard back.
Cheers,
Chris
Cheers,
Chris
I know what you are talking with this.
The pagination within this block is handled by a pagination function built into concrete5, it's not custom written, so there's not much I can do to adjust it.
I seem to recall there being some discussion about making it block specific - are you running a recent c5 version?
The pagination within this block is handled by a pagination function built into concrete5, it's not custom written, so there's not much I can do to adjust it.
I seem to recall there being some discussion about making it block specific - are you running a recent c5 version?
Yup. Even as I was writing that post I was thinking this is all very familiar. I went back in my emails and found the thread. So it looks like the problem occurs when ANY two blocks that utilize the pagination feature (even if it is only turn on in one block and not the other) are on the same page.
Using 5.7.5.9.
Was there any movement on making this change in the core as was discussed in your pull request?
Using 5.7.5.9.
Was there any movement on making this change in the core as was discussed in your pull request?
So i think the change you proposed was implemented for the file list and it no longer conflicts with page lists. But... creating a unique pagination for a file list however also has its faults… while it doesn’t conflict with the page lists, if you wanted more than one file list on a page, clicking page 2 on one file list block’s pagination changes the output for both. Even if the second one has pagination turned off.
What happened to the discussion about making the pagination function block id specific? that seems like the solution (though I wouldnt be able to do it to save my life)
What happened to the discussion about making the pagination function block id specific? that seems like the solution (though I wouldnt be able to do it to save my life)
I'm having trouble replicating this bug on a 5.7.3.1 install, with version 1.0.7 of the package.
Are you using any advanced permissions to control access to the files by any chance?
Are there other parameters on the URL when you try paginating?
Can you supply some screenshots of the block configuration and the result page (including the URL)?
You're welcome to email my directly at ryan@mesuva.com.au
-Ryan