Rails isnt practical. I hear a lot of people like it, but its a lot harder to set up, more server intensive, and a lot harder to find developers for it. If you're developing a project for yourself, sure use Rails if you want. If you are looking to do full-time work and get hired as a web developer for a company, the standard LAMP stack is the way to go IMO. The vast majority of sites on the web are php or asp based.
As far as php frameworks go, the main one we use at our company is CakePHP. Its not great with large data sets, but its a pretty good framework once you know the best ways to utilize it. Obviously there are pitfalls, but overall, it has a good MVC architecture. Some have compared it to rails for php.
Zend framework is another, though i've never used it. I think its pretty similar to cake. One of our newer developers was familiar with zend, and picked up cake without any problems.
As far as php frameworks go, the main one we use at our company is CakePHP. Its not great with large data sets, but its a pretty good framework once you know the best ways to utilize it. Obviously there are pitfalls, but overall, it has a good MVC architecture. Some have compared it to rails for php.
Zend framework is another, though i've never used it. I think its pretty similar to cake. One of our newer developers was familiar with zend, and picked up cake without any problems.