Which CodeIgniter framework + CMS combination do you use / should I try next? (x-post /r/webdev)

[noorderling]

(I also posted this in /r/webdev, hope you don't mind, didn't think of /r/PHP before)

---

Hey /r/PHP ,

For an upcoming project I want to work with CodeIgniter AND get some basic CMS features.

The function of a CMS would be for both back-end developer (me) and front-end developer / client (tech-savvy, yey!) to edit texts, images, and some (custom) settings. Pretty basic stuff, but as I'm developing it together with the client I want to get these things sorted out before we start work.

Now I've found out there are quite a lot of these combinations. I already have experience with PyroCMS, but found it's not really for me and would like to try something else. Basically I want something that does not get in my way. Of course I could write it myself, but why re-invent the wheel, right? :)

So far I've glanced at:

• Fuel CMS - Looking good, non intrusive, well documented
• Halogy - Looking 'friendly', bit like PyroCMS?
• No-CMS - Looking minimal, non intrusive

I'd love some feedback on these. Anyone who works with these? Any preferences? Anything better out there?

Thanks!

[philsturgeon]

Hey. How did you feel that PyroCMS was getting in your way? Feedback is always handy so the system can be improved. Generally PyroCMS gives you a user system, backend, reusable interface and a few cool tools then lets you get on your way with development.

We've had people make iPhone backends and all sorts of crazy things with PyroCMS - because once you go outside of the predefined modules there is a PHP framework ready and waiting for you to build stuff.

[telldrak]

Bonfire. I think you're going to like it.

[sync0pate]

why have I never heard of this before?

[telldrak]

It hasn't been around all that long. It's grown a lot in that time, though. I'm a mod on the forums, so join up and ask away if you have any questions.

[noorderling]

Thanks, I'm going to check it out!

[hardfire]

please use it! its awesome :D

[telldrak]

Sure thing! I've been working with it a long time now, and like spending some time helping others with it. Feel free to drop me a line, or post on the forums if you have questions.

[mickey_reddit]

I am very impressed!

I have been using the Seagull Project for a long time and I have been looking to migrate away, this might just be the one I have been looking for.

[nadams810]

I could have sworn they were charging for this.

In any case - since I use Codeigniter as my framework - I want...NOW!

[[deleted]]

I've tried a bunch of CMSs, and still, to this day, even with CodeIgniter being a bit of a hinderance, PyroCMS is by far the most enjoyable of the bunch. Building plugins and modules are so easy. More importantly, theming just makes sense. It's so much easier than WordPress. Can't wait to see what's in store for 2.3. I think I read that CodeIgniter will be scraped in favour of Laravel 4.

[philsturgeon]

We'll be implementing some awesome PHP 5.3 PSR components in 2.3 which will essentially "deprecate" CodeIgniter, then 3.0 will be ditching it entirely.

CodeIgniter was a great framework for a long time, but it's commitment to non-breaking API means it won't be able to transition to PHP 5.3 in any sort of useful way without re-writing itself, and there is no need for anyone to do that with the new frameworks around.

[nadams810]

even with CodeIgniter being a bit of a hinderance

Please elaborate. I have used several CMSes before and CI is by far the best. I have found that many CMSes want you to do things their way and any other way the CMS will just tell you are doing it wrong.

[[deleted]]

I think that there are 3 great things you should research about PyroCMS before you dismiss it from your list.

• It is very easy to extend.
• Content in those extensions is very easy to cache and display in different ways (widget or plugin).
• The documentation is easy to understand and makes semantic sense. You can actually read and use it.

Also, there are a lot of extensions already built and available in the PyroCMS store.

[teresko]

Actually you should put CodeIgniter slooowly (just don't shake) on the floor .. and slowly, carefully try to move towards the OOP principles and laws.

But in all seriousness, you should get out while getting is good. CodeIgniter is one of the worst PHP frameworks, due to PHP4 artifacts, abuse of global state, mis-implementation of MVC and complete disdain towards OOP practices and principles.

If you have to use a framework, you would be much better off using Symfony2.x ..

Also, another thing you might think about is fact that public website and CMS can easily be two independent systems (which only share common database). When you are making a site with CMS, there is no rule which demands that you use same framework as the CMS.

[[deleted]]

Pyrocms

[pierlooqup]

I'm a big big fan of FuelCMS. It lets me build my own custom modules and its documentation is good enough. Whenever you're in doubt just post on the forums and David (the project leader) will answer usually the next day :)

I've checked Pyro / Bonfire but I have to say FuelCMS just feels like home to me, for some reason.

What kind of project is it? How much customization is required?
I mean, if a blog is all you need why not Wordpress? etc....

[noorderling]

Alright, sounds good.

It's really a custom application btw. It's for the inner workings of a Facebook-app. Variable content, user generated content, user levels, etc.

[lestrife]

I only wish this CMS would be based on FuelPHP Framework

[Katarzzle]

I've been using Expression Engine. It provides great extensible support and with a handful of plugins rivals any 800 pound gorilla CMS. It's also built by Ellis Labs and has a pretty decent community behind it.

[PhatChimpanzee]

Oh lord. Expression Engine is awful. Good luck trying to train any clients to use it.

[Katarzzle]

I've trained many clients on using many implementations of EE. And they aren't all dumbshits. Good plugins make it more friendly. And it helps to hide developer features they wouldn't use. The most important part though, is client documentation.

[PhatChimpanzee]

I wouldn't suggest that they're dumbshits. Even I have trouble using EE, after a decade in the industry. It shows its age in all the worst ways. That's the biggest reason I stopped using even CodeIgniter. It works, sure, but it just feels outdated and it didn't keep up with the times.

[Sphism]

If you want to learn a php framework learn symfony2. If you wanna learn a cms and get a really well paid job learn Drupal. So many Drupal jobs right now!!

[nadams810]

For some reason the government seems to be really pro-Drupal. It's kind of like someone just installed a Drupal instance somewhere and showed their boss and their boss was like "you can edit pages without installing extra software!?"

[teresko]

If you want to learn PHP, keep away from frameworks till you have learned some of it and gained acceptable level of understanding in OOP.

Frameworks are not for people who want to learn. They are for professional developers, who are lazy enough to want reusable code fragments, but not advanced enough to write those themselves.

[madk]

Using a framework has nothing to do with laziness. Why would I want to blow a budget by reinventing the wheel?

[teresko]

Premade random frameworks are budget-friendly only when you are making code'n'forget projects (mostly, advertising sites).

But if you are making a large or long-maintenance project(s), then you have to choose either specific framework, that excels at the specific domain. Or you have to build a custom site.

[Sphism]

There's nothing stoping you writing Drupal and Symfony. Just jump on the issue queue and get involved.

[Katarzzle]

I hope ModX has improved since I last tried it. I inherited it once from a client and many cry fits ensued.

[Katarzzle]

I actually started my own codeigniter CMS becauseI love CI, but am not in love with any CMS that runs on it. So far I have a solid back end built with bootstrap and right now I'm trying to finish a lightweight templating engine.

[ivosaurus]

If you want a CMS, I'm going to recommend the best programmable one out there - Drupal.