permitted_uri_chars and $_GET

[eluser]Edemilson Lima[/eluser]
Did you try this?

Code:

"a-z 0-9~%.:_+-"

[eluser]taewoo[/eluser]
yeap... same result

[eluser]Bluemill Media[/eluser]
I know the general argument around here seems to be 'Segmented URIs are cleaner, SEO Friendly, and aesthetically pleasing.' This is true. But, frankly, there are several circumstances where these arguments don't matter, such as when building sections of a web application that a search engine will never see. In these situations (at least for me) CodeIgniter fails miserably. The truth is (and this seems to be a widely adopted stance on the issue) it's really kind of annoying that CI is so tight on this subject.

As much as I can appreciate the security features of CI, and as much as I absolutely love the whole of the framework, there's not enough reason that I can think of to ALWAYS require segmented URIs.

Because of this, I think it'd make the most sense (and be least frustrating for everyone) to allow the option to use both segmented URIs and Query Strings in unison. Seriously, there's no reason not to. The functionality is ALMOST already there, by way of allowing the user to specify the 'uri_protocol'.

Has anybody found a decent work-around for this problem?

Much respect for the member that finds and posts a decent solution.

[eluser]Colin Williams[/eluser]

In these situations (at least for me) CodeIgniter fails miserably. The truth is (and this seems to be a widely adopted stance on the issue) it’s really kind of annoying that CI is so tight on this subject.

Ha! To say something "fails miserably" you might want to check your own ignorance first. Just saying...

On and on and on and on these discussions go. The fact is, you CAN use both $_GET and URI segments with CI. The first step is to set enable_query_strings to TRUE. This way, CI doesn't unset the $_GET superglobal.

Next, you have to instruct CI to use path info and not query string trigger values. You do this by setting uri_protocol to something other than AUTO or QUERY_STRING. I would start with PATH_INFO and try ORIG_PATH_INFO if that causes errors.

And here's what that looks like in code:

Code:

$config['uri_protocol'] = "PATH_INFO";
$config['enable_query_strings'] = TRUE;

So, to suggest that CI has somehow disabled the possibility to use segmented URIs and query strings simultaneously is flat-out erroneous.

[eluser]taewoo[/eluser]
@Colin: Agreed.

[eluser]Bluemill Media[/eluser]
@Colin: I appreciate your willingness to correct my mistake. Thanks.

Although, seems I stepped on a soft-spot. No reason to be so tactless. We're all just here learning, after all.

Kinda funny though. You offer your advice like I must be retarded for not knowing this and it must be such common knowledge...However, if this is really the case, why is the question brought to light so often?

Really, not trying to pick a fight or insight any flaming, just seems a bit odd that somebody would take the time to answer a question and display such resentment that they 'have to'.

And oh yea,

Much respect for the member that finds and posts a decent solution.

Much respect for you, my friend!

Also, and a bit off topic: I really like your website. (http://www.dirtysouthbmx.com/)

[eluser]Colin Williams[/eluser]
Take it as me "sticking up for the framework." Your assessment of my tact is spot on, but uh, no apologies. I hope people finally $_GET the point. And the reason it comes up so much (like a myriad other things) is because people don't take the time to get to know the framework in and out.

And thanks for the compliment. DirtySouthBMX is a site I started when I was 16. It was my introduction to the Web, and while everyone poked fun at me for spending all my time working on "that stupid web site," I was gaining the knowledge and experience that put the food on the table today. It used to be a solid social network of riders in and around the Great State of Texas. It was built on a bunch of finagled Perl scripts I kept improving, but about 2 years ago I tossed it all out and decided to rebuild it in PHP. It's been going on ever since, and I'm now, of course, building it on CI. One day it will be done. (Just a dump of random posts for now.)

[eluser]Bluemill Media[/eluser]
Good for you. And no, I don't ask for any apologies...I don't believe there was any reason for you to defend CI... I'll admit, I was a bit taken back at first, but hey...you'll be who you'll be and I can't do a damn thing about that.

As for people getting the point, it seems to me that those who have brought the question up are novice/intermediate users of CI. If they weren't, they likely wouldn't be posting in the forum anyhow.

Not to say you shouldn't stand your ground, but I'd be willing to argue it's a losing battle, as there will always be novice/intermediate CI developers, and they'll likely always come here when they have a hard time with something. Not a thing I can see wrong with that. I can't imagine any other reason the creators of CI would have made these forums available, if not to supplement the other available learning sources for those who are not so familiar with the framework 'in and out'.

Now, I apologize if anything that I said came off as offensive to CI or its developers, but it wasn't intended that way. I'm an avid CI developer, and can't imagine ever needing another framework. My comments were purely an expression of my aggravation that the problem didn't seem to have a solution that I could come to...a place I'm sure you've been at one time or another as a developer. Hey, nobody's perfect.

[eluser]Colin Williams[/eluser]

...my aggravation that the problem didn’t seem to have a solution that I could come to...a place I’m sure you’ve been at one time or another as a developer...

Right. The difference is that I don't try to find a scapegoat (in your method, you blame the framework over your own ignorance). I dig in and figure it out.

And, look, I understand why people visit the forum. I don't have a problem providing straight answers anytime I know I've got a clue what I'm talking about. This topic had reached page 3, and here I find you saying CI "fails miserably." Without a counter, the participants might buy into that irresponsible conclusion.

And you say it's a losing battle (wow, more defeatism), but there are many strategies that lie outside my sphere of influence that could be effective. The most obvious is an improvement to the docs, outlining the method that works along with any caveats needed. The CI dev team is smart, committed to good documentation, and so I expect they will use the User Guide as an avenue for squashing these misunderstandings in the future.

[eluser]Bluemill Media[/eluser]
I think we're pretty close to being in agreement. You were right to correct my ignorant remark (with regard to the true definition of the word). I also believe the CI developers are very smart people. And I believe you hit it on the head: This should be somewhere in the documentation as an FYI (or at least somewhere new users can find it easily). Not defeatism, I just think you're fighting the losing battle. If you really want to pro-actively put a stop to these questions, your probably better off getting in touch with the CI team to request that this (what should be general knowledge but obviously isn't) be put in the docs.

The reason this thread had continued for 3 pages is because your solution hadn't been posted before (at least in this thread, or anywhere else I've found). Now that it has, I'm sure this thread will cease to continue beyond our discussion.

I think it's safe to say we can chalk this up to a personal disagreement. I don't ask for apologies, of course...but I'm entitled to disagree with your method of response/level of callousness. Just as you disagree with my method of questioning. I'm sure you're a nice guy beyond your posts in this thread, and it's in no way an attack toward you. I just choose to conduct myself differently. Simple.

In any case (in hope that our disagreement is over ), how long have you been developing PHP? I also started with Perl, although my experience with it never lead to any established work. PHP though is a different story altogether. Pays the bills, and then some, lol.

Maybe if we can see past our disagreement we can connect on LinkedIn or YouNoodle? I'm always looking for smart people to collaborate on new ideas with. I may even have a few right now you'd be interested in? In any case, feel free to get in touch if you'd like.

- http://www.linkedin.com/in/lorrenbiffin
- http://younoodle.com/people/lorren_biffin