Thread

Thanks Ben! If you will have some questions about it, write to me:)

Peng thank you very much I have tried your method it works flawlessly I’m shocked. I didn’t break anything. A serious concern out of my head thanks again buddy.

np, im glad it worked out for you!

pure segment based is good for SEO-ed URLs, but if many segments in your url is going to be optional it’s going to get complicated. query strings on the other hand allow you to have optional “segments” (erm… params) in any order. Bad for SEO, but useful in some use cases 😊

e.g. try doing OpenID authentication without accepting query strings =p

https://localhost/codeigniter/account/auth/finish/google?janrain_nonce=2010-02-09T03:088Zl346SH&openid;.ns=http://specs.openid.net/auth/2.0&openid;.mode=id_res&openid;.op_endpoint=https://www.google.com/accounts/o8/ud&openid;.response_nonce=2010-02-09T03:09:01ZICIURryjv7jA&openid;.return_to=https://192.168.2.77:443/baseci/account/auth/finish/google?janrain_nonce=2010-02-09T03%3A08%3A48Zl346SH&openid;.assoc_handle=AOQobUeCgpAqFDg86fbxD02Mxp_wwhEYkLHYwewyBZF3W8fhtj-4AW&openid;.signed=op_endpoint,claimed_id,identity,return_to,response_nonce,assoc_handle&openid;.sig=umqzmNwGjv85hz0hlZf7m2JDRPo=&openid;.identity=https://www.google.com/accounts/o8/id?id=AItOawkuZfF5laBgFW9vMEeoe0A4gNHQhco&openid;.claimed_id=https://www.google.com/accounts/o8/id?id=AItwku3aZfF5laBgFAcvMEeoe0A4gNHQhco

Oh, you can use large query strings and use URL shorting service to convert them into small URLs.

Thank you very much for the UTF 8 CI , I was looking for this for days, you are a life saver for my project.

I copied the files to my system folder and also copied the index.php file, but the CI was not loading after checking the php logs I figured there was an issue with apppath in index.php which was adding an extra ../ to the application directory.

Once I fixed that I have another error for a form_password() function says its a undefined function which was working fine before. for which I replaced the form_password() function with the normal html input control <input type = password>

even with your utf 8 I am unable to display russian text which is getting pulled from a database table.

Could you please guide on how to fix this.

Mine app is working fine. But, try to convert your database to utf8_general_ci using PhpMyAdmin or alternative tools. And what function was undefined? Or it is your custom function? Anyway, please describe the problem in more informative way! Thanks!

the function which is included in form helper form_password() to create password fields under CI.

I think it is one of the standard functions which is included in CI.

I don’t remember that I have been removing default CI’s functions. Hm. I’ll check it soon. So everything works fine, instead of this?

I’m in Poland and I develop websites with CMS in Polish using vanilla CodeIgniter.
I’ve been trying to do a simple jpg upload where file names have Polish characters… many problems!

I’ll download your special edition and give it a go.

[edit]Nope. Link is dead[/edit]

pioSko, why dead? Link is working. http://uploading.com/files/cf4f746c/utf8_ci.zip/

Of have a look at CI 2.0, it has full UTF8 support built in…

WanWizard, it is created x months ago. There were no CI 2.0. And in topic title “1.7.2”.

My sites are built with 1.7.2, so…

So? My suggestion is to stop fiddling with ‘hacked’ versions of 1.7.2, but to look at an upgrade to 2.0.

At the time it was a good alternative, but now maybe not. Imho it’s better to check it out now, that to come to the conclusion that an upgrade to 2.0 is very complicated due to non-standard code being used.

I’m agreeing with WanWizard. I don’t support this “edition” anymore, so you should look for CI 2.0.