Another thing for example... i have plugin users, also i have controller
users... if i have to access the action login in plugin users and
controller users... the url would be /users/users/login, it would be nice
if the plugin checks if there isnt a controller called login, if not it
sends the
you want - if you want
a modules folder you can just do:
App::build(array('Plugin', array('Modules'));
A real example of what Andre or the_woodsman mean when they talk about
modules would probably clear a lot of things up so if either of you
would like to fill out this template
On 22/06/12 04:03, Jamie wrote:
On Thursday, June 21, 2012 9:23:44 AM UTC-7, Ratty wrote:
You should not be changing any plugin code anyway. That's why they
are
plugins...
You update them straight from github when you need to. If you want
to modify
the behaviour of a
Also, if we are adding functionality to a plug-in, or fixing something that
doesn't quite work. We should probably committing that code back with the
owner of the plug-in. Considering most plug-in developers are scratching
their own itch, and not necessarily doing a market needs assessment to
TOTALLY agree Vinnie.
I believe that's what Open Source is all about.
Steve.
On 22/06/12 11:56, SpazzyV wrote:
Also, if we are adding functionality to a plug-in, or fixing something
that doesn't quite work. We should probably committing that code back
with the owner of the plug-in.
one is the most relevant to the first post in this thread. For
example, the apps I work with right now use 5-15 plugins, their app
controller/model/view folders are typically empty.
In addition you can organize your paths any way you want - if you want a
modules folder you can just do:
App
three
different directories
* Encourages less coupled code - in theory these modules could almost be
framework agnostic, whereas lumping files in /controller etc doesnt'
encourage that way of thinking
* personal preference :)
I understand it might be a lot fo work to change Cake to support
On Thursday, 21 June 2012 12:07:27 UTC+2, the_woodsman wrote:
Re the difference with plugins - I get your point, but if I want to have a
plugin with multiple models and controllers etc, then surely I still end up
losing that module structure, and end up with /Controllers and /Views
It´s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that application.
The reason for modular programming is:
imagine you have /products/categories wich uses Category
On Thursday, 21 June 2012 15:44:26 UTC+2, André Luis wrote:
It´s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that application.
So - put your modules
On 21/06/12 14:44, André Luis wrote:
It´s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that application.
You should not be changing any plugin code anyway. That's why
On Thu, Jun 21, 2012 at 6:07 AM, the_woodsman elwood.ca...@gmail.com wrote:
* Encourages less coupled code - in theory these modules could almost be
framework agnostic,
That's what the Vendors folder is for. Anything in there that's
Cake-specific should be in Plugins. And *those* are called
On Thursday, June 21, 2012 9:23:44 AM UTC-7, Ratty wrote:
You should not be changing any plugin code anyway. That's why they are
plugins...
You update them straight from github when you need to. If you want to
modify
the behaviour of a plugin model for example then you can extend it in
On Friday, June 22, 2012 10:03:57 AM UTC+7, Jamie wrote:
On Thursday, June 21, 2012 9:23:44 AM UTC-7, Ratty wrote:
You should not be changing any plugin code anyway. That's why they are
plugins...
You update them straight from github when you need to. If you want to
modify
the
Is there any way to use modules in CakePHP, it should work like
plugins, but i dont want to use plugins to create modules... it would
have it´s own Model, View and Controller folders inside...
If there isnt this feature yet, it could be applyed on next updates,
couldnt?
--
Our newest site
, if you wanted to share some code, but
for whatever reason didn't want to use a plugin, you could just do an
svn external (or export, or copy, etc etc) to get a nice working component.
On Wednesday, 20 June 2012 15:37:13 UTC+1, André Luis wrote:
Is there any way to use modules in CakePHP
external (or export, or copy, etc etc) to get a nice working component.
I like the separation. I *know* that 3rd party files can always be found
under APP/Plugin.
On Wednesday, 20 June 2012 15:37:13 UTC+1, André Luis wrote:
Is there any way to use modules in CakePHP, it should work like
Hello,
I would like to create a cakePHP application having different modules
like - Events, Poll, etc.
Each module will have more than one database tables.
Each module may have more than one controller.
So i want to have a separate folder for each module within models
folder, like - /app/models
On Fri, Jan 14, 2011 at 9:27 AM, earth earthtechnol...@gmail.com wrote:
Hello,
I would like to create a cakePHP application having different modules
like - Events, Poll, etc.
Each module will have more than one database tables.
Each module may have more than one controller.
So i want
You should probably read the plugins section of the Cookbook:
http://book.cakephp.org/view//Plugins
- Jamie
On Jan 14, 6:27 am, earth earthtechnol...@gmail.com wrote:
Hello,
I would like to create a cakePHP application having different modules
like - Events, Poll, etc.
Each module
:
Hello,
I would like to create a cakePHP application having different modules
like - Events, Poll, etc.
Each module will have more than one database tables.
Each module may have more than one controller.
So i want to have a separate folder for each module within models
folder, like - /app
/app/controllers/poll/polls_controller.php
etc.
just clear cache. and for views, there's Controller::viewPath property
I suggest plugins for solution.
On Jan 14, 3:27 pm, earth earthtechnol...@gmail.com wrote:
Hello,
I would like to create a cakePHP application having different modules
No,
but you can group mvc files by adding additional paths in
bootstrap.php (see doc comments), but this is not best solution.
(performance and some other issues on how cake includes view files)
On Aug 26, 11:09 pm, Mech7 chris.de@gmail.com wrote:
Is there way to setup modules in cake... I
Well, you could just write plugins that take advantage of this
functionality - i.e. write a Blog plugin that will use a Tag plugin if
it exists.
On Aug 26, 2:09 pm, Mech7 chris.de@gmail.com wrote:
Is there way to setup modules in cake... I don't mean plugins which
are seperate
But plugins are not convenient to use for this purpose as they have
their own layout / script etc files.. And not really share anything
from the main application
On Aug 27, 4:36 pm, Jamie jamie@gmail.com wrote:
Well, you could just write plugins that take advantage of this
functionality -
Is there way to setup modules in cake... I don't mean plugins which
are seperate capplications but modules that will hace MVC files... but
could also work togheter... for example you can install a Tag module..
and if you install a Pages or Blog modules they could make use of
it... all in seperate
or other framework. Drupal looks like (30sec peek at the code
for a custom module) a half-finished app. Not in the sense that
anything is missing but that you start with haft the app done. The
downside is that you have to live with the modules and hooks to make
your code talk to Drupal. You have less
at the code
for a custom module) a half-finished app. Not in the sense that
anything is missing but that you start with haft the app done. The
downside is that you have to live with the modules and hooks to make
your code talk to Drupal. You have less freedom.
Cake and most other frameworks act
Does anyone have CakePHP experience and Drupal custom module
experience?
If so, what is your opinion of the Drupal API for writing custom
modules?
I have a friend that is about to do a re-design for his Drupal app and
is considering changing frameworks. They would have to design 3-4
custom
of the Drupal API for writing custom
modules?
I have a friend that is about to do a re-design for his Drupal app and
is considering changing frameworks. They would have to design 3-4
custom modules. Any thoughts?
Thanks.
--~--~-~--~~~---~--~~
You received
for
drupal also.
On Aug 9, 9:14 am, Josh joshs.silver...@gmail.com wrote:
Does anyone have CakePHP experience and Drupal custom module
experience?
If so, what is your opinion of the Drupal API for writing custom
modules?
I have a friend that is about to do a re-design for his Drupal app
My scenario is :
Keep for example there is a view file and it has 2 input fields for
entering name.
First field belong to model_1 which is the primary model of the view
page.
Second field belongs to another model model_2.
Both fields are mandatory and has an error msg. if left blank.
If I use
, and the helper could be written
to act like a module bucket - pull in the modules for that page,
pass data to the elements and render them to a position in your page.”
It seems that James approach is more generalized:
James if I am not wrong than you are asking me to deal the things as
following way
Singleton Pattern)
therefore you dont have that much more memory usage..
using this inside elements might not be MVC like, but it would come
close to the above Joomla Modules
You CAN use App::import within an element to include the model(s) you
need, and run queries on them but this not very
I too am aware of Joomla, and have wondered how cake would do
something similar. I am only relatively new to cake, when reading the
docs the closest thing I could see were Elements (but I don't know
their limitiations).
It may be worthwhile posting a more generic question, such as: how do
cake
A helper in conjunction with elements would likely be the closest
thing you'll get to a Joomla module. Elements would contain the
presentation logic for each module, and the helper could be written
to act like a module bucket - pull in the modules for that page,
pass data to the elements
Any modular system is going to be written to meet specific needs. The
main issue that I see with CMS-rivaling system is the need to tie it
in at all stages of the application: model, view and controller.
Modules themselves would need a database presence, requiring models. A
notification system
Joomla Modules
You CAN use App::import within an element to include the model(s) you
need, and run queries on them but this not very efficient as you may
end up with several complete instances of the same model being
generated in a single request
by simply adding files and db entries
• We would have generalized function to load modules but once I want
to create new module than I need not require to touch my controller’s
logic, just need to db entry and adding necessary files
• We can easily enable/disable modules to any page
Building any kind of module/modular system has certain complexities,
and if there is any form of public implementation it's unlikely to be
one size fits all. The first thing is to be very clear what
funtionality you want from the system, and what behaviour you want it
to exhibit.
Modules relate
There is no entity in CakePHP that work like Joomla modules out of the
box. The closest thing would be elements - elements are mini-views
that can be included in layouts or views. However, since they are
intended to be reliant on the information passed to the view they're
included in, they lose
at 12:14 AM, James K james.m.k...@gmail.com wrote:
There is no entity in CakePHP that work like Joomla modules out of the
box. The closest thing would be elements - elements are mini-views
that can be included in layouts or views. However, since they are
intended to be reliant
Yes, I agree. An element is just a partial view, and would have to be
copied into and reworked for every application. Not to mention that
you can't link an element to content in the database.
I think setting up the core of the modules as a Model would allow for
a lot of flexibility. An Observer
Hi , I wonder if this is possible ,
lets say i have 2 modules
1. login box = i made it on folder http://localhost/cake/login/log
2. news box = i made it on folder http://localhost/cake/news/show
Now i want to make 1 page that will conteins both of the modules , let
say that ths url of this page
model data on all your modules you can either use [2]
the all required models in your controller and pass the data to your
view or use requestAction [3] to fetch data for another controller.
[1] http://book.cakephp.org/view/97/Elements
[2]
http://book.cakephp.org/view/51/Controller-Attributes
on all your modules you can either use [2]
the all required models in your controller and pass the data to your
view or use requestAction [3] to fetch data for another controller.
[1]http://book.cakephp.org/view/97/Elements
[2]http://book.cakephp.org/view/51/Controller-Attributes#components-help
An element is simply a re-usable view ... rather than repeat a whole
view or a part of a view which is used multiple times across your app,
create a single element and use that across multiple views.
--~--~-~--~~~---~--~~
You received this message because you are
Thanks , and this re-usable view can have a controller ?
If i want this view to take data from DB for example login box .
How do i do the logic part on this view ?
Thanks.
On Jan 3, 12:04 am, WebbedIT p...@webbedit.co.uk wrote:
An element is simply a re-usable view ... rather than repeat a
The element refers to data just like any other view. I use an element
to display task listings, and by choosing which data to pass to the
element, I get different displays on the same page:
div class=related
?php if (isset($userSlots)):?
h3?php __('You are signed up for');?/h3
?php
Have you read the link offered eariler?
http://book.cakephp.org/view/97/Elements
We are only repeating content within this page when explaining the use
of elements to you.
Regards,
Paul.
--~--~-~--~~~---~--~~
You received this message because you are subscribed
You can implement something like Joomla modules fairly easily via
CakePHP's elements. Elements are fairly self-contained blocks of code
that can be called from views or even controllers. The only difference
is you have to pre-fetch your data and pass it to the element rather
than have the element
problems that came along development. I was using Joomla
for a few years so I'm used to refer some elements like pools,
latest comments, tags cloud, menus etc. as MODULES.
My question is what would be a good approach to build them in Cake
PHP.
For example: should I define a new helper/component
cloud, menus etc. as MODULES.
My question is what would be a good approach to build them in Cake
PHP.
For example: should I define a new helper/component that would check
installed and active modules and then call that helper from a view or
template file?
Some guidelines how to approach would
I'm building a shopping cart and want to integrate shipping APIs. Now,
I've found existing code for UPS Rates Services and something
similar for FedEx. But what I really want is an API that will actually
create a shipment, schedule it for pickup, provide a label and
tracking code, etc. You can't
Hi all :)
I'm currently working on a CMS-Like webapp. You're able to add an
arbitary amount of content-elements to a page - which are sortable.
Everyhtings workin fine. Now i want these content-elements to be some
sort of modules. So that i can have several different content-element-
types like
Okay, this might sound a bit crazy at first, but there's real reasons
for doing this.
We're a design firm that developed a CMS to handle the advanced layout
requirement of our projects. The main thing is being able to build
pages which content fields change in name, amount and type. And that's
I've got a series of web services implemented as models that a controller
might call as such:
$a = $this-WebService1-findByName($searchstring1);
$b = $this-WebService2-findByName($searchstring2)
$c = $this-WebService3-findByName($searchstring3)
// Do something with $a, $b, and $c, then pass it to
I've tried to post this article in Bakery. But it returned blank
page...
Have a look here:
http://xoopscube.org/modules/xhnewbb/viewtopic.php?topic_id=582
:)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP
@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of
stefanb
Sent: 10. oktober 2007 10:36
To: Cake PHP
Subject: Modules?
Does Cake support the use of modules?
www.example.com/module/controller/action/var1/val1/var2/val2
--~--~-~--~~~---~--~~
You received
or the group ?
Its called plugins in cake
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of
stefanb
Sent: 10. oktober 2007 10:36
To: Cake PHP
Subject: Modules?
Does Cake support the use of modules?
www.example.com/module/controller
: Modules?
Does Cake support the use of modules?
www.example.com/module/controller/action/var1/val1/var2/val2
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP group.
To post to this group, send email
. oktober 2007 10:36
To: Cake PHP
Subject: Modules?
Does Cake support the use of modules?
www.example.com/module/controller/action/var1/val1/var2/val2
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP
No, the plugin part is right
But the first part about you not bothering to search for answer first is also
true
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So
You can consider plugins to be modules of CakePHP as they are built to
be able to integrate with any Cake installation.
On Oct 11, 7:39 am, stefanb [EMAIL PROTECTED] wrote:
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote
] On Behalf Of stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote:
Though the first half is the correct one.
On Oct 10, 10:24 am, stefanb [EMAIL
PROTECTED] On Behalf Of stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote:
Though the first half is the correct one.
On Oct 10, 10:24 am, stefanb [EMAIL
Thank you, finally a reasonable answer! :)
On Oct 11, 3:32 pm, savagekabbage [EMAIL PROTECTED] wrote:
You can consider plugins to be modules of CakePHP as they are built to
be able to integrate with any Cake installation.
On Oct 11, 7:39 am, stefanb [EMAIL PROTECTED] wrote:
So a plugin
true
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of
stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED
Does Cake support the use of modules?
www.example.com/module/controller/action/var1/val1/var2/val2
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP group.
To post to this group, send email to cake-php
Did you even bother to look in the manual or the group ?
Its called plugins in cake
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of stefanb
Sent: 10. oktober 2007 10:36
To: Cake PHP
Subject: Modules?
Does Cake support the use of modules
[mailto:[EMAIL PROTECTED] On Behalf Of stefanb
Sent: 10. oktober 2007 10:36
To: Cake PHP
Subject: Modules?
Does Cake support the use of modules?
www.example.com/module/controller/action/var1/val1/var2/val2
--~--~-~--~~~---~--~~
You received this message
modules.
On Sep 19, 10:34 pm, John David Anderson (_psychic_)
[EMAIL PROTECTED] wrote:
On Sep 19, 2007, at 2:12 PM, [EMAIL PROTECTED] wrote:
Hi,
I would like to know if there is the same concept that the
modules of
the zend framework on cakephp :
http://framework.zend.com/manual
PROTECTED] wrote:
http://manual.cakephp.org/chapter/plugins
On 9/19/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
yep i confirm. but so how ? :(
On 20 sep, 00:08, Mech7 [EMAIL PROTECTED] wrote:
But this is not really about the libs and webroot but about
selfcontaining modules.
On Sep 19
On Sep 19, 2007, at 2:12 PM, [EMAIL PROTECTED] wrote:
Hi,
I would like to know if there is the same concept that the modules of
the zend framework on cakephp :
http://framework.zend.com/manual/en/zend.controller.modular.html
(it's like a way to make multiple sites with only one zend
the controllers of
www.domain.com (like the controller to know if you're loggued ..etc)
On zend framework, with the modules, you have a default module
(www.domain.com for me) that contains his own controllers / views/
models/ and you can add as much modules as you want.
module1, module2
default
Hi,
I would like to know if there is the same concept that the modules of
the zend framework on cakephp :
http://framework.zend.com/manual/en/zend.controller.modular.html
(it's like a way to make multiple sites with only one zend framework)
thanks
://manual.cakephp.org/chapter/plugins
On 9/19/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
yep i confirm. but so how ? :(
On 20 sep, 00:08, Mech7 [EMAIL PROTECTED] wrote:
But this is not really about the libs and webroot but about
selfcontaining modules.
On Sep 19, 10:34 pm, John David
, Mech7 [EMAIL PROTECTED] wrote:
But this is not really about the libs and webroot but about
selfcontaining modules.
On Sep 19, 10:34 pm, John David Anderson (_psychic_)
[EMAIL PROTECTED] wrote:
On Sep 19, 2007, at 2:12 PM, [EMAIL PROTECTED] wrote:
Hi,
I would like to know
:
But this is not really about the libs and webroot but about
selfcontaining modules.
On Sep 19, 10:34 pm, John David Anderson (_psychic_)
[EMAIL PROTECTED] wrote:
On Sep 19, 2007, at 2:12 PM, [EMAIL PROTECTED] wrote:
Hi,
I would like to know if there is the same concept that the
modules of
the zend
Maybe you could change the bootstrap file and make the array name
dynamic of the controller that is being requested ?
$modelPaths = array('full path to models', 'second full path to
models', 'etc...');
$viewPaths = array('this path to views', 'second full path to views',
'etc...');
Hey guys !!
I've been thinking from a last few days, that how many hours can I
save if I build a library of all my reusable code/modules which is
very easily accessible while working on a project... ? Dont you think
that will save time ?
Some of you might be already doing it ?
The problem right
many hours can I
save if I build a library of all my reusable code/modules which is
very easily accessible while working on a project... ? Dont you think
that will save time ?
Some of you might be already doing it ?
The problem right now I'm facing is, I dont keep track of every
reusable
keep an organised file tree.
Simon
On Jul 2, 4:42 pm, Max [EMAIL PROTECTED] wrote:
Hey guys !!
I've been thinking from a last few days, that how many hours can I
save if I build a library of all my reusable code/modules which is
very easily accessible while working on a project... ? Dont you
Well you might want to look up layouts and elements in the manual.
http://manual.cakephp.org/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP group.
To post to this group, send email to
I am very new to MVC and CakePHP and was wondering what the best way is
to create a site with modules. I am talking about modules like
zymic.com's a poll, affiliates, whatever.
How do I include them on every page while still including new content
in the content box? Is it better to use seperate
85 matches
Mail list logo
