Comments on: Simple CakePHP CMS (Content Management System)

By: Bo-oz

Bo-oz — Wed, 12 Oct 2011 11:32:49 +0000

Hi,

Great tut, very clean and simple code. I was looking for a solution like this, although I would also like to be able to point to other controller/action combinations when creating ‘content’, so you can actually use the same system for non-CMS content. Any thoughts on this?

By: Fahd

Fahd — Thu, 16 Jun 2011 03:13:12 +0000

Thanks fot the tut man !

By: tom

tom — Wed, 25 May 2011 21:39:28 +0000

Hi.. thanks for the tutorial.. but the sample link is broken..

By: Douglas

Douglas — Thu, 05 May 2011 19:52:08 +0000

Changing the title of pages created? Content appears in all

By: Fred

Fred — Mon, 18 Apr 2011 15:05:29 +0000

Very Nice work Joe

Thanks for sharing

By: Simon

Simon — Fri, 08 Apr 2011 16:24:59 +0000

Thanks for this, its nice to see people putting the effort in to provide the community with quality examples of what can be done using freely available tools.

By: CHristopher Cuizon

CHristopher Cuizon — Tue, 18 Jan 2011 04:47:30 +0000

starting to like cake php now……than ci ^_^

By: dogmatic69

dogmatic69 — Sun, 21 Nov 2010 01:03:57 +0000

That is exactly what the router is for, you should never name controllers according to what you want the url to be.

Router::connect(‘/whatever’, array(‘controller’ => ‘contents’… would allow you to have what you need in the url.

Cake will also never look for a Contents model, it does something like Inflector::singularize() to the controller name to get the model name, and hence will never be plural.

You can also create a pages controller with out having any problems as cake looks inside the app folder for code before going to the core libs folder.

By: Joseph

Joseph — Sun, 07 Nov 2010 14:50:57 +0000

Thanks Jan good catch. I think I might also update the setFlash calls to use templates.

By: Jan

Jan — Sun, 07 Nov 2010 13:17:32 +0000

Hi Joseph,

This is a very nice base to start with. It needs some tweaking to work properly with 1.3, but it shouldn’t be too bad.

Apart from the delete thing, another one is to explicitly call the Session component, otherwise you’ll get errors on the setFlash calls, saying Session is not an object. It’s quite a simple fix, append the $components array in the controller with Session, so you’ll get this:

var $components = array(‘Session’, ‘Route’);