getPagination options

0

I think it would be great if there were a few more options for the getPagination function.

At the moment the pagination on my pods page looks like:

Go to page: 1 2 3 6

or Go to page: 1 3 4 5 6

It would be great if you could do something like:

Go to page: 1 2 3 4 5 ... Last >>

or Go to page: << First ... 3 4 5 6 7 ... Last >>

The options could include:

i) The divider you want to use ('...' in my examples above) ii) Text for First Page and Last Page links iii) Maximum number of page links you want to show (5 in my example above)

asked Apr 19 '10 at 6:47

samburdge

1

add comment
enter at least 15 characters
most votes oldest newest

4 Answers

1

Perhaps this will help you:

http://www.openscriptsolution.com/2009/09/24/improving-pagination-feature-in-pods-cms-of-wordpress/

answered Apr 19 '10 at 8:48

Masino Sinaga

41

Masino, your new code worked beautifully for the front end of the site, and was a big improvement on the default pagination, so thank you for that. However, it screwed up the Pods admin area, and meant that it was not possible to add or edit any pods where the browse list involved paging. So if I have 40 records in Pod A, but only 3 records in Pod B, I would be able to add and edit records to Pod B (because there's only 1 page in the admin browse mode, and pagination.php isn't invoked), but I would NOT be able to add or edit Pod A records - because listing them in the admin involved pagination. When I returned to the default pagination.php everything worked again. Can anyone else confirm this? I'm using Pods 1.9.4 on WP 3.0.5. Which version did you write the new pagination.php for? I see that you posted your message almost a year ago, so perhaps everything worked okay on the version you used at the time, but changes made since then have had an effect on how the pagination work? – Simon Apr 13 '11 at 10:01
add comment
enter at least 15 characters
0

Great tweek Masino. Just what I was looking for.

answered Jul 28 '10 at 1:08

bjornet

1

add comment
enter at least 15 characters
0

Sorry, I know this is a repeat of my previous comment, but I added it as a comment rather than a reply, so it'll just end up buried and unnoticed! Here it is as a proper comment:

Masino, your new code worked beautifully for the front end of the site, and was a big improvement on the default pagination, so thank you for that. However, it screwed up the Pods admin area, and meant that it was not possible to add or edit any pods where the browse list involved paging. So if I have 40 records in Pod A, but only 3 records in Pod B, I would be able to add and edit records to Pod B (because there's only 1 page in the admin browse mode, and pagination.php isn't invoked), but I would NOT be able to add or edit Pod A records - because listing them in the admin involved pagination. When I returned to the default pagination.php everything worked again.

Can anyone else confirm this? I'm using Pods 1.9.4 on WP 3.0.5. Which version did you write the new pagination.php for? I see that you posted your message almost a year ago, so perhaps everything worked okay on the version you used at the time, but changes made since then have had an effect on how the pagination work?

answered Apr 14 '11 at 3:12

Simon

69

add comment
enter at least 15 characters
0

Simon, try this following modification for the latest version of Pods CMS and WordPress: http://www.openscriptsolution.com/2011/04/15/getpagination-options-for-pods-cms-1-9-5-and-wordpress-3-1-1/

answered Apr 15 '11 at 2:24

Masino Sinaga

41

add comment
enter at least 15 characters