Timeline for Using next/previous_posts_link with customised search
Current License: CC BY-SA 3.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2012 at 13:39 | history | notice removed | turbonerd | ||
| Mar 1, 2012 at 13:39 | history | bounty ended | turbonerd | ||
| Mar 1, 2012 at 13:39 | vote | accept | turbonerd | ||
| Mar 1, 2012 at 12:45 | answer | added | Tom J Nowell♦ | timeline score: 2 | |
| Feb 25, 2012 at 22:17 | comment | added | Rob Vermeer | using $_GET and then redirecting to a nice URL (like /search/species/xxx/) will result in share-able URL's and also beter SEO URL's. It is a bit more complicated, but in the end far more rewarding imo. | |
| Feb 25, 2012 at 9:32 | comment | added | t31os |
Exactly what i suspected, pagination functions will not work with any query beyond the main one, defined by query_posts , in essence the $wp_query object (the main query). I feel the two answers you have both address this problem though, so i'll leave it at that.
|
|
| Feb 23, 2012 at 18:17 | answer | added | Webord | timeline score: -1 | |
| Feb 23, 2012 at 16:31 | answer | added | Rob Vermeer | timeline score: 3 | |
| Feb 23, 2012 at 16:16 | history | notice added | turbonerd | Draw attention | |
| Feb 23, 2012 at 16:16 | history | bounty started | turbonerd | ||
| Feb 21, 2012 at 19:29 | comment | added | Stephen Harris | Well clicking next, you'll be wanting to GET the data, not POST it (I may be wrong in this, but using $_REQUEST doesn't hurt...) | |
| Feb 21, 2012 at 19:02 | comment | added | turbonerd | Added those now @MarkDuncan, sorry! | |
| Feb 21, 2012 at 19:02 | history | edited | turbonerd | CC BY-SA 3.0 |
added 965 characters in body; edited tags
|
| Feb 21, 2012 at 16:41 | comment | added | t31os |
Where do those args end up? Inside query_posts, inside a call to WP_Query? Need to see the code those args are passed to..
|
|
| Feb 21, 2012 at 16:31 | comment | added | turbonerd |
Yeah, I was just wondering why that would make a difference. The actual search is working, just not the pagination. I've updated my code to use $_REQUEST and nothing has changed.
|
|
| Feb 21, 2012 at 16:30 | comment | added | kaiser |
$_REQUEST is something like a "combination" of $_POST and $_GET.
|
|
| Feb 21, 2012 at 15:19 | comment | added | turbonerd |
Updated my post to include used of $paged. I've also tried using $_REQUEST instead of $_POST but it appears to make no difference.
|
|
| Feb 21, 2012 at 15:19 | history | edited | turbonerd | CC BY-SA 3.0 |
added $paged
|
| Feb 21, 2012 at 15:16 | comment | added | turbonerd | OK Stephen, may I enquire why? | |
| Feb 21, 2012 at 15:14 | comment | added | Stephen Harris |
If it replaces the default search, you may need to use $_REQUEST rather than $_POST
|
|
| Feb 21, 2012 at 15:02 | comment | added | turbonerd | Ah, no I hadn't - I didn't think it was relevant. Just found a good post which might help me though: wordpress.stackexchange.com/questions/10459 | |
| Feb 21, 2012 at 15:00 | comment | added | kaiser |
Have you read about the paged and page for paginated results in the related Qs?
|
|
| Feb 21, 2012 at 15:00 | comment | added | t31os | What happens inside the searchresults template(can you add the code from that file to the question), are you passing in those args as is? You'll lose any other query vars intended for the query that way..(such as paging values, etc..).. | |
| Feb 21, 2012 at 14:48 | history | asked | turbonerd | CC BY-SA 3.0 |