Coding in ‘core php’ and separating logic from presentation

What are the various ways of acheiving this ? Can someone please guide me?

Controllers and re-factoring for maintainability / sensibility

I have read many posts similar to this on the site: however I still am questioning what is best in my situation (also the answers are contradicting from question to question).

Is it best practice to have a file only of “includes/requires”?

I have 5-10 files on one server that all catch XMLRPC-PHP requests. There’s about 20 lines of require_once in each one that are all the same. It’d make life simpler for me to create a separate file that only has the requires and require that in my XMLRPC files. Is this best practice, or does it open up issues that I don’t know about?

How important is it to implement a caching system in an MVC style framework?

I am writing my own PHP framework (…waits for the groans to subside) for the purpose of learning (best practices, design principals etc.) as I’m entirely self-taught and consequently there are gaps in my knowledge.

Is there any design pattern except MVC for web?

I want to know are there any design patterns for web besides MVC?

Would this constitute MVC – even in a very loose sense?

I’ve been working on a kind of CRM for the sales guys in our office – not as a job role but as a spare time task type of thing – I don’t claim to be a developer or anything like that, but I would definitely like to pursue a career as a web developer down the line, I just think I need a much stronger understanding of OOP principles and design patterns such as MVC before I could even consider it.

Zend Framework View Helper Composition

So I’m reviewing a piece of code that is a perfect candidate to be abstracted away into a view helper. However at the moment, the piece of code uses two other view helpers to get the final display.

Actions and Controllers managing strategy in MVC apps

Can anyone name any usefull strategy/architectural pattern for allocating actions between different controllers when using MVC pattern for developing web application?

Performing user authentication in a CodeIgniter controller constructor?

In “The Clean Code Talks — Unit Testing”, Miško Hevery mentions that “as little work as possible should be done in constructors [to make classes more easily testable]’. It got me thinking about the way I have implemented my user authentication mechanism.

Binding in the view or the controller?

I’ve seen 2 different approaches with MVC on the web.