what PHP framework do you use ?

I use my own custom made framework ;-). Never liked CakePHP.
 
codeigniter is well known here. it's simple and useful. also symfony.
What you want to do?
 
What are you trying to do with it? For scraping I use Zend.
no scraping , I need something for more general use, e.g: working with forms and mySql database with ajax, user authentication...
 
Have been experimenting with Cakephp for something I wish to create. Had to "fire" them as they are dependant on mod_rewrite.
Sadly CodeIgniter seeeeeemed more promising...but alas mod_rewrite F's it up again.
Tried to ditch Wamp server as any attempt to rectify the issue "frys" it and it's re-installation time. Just wasted a lot of time DLing Xampp server. Can't even get the CI welcome page with that. I'm 99% sure it has everything to do with "Apache sucks" and nothing to do with the frameworks. But then I wouldnt know. You can't learn a system when you can't make it work.

Current framework:none
Time invested: Good portion of free time over last 4 1/2 months
Quitting point: 6 months (just not worth it)
Ideas produced: plenty
proceeding with any of them: pointless
specific issue: undetectable
resolution: unfixable
commonality: to broad of a scope - Name a computer, OS, hosting company, platform, framework etc etc Apache has F'ed it up.
(google is your friend)
Fixes: Endless list of things that don't work.
Cost: One blown up computer, countless man hours, pride blah blah blah
Summary: Win8.1, HP Touchsmart, Firefox WILL NOT work with GD Apache. This being said it kinda makes it pointless to further persue learning the frameworks or the php language as successful operation on my system is theoretical only. I will spend the next 52 days searching for a result from someone with the EXACT same OS build, EXACT same machine and EXACT same version of firefox who manages to fix this problem. If google doesn't know then no solution exists as I am GD sick and tired of going board to board reading what "smart guys" HYPOTHESIZE the problem to be.

At the point where we stopped having fun...MySQL...seemed like cake to me...I could master that. PHP...tho a picky and particular language as far as syntax...it follows a logic that I could pick up reasonably quickly. And all that means precisely DICK as prior to this project I didn't know that I'd need a Masters Degree in server maintenance and deployment. I'd rather read the 1000 page CakePHP Cookbook than even attempt to decipher that chicken scratch Apache calls a "manual"

Sigh, uninstal xampp, reinstall wamp (for 113th time), reload saved files into www folder, edit wamp index.php turning off localhost supression, remove "#" from Load Module....., watch bullshit start all over again, outline next phase of google search queries, count the SECONDS until the end of January when my time commitment to self terminates and I can finally bring myself to use the "I" word, as at that point the task has been qualified and quantified to be mechanically impossible.
 
What size is your project?

I personally prefer CodeIgniter for how light it is. However, you may want something more feature rich for a bigger project such as Laravel.
 
The update is tho thru a miracle I found the right answer to mod_rewrite and conquered the Apache hill (for now), I have wasted yet another month getting CI way further than Cake ever got me. But CI will fight you at every single turn. From errors directly in there tutorial CI will test your googling skills. Simple problems can take days to find the RIGHT answer in a sea of outdated crap. Using Bootstrap? Forget about it! But don't worry, every other prebuilt twitter-bootstrap goodness has and alternate CI demon so there is no shortage of search queries of "what am I doing wrong, why doesn't this work, why is this happening when I do (this)...
Fortunately, even Ellislabs has turned its back on it's own creation giving it a home far far away in Canada where (hopefully) college students will do a total rewrite and release the touted but never released version 3. As for now, much like Jesus...we're still awaiting a glorious second coming.

Switching gears entirely. I will accept their shortcomings as my own (desire to have universal tools). Mea culpa! Going to step down to a loose micro MVC. If I need fancy bells and whistles then I will just code them myself. It should increase intimacey with the creation and I'll have a clearer picture, when I need a workaround for something, if it will conflict with my setup so I can think more objectively and exponentially reduce frustration.

On the side I'm starting to play with wordpress. I wasn't impressed years ago, but I'm curious now. Someone always needs something fixed or modified on a wordpress site. Could one day be some small side money for a rainy day.

Codeigniter...I'm Donald Trumping your azz...YOUR FIRED!
 
Did a project in cakephp a while ago, using mongo and such. It was alright.
Currently building a different site using yii2, twig, fb api, and mongo. This wasn't fun to set up on my windows machine. Took 2 seconds on ubuntu hehe.
I am enjoying yii2, but this time going without anyone to instruct me it is slower going.

I chose mongo as a storage engine simply because it is generally very fast. The way it's flexible storage system is perfect for my needs, because I don't want to constantly add many field types and such things. So I'll design so that Each user is a silo with all their data contained.
User A will only ever see User A, so this makes this great. Not the worst setup for data collection either.


Now Wordpress. For most sites I'll use wordpress, advanced custom fields, maybe(probably) acf repeater, wp super cache, custom implementation of twig. Grab bootstrap, jquery and start building a theme, or use a base skeletal one to speed this up.
Generally as a rule with wp, if I can throw it up and get both the cms and the functionality desired working faster than a framework, then I will.

Expression Engine. Sigh... While I've hated this cms from the day I began using it, It was my job to not only to become proficient, but to become an expert at using it. I can't call myself an expert so much as highly creative. I do have a patch I contributed to a while back, and I have done a lot of stuff in stack exchange. ok So here is why EE is on this list. We wanted to land a client at work, but we REALLY wanted to land it. So we took his idea, and we built a mock up, functional and non-scaling version. We threw this on a digitalocean $5 box with ssd and that was the magic. We built this mock up in two days and it landed us the client.

My point is, you can crank something fast out in EE. Especially with its hidden relational db type of powers.

So................ I use whatever framework suits the project at hand best, and which framework is mose efficient to use (client needs included), and finally, of the ones left, whichever we prefer.
 
Laravel +1 so easy to pick up and has great documentation and community
 
Mostly Yii and CI here. These days I am working in magento, but I still love those two frameworks :)
 
Personally, I prefer Laravel. However, when I've worked for companies it's almost always either 1) CodeIgniter or 2) Zend Framework. (Although Laravel is growing in popularity there too). If I'm making smaller projects, I almost always use a micro-framework though.
 
Now using laravel, and I have to say that I love it!
 
Back
Top