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'
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
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
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.
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
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
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
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
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
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.
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
: 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
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
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
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
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
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)
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
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
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
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
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
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
: 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
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
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
26 matches
Mail list logo
