Timeline for Using query_vars filter
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2013 at 13:16 | vote | accept | Josh Levinson | ||
| Jul 25, 2013 at 13:16 | comment | added | Josh Levinson | You were right! It was this plugin: wordpress.org/plugins/404-redirected that was causing the get params to be stripped. Weird. Now I remember why I never install plugin more than 6 months old without knowing the developer... | |
| Jul 24, 2013 at 14:37 | comment | added | Josh Levinson | Hm...I'll have to try this out and get back on it. | |
| Jul 24, 2013 at 4:37 | comment | added | Milo | parse_request strips get vars for the purpose of parsing the request, it doesn't redirect to that version of the URL. why it doesn't work for you I can't say, I do this all the time without issue- I've just tested on a clean install and twentytwelve theme, and it works as expected. | |
| Jul 24, 2013 at 4:30 | comment | added | Josh Levinson | If query_vars is not the solution, why does wp strip my get params, and what can I do about it? | |
| Jul 24, 2013 at 4:28 | comment | added | Josh Levinson | Also, you said there is no mechanism for converting get params into query bars, but that's exactly what step 4 or parse_request does according to that page. | |
| Jul 24, 2013 at 4:23 | comment | added | Josh Levinson |
According to codex.wordpress.org/… , parse_request() strips the $_GET parameters from the URL. When I visit example.com/post123/?my-preview=123 (I doubt my-prevoew is reserved), wp strips the get params and I eventually land on example.com/post123/
|
|
| Jul 23, 2013 at 20:52 | history | answered | Milo | CC BY-SA 3.0 |