Re: CDN for CakePHP

2014-09-29 Thread majna
See https://github.com/cakephp/cakephp/issues/2149

On Monday, September 29, 2014 12:43:53 PM UTC+2, Kan Samy wrote:
>
> Thanks for your reply Cherankrish.
> I am using Cloudfront CDN and I have created the distribution and 
> generated the cdn url. Now I dont know where(which file) to map the cdn url 
> in my CakePHP project?
>
> On Monday, September 29, 2014 4:05:57 PM UTC+5:30, cheran krishnamoorthy 
> wrote:
>>
>> Try Cloudflare.
>>
>> On Mon, Sep 29, 2014 at 12:53 PM, Kan Samy  
>> wrote:
>>
>>>  I would like to activate the content delivery network for my CakePHP 
>>> project. Can someone help me to activate CDN for my CakePHP site?
>>>
>>> -- 
>>> Like Us on FaceBook https://www.facebook.com/CakePHP
>>> Find us on Twitter http://twitter.com/CakePHP
>>>
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "CakePHP" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to cake-php+u...@googlegroups.com.
>>> To post to this group, send email to cake...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/cake-php.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> *Cherankrish*
>> chera...@gmail.com
>> Skype: cherankrish
>>
>> QR code :
>>
>>  

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: Warning (512): cake_model cache was unable to write

2014-09-29 Thread majna
"unable write 'default_aptutori_a' to Apc cache"

I guess your app/Config/core.php needs to be updated for 2.5.
APC as a default cache engine was removed two years ago, in 2.3
https://github.com/cakephp/cakephp/commit/2f7f5e13224537eaa4da6b825b1d106bebc35d05

On Tuesday, September 30, 2014 6:26:39 AM UTC+2, Jeremy Burns wrote:
>
> I had a similar issue when running MAMP locally. I fixed it by turning off 
> MAMP’s internal caching. Not sure if that’s the same issue you’re facing. 
>
> On 30 Sep 2014, at 01:12, Andras Kende > 
> wrote: 
>
> > Try deleting the files within app/tmp folders. 
> > 
> > and adding  'mask' => 0777 to 
> > core.php 
> > Cache::config('_cake_core_', array(... 
> > Cache::config('_cake_model_', array(... 
> > https://github.com/cakephp/cakephp/blob/master/app/Config/core.php#L294 
> > 
> > Andras Kende 
> > 
> > 
> > On Sep 29, 2014, at 4:02 PM, ajt > 
> wrote: 
> > 
> >> 2.5 but I checked many posts on the issue and I dont think that makes 
> any difference. 
> >> The only solution was to chmod the app/tmp folders and subfolders but i 
> did that. 
> >> 
> >> I am using cpanel and have no command prompt to run scripts 
> >> 
> >> -- 
> >> Like Us on FaceBook https://www.facebook.com/CakePHP 
> >> Find us on Twitter http://twitter.com/CakePHP 
> >> 
> >> --- 
> >> You received this message because you are subscribed to the Google 
> Groups "CakePHP" group. 
> >> To unsubscribe from this group and stop receiving emails from it, send 
> an email to cake-php+u...@googlegroups.com . 
> >> To post to this group, send email to cake...@googlegroups.com 
> . 
> >> Visit this group at http://groups.google.com/group/cake-php. 
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > Like Us on FaceBook https://www.facebook.com/CakePHP 
> > Find us on Twitter http://twitter.com/CakePHP 
> > 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "CakePHP" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to cake-php+u...@googlegroups.com . 
> > To post to this group, send email to cake...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/cake-php. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: Warning (512): cake_model cache was unable to write

2014-09-29 Thread Jeremy Burns
I had a similar issue when running MAMP locally. I fixed it by turning off 
MAMP's internal caching. Not sure if that's the same issue you're facing.

On 30 Sep 2014, at 01:12, Andras Kende  wrote:

> Try deleting the files within app/tmp folders.
> 
> and adding  'mask' => 0777 to
> core.php
> Cache::config('_cake_core_', array(...
> Cache::config('_cake_model_', array(...
> https://github.com/cakephp/cakephp/blob/master/app/Config/core.php#L294
> 
> Andras Kende
> 
> 
> On Sep 29, 2014, at 4:02 PM, ajt  wrote:
> 
>> 2.5 but I checked many posts on the issue and I dont think that makes any 
>> difference.
>> The only solution was to chmod the app/tmp folders and subfolders but i did 
>> that.
>> 
>> I am using cpanel and have no command prompt to run scripts
>> 
>> -- 
>> Like Us on FaceBook https://www.facebook.com/CakePHP
>> Find us on Twitter http://twitter.com/CakePHP
>> 
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "CakePHP" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to cake-php+unsubscr...@googlegroups.com.
>> To post to this group, send email to cake-php@googlegroups.com.
>> Visit this group at http://groups.google.com/group/cake-php.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> Like Us on FaceBook https://www.facebook.com/CakePHP
> Find us on Twitter http://twitter.com/CakePHP
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "CakePHP" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to cake-php+unsubscr...@googlegroups.com.
> To post to this group, send email to cake-php@googlegroups.com.
> Visit this group at http://groups.google.com/group/cake-php.
> For more options, visit https://groups.google.com/d/optout.

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: The (bad) perception and image of CakePHP in the public

2014-09-29 Thread Jeremy Burns : Class Outfit
This is so true. I'm a huge fan of Cake but we do feel like the whipping boys 
sometimes. I recently hired someone into a project and the first thing he tried 
to do was change the framework for a whole bunch of vague reasons like 'Laravel 
is just so much better'.

Perhaps someone can devise some simple benchmarking challenges that the 
guardians of the various frameworks can take up themselves and then compare the 
actual results, rather than letting a random person do it out of the box. A 
competition, if you will. So, for example, write a thousand records to a 
database, read them back, perform some function and render them to screen. Yes, 
yes, I know there would need to be some element of a level playing field with 
server spec and the like, but it could be done. Then each framework can show 
it's own best efforts and - importantly - will have no excuses about not 
understanding the framework or setting it up correctly.

I haven't had a 'job' for the past six years, but on the odd time that I decide 
a regular income would be nice I rarely - if ever - see CakePHP as a 
requirement. It's always Symfony, Zend, Drupal, Code Ingniter, sometimes 
Laravel, sometimes ROR and sometimes something else. That's awkward and I just 
can't help wondering if I am swimming against a tide. Perhaps everyone else is 
right and I am wrong? TBH, I'm not clever enough to be able to explain why Cake 
is the right choice compared to others; some help there would be cool.

On 30 Sep 2014, at 00:43, Reuben  wrote:

> My apologies, dereuromark, for the incorrect spelling of your handle.
> 
> On Tuesday, 30 September 2014 09:40:31 UTC+10, Reuben wrote:
> The few times that I've seen CakePHP compared to other PHP frameworks is in 
> performance tests, and it never looks pretty.  Usually the test is a very 
> simple Hello World test, or an action that reads/writes a bunch of records to 
> the database.  Not really real work tests, and no effort to configure the 
> application to make sure it's doing the best that it can (i.e. appropriate 
> cache options, etc).  
> 
> There have been a few articles written on CakePHP and performance, and all 
> the stuff you can do before complaining about the framework itself.
> 
> Unfortunately, when people are comparing PHP frameworks, they just look for 
> that performance index, and don't take too much notice of the merits of the 
> performance test taken.
> 
> My perception is that at last check, there might be room for improvement in 
> the event model, but I don't do all the other things that can be done to get 
> better performance out of CakePHP, before going there, so it's never been an 
> issue for me.  I also understand that start up times have been improved with 
> CakePHP 3, and the routing configuration required.
> 
> Of course, CakePHP is more than just performance of the framework.  The 
> documentation is great, the community is great and the core development team 
> are very approachable, via groups, irc and github issues. And the code 
> itself, should you need to look at it, is very readable.  The only part that 
> makes my brain hurt a little is the event system, especially when trying to 
> work out, when this event is fired, what is listening for it in the CakePHP 
> core.  
> 
> Maybe there could be some articles written about the CakePHP core, to make 
> TheBakery a little more attractive to read. I'm more likely to read CakePHP 
> articles from Mark Story, AD7six or deuromark than peruse the 1 or 2 
> paragraph articles on TheBakery.
> 
> Regards
> Reuben Helms
> 
> On Tuesday, 30 September 2014 07:15:54 UTC+10, Florian Krämer wrote:
> In the official CakePHP Facebook group Yanuar Nurcahyo asked about opinions 
> on that link 
> http://www.quora.com/Why-isnt-Cakephp-popular-despite-being-one-of-the-earliest-php-framework-to-be-written
> 
> I'll quote my own comment I've added to that posting:
> 
> I'm a little shocked about the wrong information people spreading there as 
> well as the amount of false information. Especially the one that got 4 
> up-votes. Most of the answers there read like FUD or written by people who 
> can't or won't read documentation. Also I really don't get why people always 
> "need" bleeding edge php support. There is no urgent need or do you migrate 
> you app / server to a new php version just because it's cool? The only 
> problem that CakePHP has is an image problem.
> 
> What I would like to discuss in this thread is reasons and solution to them. 
> Why has CakePHP such a negative perception? The thing that bothers me 
> personally the most is why the *uck do people say it has a bad documentation? 
> Seriously, I don't get it. Can't they find the documentation? Can't they use 
> it? Or is it really just FUD by some  fanboys?
> 
> The "stone age php version" isn't a very valid argument IMHO. Yes, I agree, 
> CakePHP felt behind other frameworks for at least ~2 years and I've missed 
> the namespace support more than one time. But that was 

Re: Warning (512): cake_model cache was unable to write

2014-09-29 Thread Andras Kende
Try deleting the files within app/tmp folders.

and adding  'mask' => 0777 to
core.php
Cache::config('_cake_core_', array(...
Cache::config('_cake_model_', array(...
https://github.com/cakephp/cakephp/blob/master/app/Config/core.php#L294

Andras Kende


On Sep 29, 2014, at 4:02 PM, ajt  wrote:

> 2.5 but I checked many posts on the issue and I dont think that makes any 
> difference.
> The only solution was to chmod the app/tmp folders and subfolders but i did 
> that.
> 
> I am using cpanel and have no command prompt to run scripts
> 
> -- 
> Like Us on FaceBook https://www.facebook.com/CakePHP
> Find us on Twitter http://twitter.com/CakePHP
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "CakePHP" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to cake-php+unsubscr...@googlegroups.com.
> To post to this group, send email to cake-php@googlegroups.com.
> Visit this group at http://groups.google.com/group/cake-php.
> For more options, visit https://groups.google.com/d/optout.

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: The (bad) perception and image of CakePHP in the public

2014-09-29 Thread Reuben
My apologies, dereuromark, for the incorrect spelling of your handle.

On Tuesday, 30 September 2014 09:40:31 UTC+10, Reuben wrote:
>
> The few times that I've seen CakePHP compared to other PHP frameworks is 
> in performance tests, and it never looks pretty.  Usually the test is a 
> very simple Hello World test, or an action that reads/writes a bunch of 
> records to the database.  Not really real work tests, and no effort to 
> configure the application to make sure it's doing the best that it can 
> (i.e. appropriate cache options, etc).  
>
> There have been a few articles written on CakePHP and performance, and all 
> the stuff you can do before complaining about the framework itself.
>
> Unfortunately, when people are comparing PHP frameworks, they just look 
> for that performance index, and don't take too much notice of the merits of 
> the performance test taken.
>
> My perception is that at last check, there might be room for improvement 
> in the event model, but I don't do all the other things that can be done to 
> get better performance out of CakePHP, before going there, so it's never 
> been an issue for me.  I also understand that start up times have been 
> improved with CakePHP 3, and the routing configuration required.
>
> Of course, CakePHP is more than just performance of the framework.  The 
> documentation is great, the community is great and the core development 
> team are very approachable, via groups, irc and github issues. And the code 
> itself, should you need to look at it, is very readable.  The only part 
> that makes my brain hurt a little is the event system, especially when 
> trying to work out, when this event is fired, what is listening for it in 
> the CakePHP core.  
>
> Maybe there could be some articles written about the CakePHP core, to make 
> TheBakery a little more attractive to read. I'm more likely to read CakePHP 
> articles from Mark Story, AD7six or deuromark than peruse the 1 or 2 
> paragraph articles on TheBakery.
>
> Regards
> Reuben Helms
>
> On Tuesday, 30 September 2014 07:15:54 UTC+10, Florian Krämer wrote:
>>
>> In the official CakePHP Facebook group Yanuar Nurcahyo asked about 
>> opinions on that link 
>> http://www.quora.com/Why-isnt-Cakephp-popular-despite-being-one-of-the-earliest-php-framework-to-be-written
>>
>> I'll quote my own comment I've added to that posting:
>>
>> I'm a little shocked about the wrong information people spreading there 
>>> as well as the amount of false information. Especially the one that got 4 
>>> up-votes. Most of the answers there read like FUD or written by people who 
>>> can't or won't read documentation. Also I really don't get why people 
>>> always "need" bleeding edge php support. There is no urgent need or do 
>>> you migrate you app / server to a new php version just because it's cool? 
>>> The only problem that CakePHP has is an image problem.
>>
>>
>> What I would like to discuss in this thread is reasons and solution to 
>> them. Why has CakePHP such a negative perception? The thing that bothers me 
>> personally the most is why the *uck do people say it has a bad 
>> documentation? Seriously, I don't get it. Can't they find the 
>> documentation? Can't they use it? Or is it really just FUD by some 
>>  fanboys?
>>
>> The "stone age php version" isn't a very valid argument IMHO. Yes, I 
>> agree, CakePHP felt behind other frameworks for at least ~2 years and I've 
>> missed the namespace support more than one time. But that was really the 
>> only language feature I was really missing. Everything else is sugar on top 
>> of the cake. I don't know if other people update their servers and apps for 
>> fun and if they do the required testing for free for their clients...but 
>> well, looks like some guys out there have more a cowboy-coder attitude than 
>> a professional one.
>>
>> Also I don't get why people complain about the architecture of CakePHP, 
>> yes it is different, yes it gives you everything out of the box and isn't a 
>> package made of 100 loose libs and then glued together. This is IMHO 
>> actually an advantage and makes it easy to get started with it. And 
>> seriously, how often do you change the ORM stack of  in 
>> reality? And on top of that, CakePHP 3.0, as far as I can tell, is more 
>> decoupled than 2.0 was. For example the face pattern in Laravel is, as far 
>> as I've worked with it and understood it, just one way you can use for 
>> dependency injection. The face seems to works like a proxy. I might be 
>> wrong, I haven't spent much time with it yet. SF2 is using a container 
>> object to deal with the dependencies. However, my point here is other 
>> frameworks *appear* to be more fancy and by this attract people who are 
>> looking for fancy things, "interesting" design patterns and architecture. 
>> Which brings us back to the cowboy-coder attitude. Something doesn't has to 
>> be fancy to just work.
>>
>> I know that for example Symfony gets a lot attention and expo

Re: The (bad) perception and image of CakePHP in the public

2014-09-29 Thread Reuben
The few times that I've seen CakePHP compared to other PHP frameworks is in 
performance tests, and it never looks pretty.  Usually the test is a very 
simple Hello World test, or an action that reads/writes a bunch of records 
to the database.  Not really real work tests, and no effort to configure 
the application to make sure it's doing the best that it can (i.e. 
appropriate cache options, etc).  

There have been a few articles written on CakePHP and performance, and all 
the stuff you can do before complaining about the framework itself.

Unfortunately, when people are comparing PHP frameworks, they just look for 
that performance index, and don't take too much notice of the merits of the 
performance test taken.

My perception is that at last check, there might be room for improvement in 
the event model, but I don't do all the other things that can be done to 
get better performance out of CakePHP, before going there, so it's never 
been an issue for me.  I also understand that start up times have been 
improved with CakePHP 3, and the routing configuration required.

Of course, CakePHP is more than just performance of the framework.  The 
documentation is great, the community is great and the core development 
team are very approachable, via groups, irc and github issues. And the code 
itself, should you need to look at it, is very readable.  The only part 
that makes my brain hurt a little is the event system, especially when 
trying to work out, when this event is fired, what is listening for it in 
the CakePHP core.  

Maybe there could be some articles written about the CakePHP core, to make 
TheBakery a little more attractive to read. I'm more likely to read CakePHP 
articles from Mark Story, AD7six or deuromark than peruse the 1 or 2 
paragraph articles on TheBakery.

Regards
Reuben Helms

On Tuesday, 30 September 2014 07:15:54 UTC+10, Florian Krämer wrote:
>
> In the official CakePHP Facebook group Yanuar Nurcahyo asked about 
> opinions on that link 
> http://www.quora.com/Why-isnt-Cakephp-popular-despite-being-one-of-the-earliest-php-framework-to-be-written
>
> I'll quote my own comment I've added to that posting:
>
> I'm a little shocked about the wrong information people spreading there as 
>> well as the amount of false information. Especially the one that got 4 
>> up-votes. Most of the answers there read like FUD or written by people who 
>> can't or won't read documentation. Also I really don't get why people 
>> always "need" bleeding edge php support. There is no urgent need or do 
>> you migrate you app / server to a new php version just because it's cool? 
>> The only problem that CakePHP has is an image problem.
>
>
> What I would like to discuss in this thread is reasons and solution to 
> them. Why has CakePHP such a negative perception? The thing that bothers me 
> personally the most is why the *uck do people say it has a bad 
> documentation? Seriously, I don't get it. Can't they find the 
> documentation? Can't they use it? Or is it really just FUD by some 
>  fanboys?
>
> The "stone age php version" isn't a very valid argument IMHO. Yes, I 
> agree, CakePHP felt behind other frameworks for at least ~2 years and I've 
> missed the namespace support more than one time. But that was really the 
> only language feature I was really missing. Everything else is sugar on top 
> of the cake. I don't know if other people update their servers and apps for 
> fun and if they do the required testing for free for their clients...but 
> well, looks like some guys out there have more a cowboy-coder attitude than 
> a professional one.
>
> Also I don't get why people complain about the architecture of CakePHP, 
> yes it is different, yes it gives you everything out of the box and isn't a 
> package made of 100 loose libs and then glued together. This is IMHO 
> actually an advantage and makes it easy to get started with it. And 
> seriously, how often do you change the ORM stack of  in 
> reality? And on top of that, CakePHP 3.0, as far as I can tell, is more 
> decoupled than 2.0 was. For example the face pattern in Laravel is, as far 
> as I've worked with it and understood it, just one way you can use for 
> dependency injection. The face seems to works like a proxy. I might be 
> wrong, I haven't spent much time with it yet. SF2 is using a container 
> object to deal with the dependencies. However, my point here is other 
> frameworks *appear* to be more fancy and by this attract people who are 
> looking for fancy things, "interesting" design patterns and architecture. 
> Which brings us back to the cowboy-coder attitude. Something doesn't has to 
> be fancy to just work.
>
> I know that for example Symfony gets a lot attention and exposure through 
> having virtually one domain per component of their framework and a nice 
> design for these sites and for whatever reason Symfony manages it somehow 
> to get massive funding. Creating all these pages and a fancy design takes 
> time 

Re: CakePHP 3.0.0-beta2 released

2014-09-29 Thread Reuben
Super excited for separate packages, and using components inside other 
applications.

On Sunday, 28 September 2014 23:49:02 UTC+10, José Lorenzo wrote:
>
> The CakePHP core team is proud to announce the second beta release for 
> CakePHP 
> 3.0.0 .
> It's been a month since our first beta release, and we are excited by the 
> big welcome the community has given to the new version. All the positive 
> feedback and help has been a great motivation for the core team to work 
> harder on improving the developer experience for 3.0.
>
> This will be the last beta release for 3.0, this means that the API is 
> already stabilizing and we're mostly focusing on polishing the current 
> features, performance optimizations, documentation and quickly solving any 
> issues reported in Github.
>
> We've had a very busy month implementing a few missing features we had in 
> our roadmap and upgrading some of the popular plugins for CakePHP.
>
> Below the list of new features and changes that made it into 3.0.0-beta2:
> DebugKit 
>
> Debugging CakePHP 3.0 applications is even better. The new DebugKit is 
> easier to install, faster and looks gorgeous.
>
> DebugKit is a application toolbar that collects useful statistics about 
> your code such as time and memory, executed queries, log messages and view 
> variables. To install Debugkit just use
>
> composer require cakephp/debug_kit "3.0.*-dev"
>
> And add this line to your bootstrap.php file:
>
> Plugin::load('DebugKit', ['bootstrap' => true]);
>
> If you install a new application using the app skeleton 
> , DebugKit will be automatically 
> installed for you.
> Database Migrations 
>
> Migrations  is now an official 
> CakePHP plugin. It wraps the excellent Phinx  library 
> into a CakePHP shell to avoid repeating configuration strings and add some 
> of the cake experience. A database migration generated by this plugin would 
> look like:
>
>  AbstractMigration {
> /** * Change. */
> public function change() {
> // create the table
> $table = $this->table('users');
> $table->addColumn('id', 'integer')
> ->addColumn('username', 'string')
> ->addColumn('password', 'string')
> ->addColumn('created', 'datetime')
> ->create();
> }
>
> Migrations are reversible. This means that with the same code you can 
> create or rollback the changes done to the database schema.
>
> To install the Migrations plugins run:
>
> composer require cakephp/migrations "dev-master"
>
> And add this line to your bootstrap.php file:
>
> Plugin::load('Migrations');
>
> New Logger interface 
>
> CakePHP has adopted the PSR-3 recommendation for loggers. Now all log 
> engines implement the Prs\Log\LoggerInterface interface. This means that 
> the entire logging system can easily be replaced by other implementations, 
> such as the popular Monolog library .
> Integration Tests and Data Integrity 
>
> Testing controllers has always been problematic. While ControllerTestCase 
> solved some of the problems, we identified this class as a source of 
> problems and confusion among our users. We decided to implement the new 
> IntegrationTestCase class as a way totest all aspects of an HTTP request 
> in your application without much mocking being involved. This should help 
> you improve code quality and ensure that your application and routes are 
> working as expected.
>
> We also made the fixtures system better, allowing developers to define and 
> work with foreign key constraints in their database. The fixtures system 
> will now correctly load all data and enable constraints right before your 
> test code is executed.
> New Bake templates 
>
> With the date for a stable release getting closer and closer we decided to 
> give a new look to default baked applications. Hopefully the new look will 
> feel fresher, more modern, and easier to work with.
> Separate packages 
>
> We've seen an increasing interest in using the new ORM outside the 
> framework or within older CakePHP applications. One of our goals since the 
> start has been making this possible. We have already begun the work to 
> split the framework into various standalone components that can be reused 
> and installed with composer. While the ORM has not yet been extracted into 
> its own repository, most of the necessary pre-requisites are complete. As a 
> product of this work, we have already extracted several components out of 
> the main code base:
>
>- Collections : Provides a set 
>of tools to manipulate arrays or Traversable objects in an efficient and 
>elegant way.
>- Validation : The excellent 
>and flexible validation library can now be used in any project!
>- 

Re: Warning (512): cake_model cache was unable to write

2014-09-29 Thread ajt
2.5 but I checked many posts on the issue and I dont think that makes any 
difference.
The only solution was to chmod the app/tmp folders and subfolders but i did 
that.

I am using cpanel and have no command prompt to run scripts

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Upload Plugin

2014-09-29 Thread Rafael Queiroz
Hi guys,

I'm using Upload Plugin 2.0 (https://github.com/josegonzalez/cakephp-upload),
it works ridiculous automagic, it's perfect.
I need show upload file in my view, my model is User and field is photo, what
is the best practice in this case?


-- 
Regards,

Rafael F. Queiroz

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


The (bad) perception and image of CakePHP in the public

2014-09-29 Thread Florian Krämer
In the official CakePHP Facebook group Yanuar Nurcahyo asked about opinions 
on that 
link 
http://www.quora.com/Why-isnt-Cakephp-popular-despite-being-one-of-the-earliest-php-framework-to-be-written

I'll quote my own comment I've added to that posting:

I'm a little shocked about the wrong information people spreading there as 
> well as the amount of false information. Especially the one that got 4 
> up-votes. Most of the answers there read like FUD or written by people who 
> can't or won't read documentation. Also I really don't get why people 
> always "need" bleeding edge php support. There is no urgent need or do 
> you migrate you app / server to a new php version just because it's cool? 
> The only problem that CakePHP has is an image problem.


What I would like to discuss in this thread is reasons and solution to 
them. Why has CakePHP such a negative perception? The thing that bothers me 
personally the most is why the *uck do people say it has a bad 
documentation? Seriously, I don't get it. Can't they find the 
documentation? Can't they use it? Or is it really just FUD by some 
 fanboys?

The "stone age php version" isn't a very valid argument IMHO. Yes, I agree, 
CakePHP felt behind other frameworks for at least ~2 years and I've missed 
the namespace support more than one time. But that was really the only 
language feature I was really missing. Everything else is sugar on top of 
the cake. I don't know if other people update their servers and apps for 
fun and if they do the required testing for free for their clients...but 
well, looks like some guys out there have more a cowboy-coder attitude than 
a professional one.

Also I don't get why people complain about the architecture of CakePHP, yes 
it is different, yes it gives you everything out of the box and isn't a 
package made of 100 loose libs and then glued together. This is IMHO 
actually an advantage and makes it easy to get started with it. And 
seriously, how often do you change the ORM stack of  in 
reality? And on top of that, CakePHP 3.0, as far as I can tell, is more 
decoupled than 2.0 was. For example the face pattern in Laravel is, as far 
as I've worked with it and understood it, just one way you can use for 
dependency injection. The face seems to works like a proxy. I might be 
wrong, I haven't spent much time with it yet. SF2 is using a container 
object to deal with the dependencies. However, my point here is other 
frameworks *appear* to be more fancy and by this attract people who are 
looking for fancy things, "interesting" design patterns and architecture. 
Which brings us back to the cowboy-coder attitude. Something doesn't has to 
be fancy to just work.

I know that for example Symfony gets a lot attention and exposure through 
having virtually one domain per component of their framework and a nice 
design for these sites and for whatever reason Symfony manages it somehow 
to get massive funding. Creating all these pages and a fancy design takes 
time and money. So I don't think doing something similar would be an option 
for CakePHP. Honestly I have no ideas what could be done to help making 
CakePHP look better (and stop these silly guys from spreading FUD). I would 
not mind all their critics at all if they would bring valid and detailed 
arguments. But everybody complaining about CakePHP is just repeating other 
peoples FUD about a bad documentation and not exactly mentioning what is 
wrong with the architecture. Going into a discussion is like going into a 
fight without a weapon. But well, the problem here is nobody fights these 
false "arguments". :(

I personally don't mind using Symfony2 or Laravel, they're good frameworks 
as well, but I don't think that CakePHP 3.0 has to hide in any aspect, nor 
had Cake2 when it was new. But CakePHP has a completely different 
philosophy than SF2 and Laravel, obviously one that people are not used to.

So, has anyone constructive critics about that? Maybe others here don't 
even think CakePHP has a problem with it's perception?

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: Creating PDF with cakePHP and TCPDF

2014-09-29 Thread Kyle Rebstock
I would like to ask to clarify my understanding of the topic of these 
postings. "Generated pdf" meaning to convert files into a pdf or just 
making a file view-able and downloadable as a PDF?

On Saturday, September 27, 2014 12:46:05 AM UTC-5, Dakota wrote:
>
> I would highly recommend using the Cake PDF plugin from Friends of Cake. 
> It makes PDF generation very easy. You can get It from 
> https://github.com/friendsofcake/cakepdf

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


i18n base language and database fields

2014-09-29 Thread Radharadhya Dasa
Hi,

I follow cakePHP conventions, so my database tables and fields have english 
names, as it so for cake's default error messages. I am building a webapp 
for a Hungarian client. I would like to use i18n as I think later the 
client will need internationalizing and localizing. But for now they do not 
need it.

So I do not want to create all my view files strings in English and than 
translate to Hungarian, but I want to use translate behaviour to translate 
database field names to Hungarian.

What is the best approach for this scenario?

rrd 

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: 3.0 Database Error : SQLSTATE[HY000] [14] unable to open database file

2014-09-29 Thread Md Bayezid Alam
Sorry, i got the answer, it was an issue of permission..

Thanks

On Mon, Sep 29, 2014 at 9:42 PM, Md Bayezid Alam 
wrote:

> Dear All,
> i am getting the subjected Error for beta-2 of cake3, while first browsing
> from localhost.
>
> sub-hints:
> If you are using SQL keywords as table column names, you can enable
> identifier quoting for your database connection in config/app.php.
>
> *Notice: * If you want to customize this error message, create
> src/Template/Error/pdo_error.ctp
>
> Stack Trace
>
>- CORE/src/Database/Driver/PDODriverTrait.php line 44
> → PDO->__construct(string, null, null,
>array) 
>- CORE/src/Database/Driver/Sqlite.php line 62
> →
>Cake\Database\Driver\Sqlite->_connect(array)
>
>- CORE/src/Database/Schema/BaseSchema.php line 44
> → Cake\Database\Driver\Sqlite->connect()
>
>- CORE/src/Database/Dialect/SqliteDialectTrait.php line 163
> →
>Cake\Database\Schema\BaseSchema->__construct(Cake\Database\Driver\Sqlite)
>
>- CORE/src/Database/Schema/Collection.php line 59
> →
>Cake\Database\Driver\Sqlite->schemaDialect()
>
>- CORE/src/Database/Connection.php line 288
> →
>Cake\Database\Schema\Collection->__construct(Cake\Database\Connection)
>
>- ROOT/plugins/DebugKit/src/Model/Table/LazyTableTrait.php line 38
> →
>Cake\Database\Connection->schemaCollection()
>
>- ROOT/plugins/DebugKit/src/Model/Table/RequestsTable.php line 41
> →
>DebugKit\Model\Table\RequestsTable->ensureTables(array)
>
>- CORE/src/ORM/Table.php line 231  →
>DebugKit\Model\Table\RequestsTable->initialize(array)
>
>- CORE/src/ORM/TableRegistry.php line 186 
>→ Cake\ORM\Table->__construct(array) 
>- ROOT/plugins/DebugKit/src/Routing/Filter/DebugBarFilter.php line 178
> → Cake\ORM\TableRegistry::get(string)
>
>- CORE/src/Event/EventManager.php line 268 
>→ DebugKit\Routing\Filter\DebugBarFilter->afterDispatch(Cake\Event\Event,
>Cake\Network\Request, Cake\Network\Response)
>
>- CORE/src/Event/EventManager.php line 235 
>→ Cake\Event\EventManager->_callListener(array, Cake\Event\Event)
>
>- CORE/src/Event/EventManagerTrait.php line 76
> →
>Cake\Event\EventManager->dispatch(Cake\Event\Event)
>
>- CORE/src/Routing/Dispatcher.php line 90 
>→ Cake\Routing\Dispatcher->dispatchEvent(string, array)
>
>- ROOT/webroot/index.php line 37  → 
> Cake\Routing\Dispatcher->dispatch(Cake\Network\Request,
>Cake\Network\Response) 
>
>
> Note: i have manually downloaded from
> https://github.com/cakephp/cakephp/releases/3.0.0-beta2
>
> Hope it's proper suggestion
>
> Thanks
> Bayezid
>

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


3.0 Database Error : SQLSTATE[HY000] [14] unable to open database file

2014-09-29 Thread Md Bayezid Alam
Dear All,
i am getting the subjected Error for beta-2 of cake3, while first browsing
from localhost.

sub-hints:
If you are using SQL keywords as table column names, you can enable
identifier quoting for your database connection in config/app.php.

*Notice: * If you want to customize this error message, create
src/Template/Error/pdo_error.ctp

Stack Trace

   - CORE/src/Database/Driver/PDODriverTrait.php line 44
    → PDO->__construct(string, null, null,
   array) 
   - CORE/src/Database/Driver/Sqlite.php line 62
    →
   Cake\Database\Driver\Sqlite->_connect(array) 
   - CORE/src/Database/Schema/BaseSchema.php line 44
    → Cake\Database\Driver\Sqlite->connect()
   
   - CORE/src/Database/Dialect/SqliteDialectTrait.php line 163
    →
   Cake\Database\Schema\BaseSchema->__construct(Cake\Database\Driver\Sqlite)
   
   - CORE/src/Database/Schema/Collection.php line 59
    →
   Cake\Database\Driver\Sqlite->schemaDialect() 
   - CORE/src/Database/Connection.php line 288 
   → Cake\Database\Schema\Collection->__construct(Cake\Database\Connection)
   
   - ROOT/plugins/DebugKit/src/Model/Table/LazyTableTrait.php line 38
    →
   Cake\Database\Connection->schemaCollection() 
   - ROOT/plugins/DebugKit/src/Model/Table/RequestsTable.php line 41
    →
   DebugKit\Model\Table\RequestsTable->ensureTables(array)
   
   - CORE/src/ORM/Table.php line 231  →
   DebugKit\Model\Table\RequestsTable->initialize(array)
   
   - CORE/src/ORM/TableRegistry.php line 186  →
   Cake\ORM\Table->__construct(array) 
   - ROOT/plugins/DebugKit/src/Routing/Filter/DebugBarFilter.php line 178
    → Cake\ORM\TableRegistry::get(string)
   
   - CORE/src/Event/EventManager.php line 268 
   → DebugKit\Routing\Filter\DebugBarFilter->afterDispatch(Cake\Event\Event,
   Cake\Network\Request, Cake\Network\Response) 
   - CORE/src/Event/EventManager.php line 235 
   → Cake\Event\EventManager->_callListener(array, Cake\Event\Event)
   
   - CORE/src/Event/EventManagerTrait.php line 76
    →
   Cake\Event\EventManager->dispatch(Cake\Event\Event)
   
   - CORE/src/Routing/Dispatcher.php line 90
 →
Cake\Routing\Dispatcher->dispatchEvent(string,
   array) 
   - ROOT/webroot/index.php line 37  →
Cake\Routing\Dispatcher->dispatch(Cake\Network\Request,
   Cake\Network\Response) 


Note: i have manually downloaded from
https://github.com/cakephp/cakephp/releases/3.0.0-beta2

Hope it's proper suggestion

Thanks
Bayezid

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: CDN for CakePHP

2014-09-29 Thread Kan Samy
Thanks for your reply Cherankrish.
I am using Cloudfront CDN and I have created the distribution and generated 
the cdn url. Now I dont know where(which file) to map the cdn url in my 
CakePHP project?

On Monday, September 29, 2014 4:05:57 PM UTC+5:30, cheran krishnamoorthy 
wrote:
>
> Try Cloudflare.
>
> On Mon, Sep 29, 2014 at 12:53 PM, Kan Samy  > wrote:
>
>>  I would like to activate the content delivery network for my CakePHP 
>> project. Can someone help me to activate CDN for my CakePHP site?
>>
>> -- 
>> Like Us on FaceBook https://www.facebook.com/CakePHP
>> Find us on Twitter http://twitter.com/CakePHP
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "CakePHP" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to cake-php+u...@googlegroups.com .
>> To post to this group, send email to cake...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/cake-php.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> *Cherankrish*
> chera...@gmail.com 
> Skype: cherankrish
>
> QR code :
>
>  

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


Re: CDN for CakePHP

2014-09-29 Thread cheran krishnamoorthy
Try Cloudflare.

On Mon, Sep 29, 2014 at 12:53 PM, Kan Samy  wrote:

>  I would like to activate the content delivery network for my CakePHP
> project. Can someone help me to activate CDN for my CakePHP site?
>
> --
> Like Us on FaceBook https://www.facebook.com/CakePHP
> Find us on Twitter http://twitter.com/CakePHP
>
> ---
> You received this message because you are subscribed to the Google Groups
> "CakePHP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cake-php+unsubscr...@googlegroups.com.
> To post to this group, send email to cake-php@googlegroups.com.
> Visit this group at http://groups.google.com/group/cake-php.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Cherankrish*
cherankr...@gmail.com
Skype: cherankrish

QR code :

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.


CDN for CakePHP

2014-09-29 Thread Kan Samy
 I would like to activate the content delivery network for my CakePHP 
project. Can someone help me to activate CDN for my CakePHP site?

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.