Segments and GET-data co-existing |
[eluser]Burgestrand[/eluser]
As I consider unsetting GET-data as the one shortcoming of CI I tried to fix it. application/libraries/MY_URI.php Code: <?php application/libraries/MY_Input.php Code: <?php You’ll also want to change the permitted_uri_chars to something fitting. Personally I added “=?&” to the list, but time might show it needs to be even more liberal.
[eluser]xwero[/eluser]
set the uri_protocol to path_info/path_info_org/request_uri and use Code: parse_str($_SERVER['QUERY_STRING'],$_GET); Less changes and no core adjustments.
[eluser]Burgestrand[/eluser]
[quote author="xwero" date="1239991976"]set the uri_protocol to path_info/path_info_org/request_uri and use Code: parse_str($_SERVER['QUERY_STRING'],$_GET); Less changes and no core adjustments.[/quote] Have my babies! (Thanks) Edit: It appears as if PATH_INFO and ORIG_PATH_INFO does not work properly on my installation (using REQUEST_URI). Applying a query string to the URL makes it unable to find the correct controller / method. It could have something to do with my rewrite rules (using lighttpd), I suppose. At least that's one extension less (MY_Input), either way.
[eluser]wiredesignz[/eluser]
htaccess for PHP-CGI hosting (and use segments with query strings)
[eluser]Burgestrand[/eluser]
[quote author="wiredesignz" date="1240047247"]htaccess for PHP-CGI hosting (and use segments with query strings)[/quote] Thanks! Unfortunately I run lighttpd and I'm not sure it has the equivalent in rewrite rules (or if it's less trouble than extending the URI library). Either way, I corrected the code to extend another method instead. Right now it has troubles with the default controller.
|
Welcome Guest, Not a member yet? Register Sign In |