Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Felix and the rest,
I have tried your suggestion to create a vendor branch. I have a
directory with cake setup as svn:externals, however, if I try to copy
and commit it, I get the following error:
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn update
Fetching external item into '1.2.x.x'
External at revision 4273.
At revision 26.
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn copy 1.2.x.x/ 1.2.x.x.4273/
A 1.2.x.x.4273
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn commit
Adding cakephp/1.2.x.x.4273
svn: Commit failed (details follow):
svn: PROPFIND request failed on '/repo/trunk/cake/1.2.x.x'
svn: PROPFIND of '/repo/trunk/cake/1.2.x.x': 405 Method Not Allowed
(https://dev.schapendonk.org)
svn: Your commit message was left in a temporary file:
svn:'/home/martin/findem/vendor/svn-commit.tmp'
[EMAIL PROTECTED]:~/findem/vendor/cakephp$
The path /repo/trunk/cake/1.2.x.x refers to CakePHP's svn repository!
It seems that svn copy remembers where it got the files from.
What is the proper way to tag a directory that is a svn:externals?
2006/12/4, Felix Geisendörfer [EMAIL PROTECTED]:
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
Nothing is out of the vendor package ; ). A complete copy of the latest
version of CakePHP always rests in /vendors/cakephp/current. When a new
CakePHP version is released, you checkout /vendors/cakephp/current and
simply copy the new version over the old one. If files were removed you have
to delete them manually (via SVN), but that doesn't happen very often. Then
you commit the new version. After that you tag it in /vendors/cakephp (in
our case as r4064). After that you simply merge the changes between the last
CakePHP version (r3825) and the current one (r4064) into /trunk (your
working copy of it). In case things inside /app have changed, *only* those
changes will be applied, no custom mods will be overwritten. After merging
the update in, you commit /trunk and voila, you updated CakePHP.
For a better understanding checkout a typical vendor branch folder layout:
vendors
|---cakephp
|---|---r4064
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---current
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---r3825
|---|---|---app
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---|---VERSION.txt
I hope that helps.
-- Felix
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Marcelo de Moraes Serpa wrote:
Well, most of the times replacing the /cake folder will be enough.
Sometimes however, files inside /app change, like /app/webroot/index.php. In
those cases you should replace them as well to be on the safe side.
In order to see what has changed in those files you can check the SVN
difference between your local version and the one you intent to upgrade to.
The best way to get this hassle out of your life is to manage your project
in SVN and to use a vendor branch for CakePHP. This makes updating very easy
and I highly recommend it.
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
On 12/4/06, Claudio Poli [EMAIL PROTECTED] wrote:
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--
Martin Schapendonk, [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Hey Martin,
vendor branching means that you *do not* use svn:externals but update
the vendor branch manually from time to time yourself.
This page has all information about this process:
http://svnbook.red-bean.com/en/1.1/ch07s05.html
Let me know if that helps,
-- Felix Geisendörfer aka the_undefined
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Martin Schapendonk wrote:
Felix and the rest,
I have tried your suggestion to create a vendor branch. I have a
directory with cake setup as svn:externals, however, if I try to copy
and commit it, I get the following error:
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn update
Fetching external item into '1.2.x.x'
External at revision 4273.
At revision 26.
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn copy 1.2.x.x/ 1.2.x.x.4273/
A 1.2.x.x.4273
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn commit
Adding cakephp/1.2.x.x.4273
svn: Commit failed (details follow):
svn: PROPFIND request failed on '/repo/trunk/cake/1.2.x.x'
svn: PROPFIND of '/repo/trunk/cake/1.2.x.x': 405 Method Not Allowed
(https://dev.schapendonk.org)
svn: Your commit message was left in a temporary file:
svn:'/home/martin/findem/vendor/svn-commit.tmp'
[EMAIL PROTECTED]:~/findem/vendor/cakephp$
The path /repo/trunk/cake/1.2.x.x refers to CakePHP's svn repository!
It seems that svn copy remembers where it got the files from.
What is the proper way to tag a directory that is a svn:externals?
2006/12/4, Felix Geisendörfer [EMAIL PROTECTED]:
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
Nothing is out of the vendor package ; ). A complete copy of the latest
version of CakePHP always rests in /vendors/cakephp/current. When a new
CakePHP version is released, you checkout /vendors/cakephp/current and
simply copy the new version over the old one. If files were removed you have
to delete them manually (via SVN), but that doesn't happen very often. Then
you commit the new version. After that you tag it in /vendors/cakephp (in
our case as r4064). After that you simply merge the changes between the last
CakePHP version (r3825) and the current one (r4064) into /trunk (your
working copy of it). In case things inside /app have changed, *only* those
changes will be applied, no custom mods will be overwritten. After merging
the update in, you commit /trunk and voila, you updated CakePHP.
For a better understanding checkout a typical vendor branch folder layout:
vendors
|---cakephp
|---|---r4064
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---current
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---r3825
|---|---|---app
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---|---VERSION.txt
I hope that helps.
-- Felix
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Marcelo de Moraes Serpa wrote:
Well, most of the times replacing the /cake folder will be enough.
Sometimes however, files inside /app change, like /app/webroot/index.php. In
those cases you should replace them as well to be on the safe side.
In order to see what has changed in those files you can check the SVN
difference between your local version and the one you intent to upgrade to.
The best way to get this hassle out of your life is to manage your project
in SVN and to use a vendor branch for CakePHP. This makes updating very easy
and I highly recommend it.
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
On 12/4/06, Claudio Poli [EMAIL PROTECTED] wrote:
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Yeah, that helps :-)
I thought I could take the easy route by not using svn_load_dirs,
but svn:externals instead.
Just an idea that pops up: I can simply update cakephp in the trunk by
merging directly from the svn:externals directory:
[EMAIL PROTECTED]:~/findem/trunk$ svn merge -r4272:4273
../vendor/cakephp/1.2.x.x/ cakephp/
(supposed that the last version I integrated was revision 4272 and I
wanted to merge revision 4273 in the trunk)
Regards, Martin
2007/1/12, Felix Geisendörfer [EMAIL PROTECTED]:
Hey Martin,
vendor branching means that you *do not* use svn:externals but update the
vendor branch manually from time to time yourself.
This page has all information about this process:
http://svnbook.red-bean.com/en/1.1/ch07s05.html
Let me know if that helps,
-- Felix Geisendörfer aka the_undefined
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Martin Schapendonk wrote:
Felix and the rest,
I have tried your suggestion to create a vendor branch. I have a
directory with cake setup as svn:externals, however, if I try to copy
and commit it, I get the following error:
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn update
Fetching external item into '1.2.x.x'
External at revision 4273.
At revision 26.
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn copy 1.2.x.x/ 1.2.x.x.4273/
A 1.2.x.x.4273
[EMAIL PROTECTED]:~/findem/vendor/cakephp$ svn commit
Adding cakephp/1.2.x.x.4273
svn: Commit failed (details follow):
svn: PROPFIND request failed on '/repo/trunk/cake/1.2.x.x'
svn: PROPFIND of '/repo/trunk/cake/1.2.x.x': 405 Method Not Allowed
(https://dev.schapendonk.org)
svn: Your commit message was left in a temporary file:
svn: '/home/martin/findem/vendor/svn-commit.tmp'
[EMAIL PROTECTED]:~/findem/vendor/cakephp$
The path /repo/trunk/cake/1.2.x.x refers to CakePHP's svn repository!
It seems that svn copy remembers where it got the files from.
What is the proper way to tag a directory that is a svn:externals?
2006/12/4, Felix Geisendörfer [EMAIL PROTECTED]:
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
Nothing is out of the vendor package ; ). A complete copy of the latest
version of CakePHP always rests in /vendors/cakephp/current. When a new
CakePHP version is released, you checkout /vendors/cakephp/current and
simply copy the new version over the old one. If files were removed you have
to delete them manually (via SVN), but that doesn't happen very often. Then
you commit the new version. After that you tag it in /vendors/cakephp (in
our case as r4064). After that you simply merge the changes between the last
CakePHP version (r3825) and the current one (r4064) into /trunk (your
working copy of it). In case things inside /app have changed, *only* those
changes will be applied, no custom mods will be overwritten. After merging
the update in, you commit /trunk and voila, you updated CakePHP.
For a better understanding checkout a typical vendor branch folder layout:
vendors
|---cakephp
|---|---r4064
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---current
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---r3825
|---|---|---app
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---|---VERSION.txt
I hope that helps.
-- Felix
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Marcelo de Moraes Serpa wrote:
Well, most of the times replacing the /cake folder will be enough.
Sometimes however, files inside /app change, like /app/webroot/index.php.
In
those cases you should replace them as well to be on the safe side.
In order to see what has changed in those files you can check the SVN
difference between your local version and the one you intent to upgrade to.
The best way to get this hassle out of your life is to manage your project
in SVN and to use a vendor branch for CakePHP. This makes updating very easy
and I highly recommend it.
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
On 12/4/06, Claudio Poli [EMAIL PROTECTED] wrote:
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Great work, installed new version right away and everything works just good. Switching to lazy-loading is a good decision. CakePHP makes it already easy enough to program, performance should be another concern and in this case the decision to go for performance is definately the right one. --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
The change about Model issue was what i asked for! Good Job Bakers!!! --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
RE: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Well, its not often that you can take something out of the freezer and have it taste better than before, but that's what happened. We received a few more bugs and as Gwoo said in a message last week, speed was an issue. So, with the bugs that came in, we spent some time making things work a bit faster. While speed differences may vary based on your system, we noticed a nice increase[1]. I don't know if I've got biased by your comment, but I DID notice a speed increase. Nicee :) The main increase comes from the lazy loading of models. Good call. The other nice addition in 1.1.11.4064 is updated functionality of the Configure class Thanks for letting me get rid of the $GLOBALS way to do an application config. Now code looks much smoother. Enjoy I most certainly am. Thanks guys!! -MI --- Remember, smart coders answer ten questions for every question they ask. So be smart, be cool, and share your knowledge. BAKE ON! --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
thanks for another great release :) --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
One thing I'm still not getting a grasp on, with the whole updating-to-the-newest-version-of-cake thing, is that sometimes I notice that files in the app directory have changed. For instance, /app/webroot/index.php is newer. Does it need to be replaced, or do I only have to replace the /cake folder? --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Well, most of the times replacing the /cake folder will be enough. Sometimes however, files inside /app change, like /app/webroot/index.php. In those cases you should replace them as well to be on the safe side. In order to see what has changed in those files you can check the SVN difference between your local version and the one you intent to upgrade to. The best way to get this hassle out of your life is to manage your project in SVN and to use a vendor branch http://svnbook.red-bean.com/en/1.1/ch07s05.html for CakePHP. This makes updating very easy and I highly recommend it. -- Felix Geisendörfer aka the_undefined -- http://www.thinkingphp.org http://www.fg-webdesign.de joel wrote: One thing I'm still not getting a grasp on, with the whole updating-to-the-newest-version-of-cake thing, is that sometimes I notice that files in the app directory have changed. For instance, /app/webroot/index.php is newer. Does it need to be replaced, or do I only have to replace the /cake folder? --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Well, most of the times replacing the /cake folder will be enough.
Sometimes however, files inside /app change, like /app/webroot/index.php. In
those cases you should replace them as well to be on the safe side.
In order to see what has changed in those files you can check the SVN
difference between your local version and the one you intent to upgrade to.
The best way to get this hassle out of your life is to manage your project
in SVN and to use a vendor
branchhttp://svnbook.red-bean.com/en/1.1/ch07s05.htmlfor CakePHP. This
makes updating very easy and I highly recommend it.
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
On 12/4/06, Claudio Poli [EMAIL PROTECTED] wrote:
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
RE: CakePHP 1.1.11.4064, thawed and redelivered better than before.
You shouldn't set models at the AppController level.
From this post:
http://groups-beta.google.com/group/cake-php/browse_thread/thread/df5e0b3a75
d0202a
Larry says:
You should not define the $uses var in your AppController.
When you set the $uses var it should be done in child classes, and only set
if you are not following naming conventions, or you need more then one model
in the controller.
If you follow naming convention loading of models is automatic and you do
not have to define the $uses var. Adding to your AppController sets the same
$uses on all child classes.
Also be aware of CakePHP 1.1.11.4064 regarding models:
If you did something like this before 1.1.11.4064:
$myModel = new Model();
You now have to do:
loadModel('Model');
$myModel = new Model();
-MI
---
Remember, smart coders answer ten questions for every question they ask.
So be smart, be cool, and share your knowledge.
BAKE ON!
-Mensaje original-
De: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] En nombre
de Claudio Poli ?
Enviado el: Lunes, 04 de Diciembre de 2006 01:39 p.m.
Para: Cake PHP
Asunto: Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Il giorno 04/dic/06, alle ore 18:05, Mariano Iglesias ha scritto:
You shouldn't set models at the AppController level.
From this post:
http://groups-beta.google.com/group/cake-php/browse_thread/thread/
df5e0b3a75
d0202a
Larry says:
You should not define the $uses var in your AppController.
When you set the $uses var it should be done in child classes, and
only set
if you are not following naming conventions, or you need more then
one model
in the controller.
If you follow naming convention loading of models is automatic and
you do
not have to define the $uses var. Adding to your AppController sets
the same
$uses on all child classes.
Also be aware of CakePHP 1.1.11.4064 regarding models:
If you did something like this before 1.1.11.4064:
$myModel = new Model();
You now have to do:
loadModel('Model');
$myModel = new Model();
got it, thanks.
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Il giorno 04/dic/06, alle ore 18:04, joel ha scritto: With this version of Cake, I now get an error on my site which says: Fatal error: Class 'ConnectionManager' not found in /cake/libs/session.php on line 445 Does anyone know what this is all about, or where I might be calling that class? are you saving session in database instead of php/cake? --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Claudio Poli wrote: are you saving session in database instead of php/cake? Yes, I am. --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Hey Felix, really good suggestion... I'm going to try implementing
this. However, I would I manage changes to files inside app/webroot
(as you said) considering they're out of the vendor package?
Nothing is out of the vendor package ; ). A complete copy of the latest
version of CakePHP always rests in /vendors/cakephp/current. When a new
CakePHP version is released, you checkout /vendors/cakephp/current and
simply copy the new version over the old one. If files were removed you
have to delete them manually (via SVN), but that doesn't happen very
often. Then you commit the new version. After that you tag it in
/vendors/cakephp (in our case as r4064). After that you simply merge the
changes between the last CakePHP version (r3825) and the current one
(r4064) into /trunk (your working copy of it). In case things inside
/app have changed, *only* those changes will be applied, no custom mods
will be overwritten. After merging the update in, you commit /trunk and
voila, you updated CakePHP.
For a better understanding checkout a typical vendor branch folder layout:
vendors
|---cakephp
|---|---r4064
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---current
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---r3825
|---|---|---app
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---|---VERSION.txt
I hope that helps.
-- Felix
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Marcelo de Moraes Serpa wrote:
Well, most of the times replacing the /cake folder will be enough.
Sometimes however, files inside /app change, like
/app/webroot/index.php. In those cases you should replace them as
well to be on the safe side.
In order to see what has changed in those files you can check the
SVN difference between your local version and the one you intent
to upgrade to. The best way to get this hassle out of your life is
to manage your project in SVN and to use a vendor branch
http://svnbook.red-bean.com/en/1.1/ch07s05.html for CakePHP.
This makes updating very easy and I highly recommend it.
Hey Felix, really good suggestion... I'm going to try implementing
this. However, I would I manage changes to files inside app/webroot
(as you said) considering they're out of the vendor package?
On 12/4/06, *Claudio Poli * [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Uoha! Thanks a lot for the in-depth explanation! :) It surely helped a lot
:D
Marcelo.
On 12/4/06, Felix Geisendörfer [EMAIL PROTECTED] wrote:
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
Nothing is out of the vendor package ; ). A complete copy of the latest
version of CakePHP always rests in /vendors/cakephp/current. When a new
CakePHP version is released, you checkout /vendors/cakephp/current and
simply copy the new version over the old one. If files were removed you have
to delete them manually (via SVN), but that doesn't happen very often. Then
you commit the new version. After that you tag it in /vendors/cakephp (in
our case as r4064). After that you simply merge the changes between the last
CakePHP version (r3825) and the current one (r4064) into /trunk (your
working copy of it). In case things inside /app have changed, *only* those
changes will be applied, no custom mods will be overwritten. After merging
the update in, you commit /trunk and voila, you updated CakePHP.
For a better understanding checkout a typical vendor branch folder layout:
vendors
|---cakephp
|---|---r4064
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---current
|---|---|---app
|---|---|---docs
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---r3825
|---|---|---app
|---|---|---cake
|---|---|---vendors
|---|---|---index.php
|---|---|---.htaccess
|---|---|---VERSION.txt
I hope that helps.
-- Felix
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Marcelo de Moraes Serpa wrote:
Well, most of the times replacing the /cake folder will be enough.
Sometimes however, files inside /app change, like /app/webroot/index.php. In
those cases you should replace them as well to be on the safe side.
In order to see what has changed in those files you can check the SVN
difference between your local version and the one you intent to upgrade to.
The best way to get this hassle out of your life is to manage your project
in SVN and to use a vendor
branchhttp://svnbook.red-bean.com/en/1.1/ch07s05.htmlfor CakePHP. This
makes updating very easy and I highly recommend it.
Hey Felix, really good suggestion... I'm going to try implementing this.
However, I would I manage changes to files inside app/webroot (as you said)
considering they're out of the vendor package?
On 12/4/06, Claudio Poli [EMAIL PROTECTED] wrote:
I'm having some problem..
In an application I've loaded a bunch of model into app_controller.php
like
var $uses = array('Blah', 'Etc');
to be available in every controller; after the upgrade into every
controller I go CakePHP tells me that he wants a model with the same
name as the controller.
for example I've a Welcome controller that do not have any model but
uses an Article model.
what's going wrong here?
thanks
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Claudio Poli wrote:
are you saving session in database instead of php/cake?
Yes, I am.
ok, same problem here.
Add this to your bootstrap.php file for now.
uses('model' . DS . 'connection_manager');
--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access public
*/
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Had the same problem, too. Session in DB instead of files. Seems as if one line is missing from cake/bootstrap.php that was present in the previous release: require LIBS . 'model' . DS . 'connection_manager.php'; If you don't want to change the core, you can also add this line to your own ap/config/bootstrap.php file. Hope this helps Heiner Claudio Poli wrote: are you saving session in database instead of php/cake? Yes, I am. ok, same problem here. --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
Hi,
On Dec 4, 2:27 pm, Larry E. Masters aka PhpNut [EMAIL PROTECTED]
wrote:
The main increase comes from the lazy loading of models. Previous versions
of CakePHP loaded all the models in the models directory. This functionality
made access to models easier, but came at the expense of valuable processing
time. The change results in a need to make sure you loadModel('ModelName');
if you use $ModelName = new ModelName() somewhere in your code. We have seen
several examples, particularly in reference to components creating model
instances. This was not recommended practice, so remember that you need to
load the model now if you plan on creating an instance.
I had a patch for lazy-loaded models that I have been using for some
time now.
Details here:
http://abing.gotdns.com/posts/2006/lazy-loaded-models-for-cakephp/
Patch is here:
http://abing.gotdns.com/cake/diffs/10-lazy-loaded-models.diff
The current mainstream implementation breaks client code that relies on
the previous model loading behavior (all models loaded). But that can
be fixed easily for most apps. My solution was to create a separate
directory for models that were lazy-loaded so that client code that
relied on the mainstream model loading behavior continued to work
without problems.
Anyway, it's great that models are now lazy loaded by default in the
mainstream version. One question though: are plugins able to take
advantage of lazy-loading as well?
Thanks and keep the good stuff coming!
--
_nimrod_a_abing_
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
I don't know if I've got biased by your comment, but I DID notice a speed increase. Nicee :) As did I. A significant increase, in fact! Way to go you guys! Definitely a great job very well done! thnx, Christoph --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
You should submit patches to trac and try not to alter the api. At the very least send someone on the dev team an email with your thoughts. This way the whole community benefits without needing to handle third party patches --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
As did I. A significant increase, in fact! Way to go you guys! Definitely a great job very well done! Thanks Christoph, The improvement had been planned for sometime I just hate thinking about optimization when code is not where I would like it to be. I feel optimization is to be done in refactoring. My motto: Make it work, then make it work better I will continue to use this motto with the future development of CakePHP, so stay tuned, and enjoy. -- /** * @author Larry E. Masters * @var string $userName * @param string $realName * @returns string aka PhpNut * @access public */ --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
RE: CakePHP 1.1.11.4064, thawed and redelivered better than before.
I think it's a smart idea. Perfectionism (like any other extreme) is a very bad thing for developers because it tends to slow down delivery time. -MI --- Remember, smart coders answer ten questions for every question they ask. So be smart, be cool, and share your knowledge. BAKE ON! De: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] En nombre de Larry E. Masters aka PhpNut Enviado el: Martes, 05 de Diciembre de 2006 12:43 a.m. Para: cake-php@googlegroups.com Asunto: Re: CakePHP 1.1.11.4064, thawed and redelivered better than before. My motto: Make it work, then make it work better --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: CakePHP 1.1.11.4064, thawed and redelivered better than before.
On Dec 5, 11:42 am, gwoo [EMAIL PROTECTED] wrote: You should submit patches to trac and try not to alter the api. At the very least send someone on the dev team an email with your thoughts. This way the whole community benefits without needing to handle third party patches I always try to stay compatible with the mainstream CakePHP. So far the patches available on my website do not introduce any API incompatibilities as far as I can tell. I already have one user who reports success (without modifying his app) using my patches for the following: - delegating actions to classes http://abing.gotdns.com/cake/diffs/07-delegate-controller-actions-to-action-class.diff - vendor customizable dispatcher http://abing.gotdns.com/cake/diffs/02-custom-dispatcher.diff - lazy model loading http://abing.gotdns.com/cake/diffs/10-lazy-loaded-models.diff - hide/expose controller methods http://abing.gotdns.com/cake/diffs/03-hide-expose-controller-actions.diff I also have at least two users who are using my alternate implementation of themeable view class. I attempted to submit the patch for lazy-loaded models about a month ago on trac but there was some error on trac preventing me from attaching the patch. I can't recall what the error was and I never got around to submitting it again. Anyway, the mainstream implementation of lazy-loaded models is currently being integrated into my personal CakePHP tree so I will be updating it soon. I consider my current work on CakePHP to be highly experimental and too domain-specific (they are for a CMS I am working on) to be of any use to the general CakePHP user base which is why I haven't made these widely available. In case anyone else is interested, the patches are available here: http://abing.gotdns.com/cake/diffs/ Instructions for using these patches are here: http://abing.gotdns.com/posts/2006/modified-cakephp/ Perhaps the easiest way to obtain these patches is to use darcs http://www.darcs.net/ and do: darcs get http://abing.gotdns.com/darcs/repos/cake Unless otherwise stated, these patches are all under the same licensing terms as CakePHP itself. -- _nimrod_a_abing_ --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
