5 ms·

What just happened?

23 points by kingsidharth 16y ago

dreur 16y ago
Thats one of the bad uses of OS but so common
stevenwei 16y ago
This is not terribly uncommon with open source projects (see the same complaints towards Django's commit process a few months ago). But CodeIgniter can't accept query strings in its urls? Really?
- epochwolf 16y ago
  > But CodeIgniter can't accept query strings in its urls? Really? Yup, you're supposed to use the router instead.
  - kingsidharth 16y ago
    This is such a turn off.
  - deleted 16y ago
    [deleted]
- aviel 16y ago
  you can hack it to... but it's dirty. just use something else.
- fookyong 16y ago
  of course you can. it is switched off by default but takes about 1 minute to re-enable (edit a config file). the author is overblowing the issue
  - zackkitzmiller 16y ago
    This is simply not true. Enabling query strings in the config breaks all of the html "helpers."
DanHulton 16y ago
This is largely why I switch to Kohana long ago - the developers of Kohana forked CodeIgniter and then maintained it, while Ellis Labs let CodeIgniter rot. For those who are interested, Kohana is in version 3 now, and is no longer a CodeIgniter fork. KO3 is basically a ground-up framework reboot with all the lessons learned from making CodeIgniter not suck (query strings, requiring PHP5+ for cleaner architecture, etc.) taken into account. http://kohanaframework.org/ http://kohanaframework.org/
- Pyrodogg 16y ago
  Thank you for pointing this out. I've used CI for a couple of previous projects, and was just starting on another. It's not too late to port everything over. :) Adios, Ellis and CI.
- citricsquid 16y ago
  Kohana has awful documentation though -- compared to CI. I think it's a good idea to start with CI to learn to nuances of PHP MVCs and then switch to Kohana with that knowledge in hand.
  - DanHulton 16y ago
    An excellent point. Though the more I work with Kohana, I find it ends up being an unexpected side-benefit: I'm forced to go through the actual code of the subsystem in question when I want to learn something tricky about how it works, which means that I thoroughly understand it, as opposed to just dox-level familiarity. They are working on better dox, though.
deleted 16y ago
[deleted]
cowboyhero 16y ago
The "Phil" he's talking about in the first paragraph is Phil Sturgeon, and the original blog post is here: http://philsturgeon.co.uk/news/2010/10/what-happens-next http://philsturgeon.co.uk/news/2010/10/what-happens-next
AlexMuir 16y ago
I moved to Yii from CI and never looked back. CI was lacking the most basic features - I cannot believe it still has so many users.
- slantyyz 16y ago
  CI's documentation is a huge part of its appeal.

23 points by kingsidharth 16y ago

dreur 16y ago

Thats one of the bad uses of OS but so common

This is not terribly uncommon with open source projects (see the same complaints towards Django's commit process a few months ago). But CodeIgniter can't accept query strings in its urls? Really?

epochwolf 16y ago
> But CodeIgniter can't accept query strings in its urls? Really? Yup, you're supposed to use the router instead.
- kingsidharth 16y ago
  This is such a turn off.
- deleted 16y ago
  [deleted]
aviel 16y ago
you can hack it to... but it's dirty. just use something else.
fookyong 16y ago
of course you can. it is switched off by default but takes about 1 minute to re-enable (edit a config file). the author is overblowing the issue
- zackkitzmiller 16y ago
  This is simply not true. Enabling query strings in the config breaks all of the html "helpers."

DanHulton 16y ago

This is largely why I switch to Kohana long ago - the developers of Kohana forked CodeIgniter and then maintained it, while Ellis Labs let CodeIgniter rot. For those who are interested, Kohana is in version 3 now, and is no longer a CodeIgniter fork. KO3 is basically a ground-up framework reboot with all the lessons learned from making CodeIgniter not suck (query strings, requiring PHP5+ for cleaner architecture, etc.) taken into account. http://kohanaframework.org/ http://kohanaframework.org/

Pyrodogg 16y ago
Thank you for pointing this out. I've used CI for a couple of previous projects, and was just starting on another. It's not too late to port everything over. :) Adios, Ellis and CI.
citricsquid 16y ago
Kohana has awful documentation though -- compared to CI. I think it's a good idea to start with CI to learn to nuances of PHP MVCs and then switch to Kohana with that knowledge in hand.
- DanHulton 16y ago
  An excellent point. Though the more I work with Kohana, I find it ends up being an unexpected side-benefit: I'm forced to go through the actual code of the subsystem in question when I want to learn something tricky about how it works, which means that I thoroughly understand it, as opposed to just dox-level familiarity. They are working on better dox, though.

deleted 16y ago

[deleted]

cowboyhero 16y ago

The "Phil" he's talking about in the first paragraph is Phil Sturgeon, and the original blog post is here: http://philsturgeon.co.uk/news/2010/10/what-happens-next http://philsturgeon.co.uk/news/2010/10/what-happens-next

AlexMuir 16y ago

I moved to Yii from CI and never looked back. CI was lacking the most basic features - I cannot believe it still has so many users.

slantyyz 16y ago
CI's documentation is a huge part of its appeal.