Thanks Ben! If you will have some questions about it, write to me:)
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
December 21, 2009 10:41am
Subscribe [15]#46 / Feb 09, 2010 2:19am
Thanks Ben! If you will have some questions about it, write to me:)
#47 / Feb 09, 2010 2:25am
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.
#48 / Feb 09, 2010 2:54am
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
#49 / Feb 09, 2010 9:29am
Oh, you can use large query strings and use URL shorting service to convert them into small URLs.
#50 / Feb 11, 2010 3:36am
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.
#51 / Feb 11, 2010 10:22am
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!
#52 / Feb 11, 2010 11:49am
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.
#53 / Feb 11, 2010 2:16pm
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?
#54 / Oct 02, 2010 10:31am
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]
#55 / Oct 02, 2010 10:44am
pioSko, why dead? Link is working. http://uploading.com/files/cf4f746c/utf8_ci.zip/
#56 / Oct 02, 2010 11:53am
Of have a look at CI 2.0, it has full UTF8 support built in…
#57 / Oct 02, 2010 11:56am
WanWizard, it is created x months ago. There were no CI 2.0. And in topic title “1.7.2”.
#58 / Oct 02, 2010 1:15pm
My sites are built with 1.7.2, so…
#59 / Oct 02, 2010 1:26pm
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.
#60 / Oct 02, 2010 3:54pm
I’m agreeing with WanWizard. I don’t support this “edition” anymore, so you should look for CI 2.0.