Hi,

I just installed the cakephp and went through the two examples in the
1.3 documentation. But am trying to now figure out how to get the plug-
ins to work.. my understanding is that the M C V files have their own
dirs in the app directory chain. Which is fine, but how do I get the
plug-ins to work?

For example, trying to get the users plug-in to work, I copied the
entire downloaded, unzipped, folder into /app/plugins/users as the
instructions say.

Then I did the "cake bake plugin users" which seems to have worked,
have the users & details tables set up, but am getting this error
now.. when I go to: http://localhost/cakephp/users

I guess I don't understand how files can sit under /app/plugins when
in the two documentation examples i had everything under the /app dir?

Do plug-ins stay under /app/plugins and you can have files under /app?
Also can I set up independent database.php files for each module, so
to speak?

I guess I don't get the special names or using, Users or user, as the
ordering is great in keeping a naming convention, but where do I look
to understand the flow is confusing. So is it the Model loads the
Connector and the Connector is displayed in the view, based on the url
that is entered?

So to back track based on URL, I would say that the "Model name" and
the "View" they are looking at is the last 2 folders in the URL?

http://localhost/cakephp/users
http://localhost/cakephp/users/login


--

Error: The Behavior file app\models\behaviors\utils.sluggable.php can
not be found or does not exist.

Error: Create the class below in file: app\models\behaviors
\utils.sluggable.php

<?php
class Utils.SluggableBehavior extends ModelBehavior {

}
?>

--

-- 
Our newest site for the community: CakePHP Video Tutorials 
http://tv.cakephp.org 
Check out the new CakePHP Questions site http://ask.cakephp.org and help others 
with their CakePHP related questions.


To unsubscribe from this group, send email to
[email protected] For more options, visit this group at 
http://groups.google.com/group/cake-php

Reply via email to