Search Pagination Problems (1.5.3)

I'm having some issues with the search result pagination in Omeka 1.5.3. When the search results appear, the new number appears in the results count and the pagination links populate the sequence of pages. However, when clicking on "next" or any other number in the series, it immediately erases the search and starts back at the index of all records.

Now, I do have the search and browse php functions appearing on the same page, as dictated by the requested site design, and I'm aware that's likely the root of the problem. So in other words, on the browse.php page, I have a panel on the left which includes the advanced-search.php and the right side shows the results in either a grid or listed display.

Although our site isn't yet available for public viewing, I can include necessary chunks of code -- however I first wanted to establish whether or not this approach seemed problematic for Omeka in general and if this search pagination problem was happening to others?

Theme: Custom, based upon "From-Scratch"

There shouldn't be any problem in including the search form on the same page as the actual results.

Sharing the custom parts of your code for search/browse/pagination would probably be helpful.

I'm unfortunately still stuck on how to ensure the pagination links retain the search parameters, so if anybody has any ideas I would be extremely grateful. I realize the above code didn't format properly in when posted here and is more than necessary but I wasn't sure where the problem might sit (I also can't delete that post to try again).

The HTML shows that the pagination links within the search results target /items/index/page etc, removing the search filters and pulling from the main index. I found a recipe that addressed a similar problem in the item pages: http://omeka.org/codex/Recipes/Using_Search_Results_to_Create_Custom_Next_and_Previous_Links so again, I wonder if this issue is derived from the Omeka/Zend framework, which would involve my creating a similar workaround, or something easily fixable due to a piece of errant code?

Thanks again for any advice!

My last message, once again, does not appear to have submitted correctly, and is cut off and embedded in the previous post!?

Trying again -

I'm unfortunately still stuck on how to ensure the pagination links retain the search parameters, so if anybody has any ideas I would be extremely grateful. I realize the above code didn't format properly in when posted here and is more than necessary but I wasn't sure where the problem might sit (I also can't delete that post to try again).

The HTML shows that the pagination links within the search results target "/items/index/page etc", removing the search filters and pulling from the main index. I found a recipe that addressed a similar problem in the item pages "Recipes/Using_Search_Results_to_Create_Custom_Next_and_Previous_Links" so again, I wonder if this issue is derived from the Omeka/Zend framework, which would involve my creating a similar workaround, or something easily fixable due to a piece of errant code?

Thanks again for any advice!

I deleted your post of code, something went very wrong with the formatting there (to make this forum software happy with big blocks of code, you generally want to put backticks on their own lines before and after the code).

Have you overriden common/pagination_control.php in your theme?

Thanks for the reply John (and for deleting the wonky post). No, I haven't overwritten that file, or any of pagination or search-related functions...

The likely problem jumps out at me now, looking at that (now-gone) code again.

Your form starts like this:

<form id="fullSearch" method="post" name="">

The search form shouldn't use the POST method, it should use GET. The pagination controls look for GET parameters when they're creating the links to other pages to keep the same search active.

Try using GET there instead (and a form usually doesn't really need a name attribute):

<form id="fullSearch" method="get">

...And there was much rejoicing - that did it, thanks!!