Re: cakePHP 3.0.0-RC2 documentation, Testing
OK, I have moved ahead on the /vendor side thanks to some suggestions from Mark Story. create /web/cake3-rc2-v3 directory git clone git://github.com/cakephp/bake.git cd bake copy composer.phar to /web/cake3-rc2-v3/bake directory php composer.phar install Now, the following works. E:\web\cake3-rc2-v3\bake> vendor\bin\phpunit tests/TestCase/Shell/Task/BakeTemplateTaskTest.php PHPUnit 4.5.0 by Sebastian Bergmann and contributors. Configuration read from E:\web\cake3-rc2-v3\bake\phpunit.xml.dist ... Time: 932 ms, Memory: 4.75Mb OK (3 tests, 3 assertions) Note for Windows users. The back slash, \ , must be used to execute phpunit. I am still stuck on getting the "simple" example in the Testing chapter of the documentation to run. Any clues anyone ??? On Monday, February 16, 2015 at 6:30:46 PM UTC-5, Lorne Dudley wrote: > > Hello Andrew > > True, my long term goal is to submit my changes to github.But first, I > have to learn how to set up a test.So I am trying to follow the > "simple" example in the "Testing" chapter at this point. I am new to the > world of object-oriented programming, coming from a procedure oriented > background. > > So my immediate goal is to get the example in the document running. Once > I understand things at that level I will attempt to write the test case for > my proposed change. > > Regards > > Lorne > > On Monday, February 16, 2015 at 5:04:33 PM UTC-5, Andrew Lechowicz wrote: >> >> So your not trying to build an app on top of CakePHP but rather I think >> my rule still stands here. In fact I believe that's the problem. Instead of >> cloning the project you created a new one which is meant to *use *the >> CakePHP core files and I believe tests will be set up accordingly. I think >> your best bet is to fork https://github.com/cakephp/bake and apply your >> tests and changes there. The bonus with this method is it's easy to create >> PR's back to the core. >> >> On Monday, February 16, 2015 at 3:51:51 PM UTC-5, Lorne Dudley wrote: >>> >>> Hello Andrew ! (and anyone else who wishes to contribute) >>> >>> Reference your comment on "You should never add/edit/remove any file >>> maintained by a package manager", >>> I think that my case is an exception. With the assistance of another >>> developer I have developed a fix >>> for a "cake bake" issue. My challenge is to develop a test case for the >>> change. >>> >>> See https://github.com/cakephp/bake/issues/35 . >>> >>> I have a change to >>> /vendor/cakephp/bake/src/Template/Bake/Element/form.ctp which solves the >>> problem. >>> >>> >>> Following your suggestions I tried a few variations. >>> >>> First, I used the imbedded phpunit in cakephp on my existing structure >>> on the /vendor side. >>> Then on the corresponding structure under /tests. >>> In both cases the results are the same. >>> >>> I then tried the C:/bin/phpunit. Same results. (Conclusion, it does >>> not matter which phpunit I use.) >>> >>> I noticed vendor/cakephp/bake/tests/TestCase/View/BakeViewTest.php which >>> is part of the composer delivered >>> cakephp system. I tried phpunit on that file and everything seems to >>> work correctly. >>> >>> Conclusion: There must be some setup detail missing in the documented >>> example in the Testing section ? >>> >>> Do you have any ideas following this additional information ? I am >>> wondering if I need to understand what is >>> going on with E:\web\cake3-rc2\phpunit.xml.dist . (See previous reply >>> for content.) >>> >>> Regards >>> >>> Lorne >>> >>> My results are shown below. >>> >>> -- >>> E:\web\cake3-rc2>php vendor/phpunit/phpunit/phpunit --version >>> PHPUnit 4.5.0 by Sebastian Bergmann and contributors. >>> -- >>> E:\web\cake3-rc2>php vendor/phpunit/phpunit/phpunit >>> vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php >>> PHPUnit 4.5.0 by Sebastian Bergmann and contributors. >>> >>> Configuration read from E:\web\cake3-rc2\phpunit.xml.dist >>> >>> Fatal error: Class 'App\View\Helper\ProgressHelper' not found in >>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php >>> >>> on line 15 >>> >>> Call Stack: >>&g
Re: cakePHP 3.0.0-RC2 documentation, Testing
gt; Then
>>>> E:\web\cake3-rc2>phpunit
>>>> vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
>>>> PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
>>>>
>>>> Configuration read from E:\web\cake3-rc2\phpunit.xml.dist
>>>>
>>>>
>>>> Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
>>>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>>>>
>>>> on line 15
>>>>
>>>> Call Stack:
>>>> 0.0300 441920 1. {main}() C:\bin\phpunit.phar:0
>>>> 0.0300 669080 2. PHPUnit_TextUI_Command::main()
>>>> C:\bin\phpunit.phar:722
>>>> 0.0300 673024 3. PHPUnit_TextUI_Command->run()
>>>> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
>>>> 0.21203838104 4. PHPUnit_TextUI_TestRunner->doRun()
>>>> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
>>>> 0.23204158704 5. PHPUnit_Framework_TestSuite->run()
>>>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
>>>> 0.24204169832 6. PHPUnit_Framework_TestCase->run()
>>>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
>>>> 0.24204170576 7. PHPUnit_Framework_TestResult->run()
>>>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
>>>> 0.25204226312 8. PHPUnit_Framework_TestCase->runBare()
>>>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
>>>> 0.26204316576 9.
>>>> App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
>>>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
>>>>
>>>> Here are my file contents and their locations.
>>>>
>>>> E:\web\cake3-rc2\phpunit.xml.dist
>>>> =
>>>>
>>>> >>> colors="true"
>>>> processIsolation="false"
>>>> stopOnFailure="false"
>>>> syntaxCheck="false"
>>>> bootstrap="./tests/bootstrap.php"
>>>> >
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ./tests/TestCase
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> >>> class="\Cake\TestSuite\Fixture\FixtureInjector"
>>>>
>>>> file="./vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php">
>>>>
>>>> >>> />
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> E:\web\cake3-rc2\vendor\cakephp\bake\src\View\Helper\ProgressHelper.php
>>>> ===
>>>> >>> namespace App\View\Helper;
>>>>
>>>> class ProgressHelper extends AppHelper
>>>> {
>>>> public function bar($value)
>>>> {
>>>> $width = round($value / 100, 2) * 100;
>>>> return sprintf(
>>>> '
>>>>
>>>> ', $width);
>>>> }
>>>> }
>>>>
>>>>
>>>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>>>>
>>>> ==
>>>> >>> namespace App\Test\TestCase\View\Helper;
>>>>
>>>> use App\View\Helper\ProgressHelper;
>>>> use Cake\TestSuite\TestCase;
>>>> use Cake\View\View;
>>>>
>>>> class ProgressHelperTest extends TestCase
>>>> {
>>>>
>>>> public function setUp()
>>>> {
>>>> parent::setUp();
>>>> $View = new View();
>>>> $this->Progress = new ProgressHelper($View);
>>>> }
>>>>
>>>> public function testBar()
>>>> {
>>>> $result = $this-&g
Re: cakePHP 3.0.0-RC2 documentation, Testing
-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
>>>
>>> Here are my file contents and their locations.
>>>
>>> E:\web\cake3-rc2\phpunit.xml.dist
>>> =
>>>
>>> >> colors="true"
>>> processIsolation="false"
>>> stopOnFailure="false"
>>> syntaxCheck="false"
>>> bootstrap="./tests/bootstrap.php"
>>> >
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ./tests/TestCase
>>>
>>>
>>>
>>>
>>>
>>>
>>> >> class="\Cake\TestSuite\Fixture\FixtureInjector"
>>>
>>> file="./vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php">
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> E:\web\cake3-rc2\vendor\cakephp\bake\src\View\Helper\ProgressHelper.php
>>> ===
>>> >> namespace App\View\Helper;
>>>
>>> class ProgressHelper extends AppHelper
>>> {
>>> public function bar($value)
>>> {
>>> $width = round($value / 100, 2) * 100;
>>> return sprintf(
>>> '
>>>
>>> ', $width);
>>> }
>>> }
>>>
>>>
>>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>>>
>>> ==
>>> >> namespace App\Test\TestCase\View\Helper;
>>>
>>> use App\View\Helper\ProgressHelper;
>>> use Cake\TestSuite\TestCase;
>>> use Cake\View\View;
>>>
>>> class ProgressHelperTest extends TestCase
>>> {
>>>
>>> public function setUp()
>>> {
>>> parent::setUp();
>>> $View = new View();
>>> $this->Progress = new ProgressHelper($View);
>>> }
>>>
>>> public function testBar()
>>> {
>>> $result = $this->Progress->bar(90);
>>> $this->assertContains('width: 90%', $result);
>>> $this->assertContains('progress-bar', $result);
>>>
>>> $result = $this->Progress->bar(33.333);
>>> $this->assertContains('width: 33%', $result);
>>> }
>>>
>>> }
>>>
>>>
>>> ==
>>>
>>> I am not at all confident that I have things placed in the correct
>>> directories.
>>> The documentation (PDF version, starting at page 559) does not clearly
>>> indicate where these items should be placed.
>>> I am guessing that the reference to the directory tests is on the vendor
>>> side.
>>>
>>> My long term goal is to learn enough about "Testing" so that I can
>>> develop a test for a change
>>> made to /vendor/cakephp/bake/src/Template/Bake/Element/form.ctp
>>>
>>> Any help or assistance for this new member of the cakephp community
>>> would be greatly appreciated.
>>>
>>> On Saturday, February 14, 2015 at 4:23:42 PM UTC-5, Andrew Lechowicz
>>> wrote:
>>>>
>>>> When something isn't loading the correct file, it smells like a
>>>> composer autoload issue or a namespace issue. Try running `composer
>>>> dump-autoload`. If that doesn't work try looking at your `use` blocks to
>>>> see if you might be missing something.
>>>>
>>>> On Friday, February 13, 2015 at 12:00:11 AM UTC-5, Lorne Dudley wrote:
>>>>>
>>>>> OK, I have made a little progress in trying to figure out what is
>>>>> wrong. My conclusion is that there are some steps missing in the
>>>>> documentation.
>>>>> I hope that perhaps one of the core developers might comment as to
>>>>> what might be wrong.
>>>>>
>>>>> I was able to make the "Fatal error: Class
>>>>> &#x
Re: cakePHP 3.0.0-RC2 documentation, Testing
web\cake3-rc2\vendor\cakephp\cakephp\src\TestSuite\TestCase.php:166
E:\web\cake3-rc2\vendor\cakephp\cakephp\src\TestSuite\StringCompareTrait.php:47
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\BakeViewTest.php:134
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
FAILURES!
Tests: 5, Assertions: 5, Failures: 5.
On Sunday, February 15, 2015 at 9:44:24 PM UTC-5, Andrew Lechowicz wrote:
>
> I was going to say:
>
> I'm curious, what happens if you run it with the composer installed
>> phpunit? Your command will be something like
>> `vendor/bin/phpunit tests/TestCase/View/Helper/`.
>
>
> But then I noticed your path: `E:\web\cake3-rc2\vendor\`. You should
> never add/edit/remove any file maintained by a package manager (composer in
> this case). Move these into the respective folders in src and you should be
> good to go.
>
> On Sunday, February 15, 2015 at 8:29:09 PM UTC-5, Lorne Dudley wrote:
>>
>> Hello Andrew !
>>
>> OK, I tried this.
>> E:\web\cake3-rc2>php composer.phar dump-autoload
>> Generating autoload files
>>
>> Then
>> E:\web\cake3-rc2>phpunit
>> vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
>> PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
>>
>> Configuration read from E:\web\cake3-rc2\phpunit.xml.dist
>>
>>
>> Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>>
>> on line 15
>>
>> Call Stack:
>> 0.0300 441920 1. {main}() C:\bin\phpunit.phar:0
>> 0.0300 669080 2. PHPUnit_TextUI_Command::main()
>> C:\bin\phpunit.phar:722
>> 0.0300 673024 3. PHPUnit_TextUI_Command->run()
>> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
>> 0.21203838104 4. PHPUnit_TextUI_TestRunner->doRun()
>> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
>> 0.23204158704 5. PHPUnit_Framework_TestSuite->run()
>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
>> 0.24204169832 6. PHPUnit_Framework_TestCase->run()
>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
>> 0.24204170576 7. PHPUnit_Framework_TestResult->run()
>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
>> 0.25204226312 8. PHPUnit_Framework_TestCase->runBare()
>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
>> 0.26204316576 9.
>> App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
>> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
>>
>> Here are my file contents and their locations.
>>
>> E:\web\cake3-rc2\phpunit.xml.dist
>> =
>>
>> > colors="true"
>> processIsolation="false"
>> stopOnFailure="false"
>> syntaxCheck="false"
>> bootstrap="./tests/bootstrap.php"
>> >
>>
>>
>>
>>
>>
>>
>>
>>
>> ./tests/TestCase
>>
>>
>>
>>
>>
>>
>> > class="\Cake\TestSuite\Fixture\FixtureInjector"
>>
>> file="./vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php">
>>
>>
>>
>>
>>
>>
>>
>>
>> E:\web\cake3-rc2\vendor\cakephp\bake\src\View\Helper\ProgressHelper.php
>> ===
>> > namespace App\View\Helper;
>>
>> class ProgressHelper extends AppHelper
>> {
>> public function bar($value)
>> {
>> $width = round($value / 100, 2) * 100;
>> return sprintf(
>> '
>>
>> ', $width);
>> }
>> }
>>
>>
>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>>
>> ==
>> > namespace App\Test\TestCase\View\Helper;
>>
>> use App\View\Helper\ProgressHelper;
>> use Cake\TestSuite\TestCase;
>> use Cake\View\View;
>>
>> class ProgressHelperTest extends TestCase
>
Re: cakePHP 3.0.0-RC2 documentation, Testing
I was going to say:
I'm curious, what happens if you run it with the composer installed
> phpunit? Your command will be something like
> `vendor/bin/phpunit tests/TestCase/View/Helper/`.
But then I noticed your path: `E:\web\cake3-rc2\vendor\`. You should never
add/edit/remove any file maintained by a package manager (composer in this
case). Move these into the respective folders in src and you should be good
to go.
On Sunday, February 15, 2015 at 8:29:09 PM UTC-5, Lorne Dudley wrote:
>
> Hello Andrew !
>
> OK, I tried this.
> E:\web\cake3-rc2>php composer.phar dump-autoload
> Generating autoload files
>
> Then
> E:\web\cake3-rc2>phpunit
> vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
> PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
>
> Configuration read from E:\web\cake3-rc2\phpunit.xml.dist
>
>
> Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>
> on line 15
>
> Call Stack:
> 0.0300 441920 1. {main}() C:\bin\phpunit.phar:0
> 0.0300 669080 2. PHPUnit_TextUI_Command::main()
> C:\bin\phpunit.phar:722
> 0.0300 673024 3. PHPUnit_TextUI_Command->run()
> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
> 0.21203838104 4. PHPUnit_TextUI_TestRunner->doRun()
> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
> 0.23204158704 5. PHPUnit_Framework_TestSuite->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
> 0.24204169832 6. PHPUnit_Framework_TestCase->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
> 0.24204170576 7. PHPUnit_Framework_TestResult->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
> 0.25204226312 8. PHPUnit_Framework_TestCase->runBare()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
> 0.26204316576 9.
> App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
>
> Here are my file contents and their locations.
>
> E:\web\cake3-rc2\phpunit.xml.dist
> =
>
> colors="true"
> processIsolation="false"
> stopOnFailure="false"
> syntaxCheck="false"
> bootstrap="./tests/bootstrap.php"
> >
>
>
>
>
>
>
>
>
> ./tests/TestCase
>
>
>
>
>
>
> class="\Cake\TestSuite\Fixture\FixtureInjector"
>
> file="./vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php">
>
>
>
>
>
>
>
>
> E:\web\cake3-rc2\vendor\cakephp\bake\src\View\Helper\ProgressHelper.php
> ===
> namespace App\View\Helper;
>
> class ProgressHelper extends AppHelper
> {
> public function bar($value)
> {
> $width = round($value / 100, 2) * 100;
> return sprintf(
> '
>
> ', $width);
> }
> }
>
>
> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>
> ==
> namespace App\Test\TestCase\View\Helper;
>
> use App\View\Helper\ProgressHelper;
> use Cake\TestSuite\TestCase;
> use Cake\View\View;
>
> class ProgressHelperTest extends TestCase
> {
>
> public function setUp()
> {
> parent::setUp();
> $View = new View();
> $this->Progress = new ProgressHelper($View);
> }
>
> public function testBar()
> {
> $result = $this->Progress->bar(90);
> $this->assertContains('width: 90%', $result);
> $this->assertContains('progress-bar', $result);
>
> $result = $this->Progress->bar(33.333);
> $this->assertContains('width: 33%', $result);
> }
>
> }
>
>
> ==
>
> I am not at all confident that I have things placed in the correct
> directories.
> The documentation (PDF version, starting at page 559) does not clearly
> indicate where these items should be placed.
> I am guessing that the ref
Re: cakePHP 3.0.0-RC2 documentation, Testing
Hello Andrew !
OK, I tried this.
E:\web\cake3-rc2>php composer.phar dump-autoload
Generating autoload files
Then
E:\web\cake3-rc2>phpunit
vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
Configuration read from E:\web\cake3-rc2\phpunit.xml.dist
Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
on line 15
Call Stack:
0.0300 441920 1. {main}() C:\bin\phpunit.phar:0
0.0300 669080 2. PHPUnit_TextUI_Command::main()
C:\bin\phpunit.phar:722
0.0300 673024 3. PHPUnit_TextUI_Command->run()
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
0.21203838104 4. PHPUnit_TextUI_TestRunner->doRun()
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
0.23204158704 5. PHPUnit_Framework_TestSuite->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
0.24204169832 6. PHPUnit_Framework_TestCase->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
0.24204170576 7. PHPUnit_Framework_TestResult->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
0.25204226312 8. PHPUnit_Framework_TestCase->runBare()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
0.26204316576 9.
App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
Here are my file contents and their locations.
E:\web\cake3-rc2\phpunit.xml.dist
=
./tests/TestCase
E:\web\cake3-rc2\vendor\cakephp\bake\src\View\Helper\ProgressHelper.php
===
', $width);
}
}
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
==
Progress = new ProgressHelper($View);
}
public function testBar()
{
$result = $this->Progress->bar(90);
$this->assertContains('width: 90%', $result);
$this->assertContains('progress-bar', $result);
$result = $this->Progress->bar(33.333);
$this->assertContains('width: 33%', $result);
}
}
==
I am not at all confident that I have things placed in the correct
directories.
The documentation (PDF version, starting at page 559) does not clearly
indicate where these items should be placed.
I am guessing that the reference to the directory tests is on the vendor
side.
My long term goal is to learn enough about "Testing" so that I can develop
a test for a change
made to /vendor/cakephp/bake/src/Template/Bake/Element/form.ctp
Any help or assistance for this new member of the cakephp community would
be greatly appreciated.
On Saturday, February 14, 2015 at 4:23:42 PM UTC-5, Andrew Lechowicz wrote:
>
> When something isn't loading the correct file, it smells like a composer
> autoload issue or a namespace issue. Try running `composer dump-autoload`.
> If that doesn't work try looking at your `use` blocks to see if you might
> be missing something.
>
> On Friday, February 13, 2015 at 12:00:11 AM UTC-5, Lorne Dudley wrote:
>>
>> OK, I have made a little progress in trying to figure out what is
>> wrong. My conclusion is that there are some steps missing in the
>> documentation.
>> I hope that perhaps one of the core developers might comment as to what
>> might be wrong.
>>
>> I was able to make the "Fatal error: Class
>> 'App\View\Helper\ProgressHelper' not found" error to go away by placing
>> ProgressHelper.php in the same directory as ProgressHelperTest.php.
>> However I still get a failure further on -- "Fatal error: Class
>> 'Cake\TestSuite\TestCase' not found".
>>
>> It appears that all searches for dependent components take place in the
>> same directory as ProgressHelperTest.php at the moment.
>>
>> So ... how do I fix this so that searches for dependent components are
>> resolved properly ??? What is missing in the documentation ?
>>
>> Below are my two latest attempts to get this to execute properly.
>>
>> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper>phpunit
>> ProgressHelperTest.php
>>
Re: cakePHP 3.0.0-RC2 documentation, Testing
When something isn't loading the correct file, it smells like a composer
autoload issue or a namespace issue. Try running `composer dump-autoload`.
If that doesn't work try looking at your `use` blocks to see if you might
be missing something.
On Friday, February 13, 2015 at 12:00:11 AM UTC-5, Lorne Dudley wrote:
>
> OK, I have made a little progress in trying to figure out what is
> wrong. My conclusion is that there are some steps missing in the
> documentation.
> I hope that perhaps one of the core developers might comment as to what
> might be wrong.
>
> I was able to make the "Fatal error: Class
> 'App\View\Helper\ProgressHelper' not found" error to go away by placing
> ProgressHelper.php in the same directory as ProgressHelperTest.php.
> However I still get a failure further on -- "Fatal error: Class
> 'Cake\TestSuite\TestCase' not found".
>
> It appears that all searches for dependent components take place in the
> same directory as ProgressHelperTest.php at the moment.
>
> So ... how do I fix this so that searches for dependent components are
> resolved properly ??? What is missing in the documentation ?
>
> Below are my two latest attempts to get this to execute properly.
>
> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper>phpunit
> ProgressHelperTest.php
>
> Fatal error: Class 'Cake\TestSuite\TestCase' not found in
> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>
> on line 9
>
> Call Stack:
> 0.0340 441904 1. {main}() C:\bin\phpunit.phar:0
> 0.0360 669064 2. PHPUnit_TextUI_Command::main()
> C:\bin\phpunit.phar:722
> 0.0360 673008 3. PHPUnit_TextUI_Command->run()
> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
> 0.0430 907096 4. PHPUnit_Runner_BaseTestRunner->getTest()
> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:126
> 0.0430 907120 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass()
> phar://C:/bin/phpunit.phar/phpunit/Runner/BaseTestRunner.php:70
> 0.0440 923936 6. PHPUnit_Runner_StandardTestSuiteLoader->load()
> phar://C:/bin/phpunit.phar/phpunit/Runner/BaseTestRunner.php:125
> 0.0450 948688 7. PHPUnit_Util_Fileloader::checkAndLoad()
> phar://C:/bin/phpunit.phar/phpunit/Runner/StandardTestSuiteLoader.php:43
> 0.0470 948848 8. PHPUnit_Util_Fileloader::load()
> phar://C:/bin/phpunit.phar/phpunit/Util/Fileloader.php:42
> 0.0470 954616 9.
> include_once('E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php')
>
> phar://C:/bin/phpunit.phar/phpunit/Util/Fileloader.php:58
>
>
> E:\web\cake3-rc2\vendor\cakephp\bake>phpunit
> tests/TestCase/View/Helper/ProgressHelperTest.php
> PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
>
> Configuration read from
> E:\web\cake3-rc2\vendor\cakephp\bake\phpunit.xml.dist
>
>
> Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>
> on line 15
>
> Call Stack:
> 0.0280 441920 1. {main}() C:\bin\phpunit.phar:0
> 0.0310 669088 2. PHPUnit_TextUI_Command::main()
> C:\bin\phpunit.phar:722
> 0.0310 673032 3. PHPUnit_TextUI_Command->run()
> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
> 0.10302762848 4. PHPUnit_TextUI_TestRunner->doRun()
> phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
> 0.11803083496 5. PHPUnit_Framework_TestSuite->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
> 0.12503094624 6. PHPUnit_Framework_TestCase->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
> 0.12503095368 7. PHPUnit_Framework_TestResult->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
> 0.13203150720 8. PHPUnit_Framework_TestCase->runBare()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
> 0.13603240640 9.
> App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
>
>
>
--
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: cakePHP 3.0.0-RC2 documentation, Testing
OK, I have made a little progress in trying to figure out what is
wrong. My conclusion is that there are some steps missing in the
documentation.
I hope that perhaps one of the core developers might comment as to what
might be wrong.
I was able to make the "Fatal error: Class 'App\View\Helper\ProgressHelper'
not found" error to go away by placing ProgressHelper.php in the same
directory as ProgressHelperTest.php. However I still get a failure
further on -- "Fatal error: Class 'Cake\TestSuite\TestCase' not found".
It appears that all searches for dependent components take place in the
same directory as ProgressHelperTest.php at the moment.
So ... how do I fix this so that searches for dependent components are
resolved properly ??? What is missing in the documentation ?
Below are my two latest attempts to get this to execute properly.
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper>phpunit
ProgressHelperTest.php
Fatal error: Class 'Cake\TestSuite\TestCase' not found in
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
on line 9
Call Stack:
0.0340 441904 1. {main}() C:\bin\phpunit.phar:0
0.0360 669064 2. PHPUnit_TextUI_Command::main()
C:\bin\phpunit.phar:722
0.0360 673008 3. PHPUnit_TextUI_Command->run()
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
0.0430 907096 4. PHPUnit_Runner_BaseTestRunner->getTest()
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:126
0.0430 907120 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass()
phar://C:/bin/phpunit.phar/phpunit/Runner/BaseTestRunner.php:70
0.0440 923936 6. PHPUnit_Runner_StandardTestSuiteLoader->load()
phar://C:/bin/phpunit.phar/phpunit/Runner/BaseTestRunner.php:125
0.0450 948688 7. PHPUnit_Util_Fileloader::checkAndLoad()
phar://C:/bin/phpunit.phar/phpunit/Runner/StandardTestSuiteLoader.php:43
0.0470 948848 8. PHPUnit_Util_Fileloader::load()
phar://C:/bin/phpunit.phar/phpunit/Util/Fileloader.php:42
0.0470 954616 9.
include_once('E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php')
phar://C:/bin/phpunit.phar/phpunit/Util/Fileloader.php:58
E:\web\cake3-rc2\vendor\cakephp\bake>phpunit
tests/TestCase/View/Helper/ProgressHelperTest.php
PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
Configuration read from
E:\web\cake3-rc2\vendor\cakephp\bake\phpunit.xml.dist
Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
on line 15
Call Stack:
0.0280 441920 1. {main}() C:\bin\phpunit.phar:0
0.0310 669088 2. PHPUnit_TextUI_Command::main()
C:\bin\phpunit.phar:722
0.0310 673032 3. PHPUnit_TextUI_Command->run()
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:104
0.10302762848 4. PHPUnit_TextUI_TestRunner->doRun()
phar://C:/bin/phpunit.phar/phpunit/TextUI/Command.php:152
0.11803083496 5. PHPUnit_Framework_TestSuite->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
0.12503094624 6. PHPUnit_Framework_TestCase->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
0.12503095368 7. PHPUnit_Framework_TestResult->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
0.13203150720 8. PHPUnit_Framework_TestCase->runBare()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
0.13603240640 9.
App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
--
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: cakePHP 3.0.0-RC2 documentation, Testing
This is line 15 in ProgressHelperTest.php, within function setUp()
$this->Progress = new ProgressHelper($View);
On Wednesday, February 11, 2015 at 9:06:29 PM UTC-5, Lorne Dudley wrote:
>
> Testing (page 559 in the pdf version)
>
> I am attempting to follow the instructions in the 3.0.0-RC2 document,
> current as of today.
>
> I believe I have followed all of the instructions.
>
> This is my setup. (cakePHP 3.0.0-RC2, updated as of today)
>
>
> E:/web/cake3-rc2/vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
>
> E:/web/cake3-rc2/vendor/cakephp/bake/src/View/Helper/ProgressHelper.php
>
> E:\web\cake3-rc2\vendor\cakephp\bake> phpunit
> E:/web/cake3-rc2/vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
> PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
>
> Configuration read from
> E:\web\cake3-rc2\vendor\cakephp\bake\phpunit.xml.dist
>
> Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
> E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
>
> on line 15
>
> Call Stack:
> 0. 120448 1. {main}() C:\xampp2\php\phpunit:0
> 0.0156 355992 2. PHPUnit_TextUI_Command::main()
> C:\xampp2\php\phpunit:46
> 0.0156 359392 3. PHPUnit_TextUI_Command->run()
> C:\xampp2\php\pear\PHPUnit\TextUI\Command.php:129
> 0.09362429736 4. PHPUnit_TextUI_TestRunner->doRun()
> C:\xampp2\php\pear\PHPUnit\TextUI\Command.php:176
> 0.10922750216 5. PHPUnit_Framework_TestSuite->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
> 0.10922761344 6. PHPUnit_Framework_TestCase->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
> 0.10922762088 7. PHPUnit_Framework_TestResult->run()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
> 0.12482817952 8. PHPUnit_Framework_TestCase->runBare()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
> 0.12482909168 9.
> App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
> E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
>
> My question:
>
> How do I fix this so that the documented test works ?
>
--
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.
cakePHP 3.0.0-RC2 documentation, Testing
Testing (page 559 in the pdf version)
I am attempting to follow the instrucions in the 3.0.0-RC2 document,
current as of today.
I believe I have followed all of the instructions.
This is my setup. (cakePHP 3.0.0-RC2, updated as of today)
E:/web/cake3-rc2/vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
E:/web/cake3-rc2/vendor/cakephp/bake/src/View/Helper/ProgressHelper.php
E:\web\cake3-rc2\vendor\cakephp\bake> phpunit
E:/web/cake3-rc2/vendor/cakephp/bake/tests/TestCase/View/Helper/ProgressHelperTest.php
PHPUnit 4.5.0 by Sebastian Bergmann and contributors.
Configuration read from
E:\web\cake3-rc2\vendor\cakephp\bake\phpunit.xml.dist
Fatal error: Class 'App\View\Helper\ProgressHelper' not found in
E:\web\cake3-rc2\vendor\cakephp\bake\tests\TestCase\View\Helper\ProgressHelperTest.php
on line 15
Call Stack:
0. 120448 1. {main}() C:\xampp2\php\phpunit:0
0.0156 355992 2. PHPUnit_TextUI_Command::main()
C:\xampp2\php\phpunit:46
0.0156 359392 3. PHPUnit_TextUI_Command->run()
C:\xampp2\php\pear\PHPUnit\TextUI\Command.php:129
0.09362429736 4. PHPUnit_TextUI_TestRunner->doRun()
C:\xampp2\php\pear\PHPUnit\TextUI\Command.php:176
0.10922750216 5. PHPUnit_Framework_TestSuite->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:398
0.10922761344 6. PHPUnit_Framework_TestCase->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestSuite.php:716
0.10922762088 7. PHPUnit_Framework_TestResult->run()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:693
0.12482817952 8. PHPUnit_Framework_TestCase->runBare()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestResult.php:609
0.12482909168 9.
App\Test\TestCase\View\Helper\ProgressHelperTest->setUp()
E:\web\cake3-rc2\vendor\phpunit\phpunit\src\Framework\TestCase.php:733
My question:
How do I fix this so that the documented test works ?
--
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.
Make a Restful documentation in CakePHP?
Is there some way to make automatic documentation for restful service? I can see some of the frameworks have integrated a great tool for creating this type of documentation. Do you have experience and recommendations for a CakePHP based resful api? Thanks -- 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: CakePHP ComboSession serious looping bug in documentation
This is resolved and patched in the documentation:
https://github.com/cakephp/docs/commit/23fc03c12c3eea8456e895c2696444e037cdcc56
Thanks!
/Lionel
On Thursday, 12 September 2013 10:23:21 UTC+8, Lionel Chan wrote:
>
> Hi All
>
> *Environment:*
> CakePHP version: *2.4.0 stable*
> latest PHP 5.3
>
> We just recently pushed our app to AWS Beanstalk with ElastiCache + RDS as
> our combo session, and using the ComboSession technique described in
> here<http://book.cakephp.org/2.0/en/development/sessions.html#creating-a-custom-session-handler>.
>
> At first everything was ok, but then out of sudden, our app keep running
> into some infinity loops that we can't really reproduce at that point of
> time. What we can do is basically remove the cookie key from RDS, or clear
> browser cookie. Clearly it has something to do with Session.
>
> So these are our sample error_logs:
>
> [Wed Sep 11 03:56:27 2013] [error] [client 10.251.91.107] PHP Fatal error:
> Maximum execution time of 60 seconds exceeded in
> /var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
> [Wed Sep 11 04:00:49 2013] [error] [client 10.251.91.107] PHP Fatal error:
> Maximum execution time of 60 seconds exceeded in
> /var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
> [Wed Sep 11 04:03:02 2013] [error] [client 10.251.91.107] PHP Fatal error:
> Maximum execution time of 60 seconds exceeded in
> /var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
> repeating
> [Thu Sep 12 01:11:48 2013] [error] [client 10.251.91.107] PHP Fatal error:
> Maximum execution time of 60 seconds exceeded in
> /var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
> [Thu Sep 12 01:13:50 2013] [error] [client 10.251.91.107] PHP Fatal error:
> Maximum execution time of 60 seconds exceeded in
> /var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
> [Thu Sep 12 01:15:15 2013] [error] [client 10.251.91.107] PHP Fatal error:
> Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800
> bytes) in /var/app/current/lib/Cake/Model/Model.php on line 1368
>
> So apparently CakeSession is trying to session_start in a loop that it
> can't resolve the session successfully.
>
> Then we found out one serious issue with the *ComboSession.php* mentioned
> in the post
> http://book.cakephp.org/2.0/en/development/sessions.html#creating-a-custom-session-handler,
>
> that, let's say, if Cache lost the session data, and Cache::delete($id)
> fails, parent::destroy() will simply won't be called to destroy expired
> session.
>
> That says, we run into this kind of loop:
>
> *Let's assume Cache lost the session data, and RDS retained a piece of
> expired session data:*
> 1. CakeSession::start()
> 2. CakeSession::_startSession() - session data get loaded from RDS because
> Cache::read returns false
> 3. CakeSession::_checkValid()
> 4. CakeSession::_validAgentAndTime() - obviously timeout, we got an
> invalid data here
> 5. CakeSession::destroy() - this calls destroy the session and trying to
> call session_destroy()
> 6. ComboSession::destroy($id) - this calls attempted to destroy the
> session data from Cache but failed (Memcache engine says not found!), and
> since it's failed, parent::destroy() will never get triggered, and so *old
> session data is survived*.
> 7. Go to step 1 and continues looping, and PHP will dies either the whole
> memory get filled up or time out.
>
>
> To reproduce, we use this modified version of ComboSession to simulate the
> problem: *(The following code is to demonstrate the bug, not a working
> copy!)*
>
> App::uses('DatabaseSession', 'Model/Datasource/Session');
>
> class ComboSession extends DatabaseSession implements
> CakeSessionHandlerInterface {
> public $cacheKey;
>
> public function __construct() {
> $this->cacheKey = Configure::read('Session.handler.cache');
> parent::__construct();
> }
>
> // read data from the session.
> public function read($id) {
> $result = false; //simulate cache read fails
> if ($result) {
> return $result;
> }
> return parent::read($id);
> }
>
> // write data into the session.
> public function write($id, $data) {
> $result = Cache::write($id, $data, $this->cacheKey);
> if ($result) {
> return parent::write($id, $data);
> }
> return false;
> }
>
> // destroy a session.
> public function destroy($id) {
> $result = false; //simulate Cache::delete
CakePHP ComboSession serious looping bug in documentation
Hi All
*Environment:*
CakePHP version: *2.4.0 stable*
latest PHP 5.3
We just recently pushed our app to AWS Beanstalk with ElastiCache + RDS as
our combo session, and using the ComboSession technique described in
here<http://book.cakephp.org/2.0/en/development/sessions.html#creating-a-custom-session-handler>.
At first everything was ok, but then out of sudden, our app keep running
into some infinity loops that we can't really reproduce at that point of
time. What we can do is basically remove the cookie key from RDS, or clear
browser cookie. Clearly it has something to do with Session.
So these are our sample error_logs:
[Wed Sep 11 03:56:27 2013] [error] [client 10.251.91.107] PHP Fatal error:
Maximum execution time of 60 seconds exceeded in
/var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
[Wed Sep 11 04:00:49 2013] [error] [client 10.251.91.107] PHP Fatal error:
Maximum execution time of 60 seconds exceeded in
/var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
[Wed Sep 11 04:03:02 2013] [error] [client 10.251.91.107] PHP Fatal error:
Maximum execution time of 60 seconds exceeded in
/var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
repeating
[Thu Sep 12 01:11:48 2013] [error] [client 10.251.91.107] PHP Fatal error:
Maximum execution time of 60 seconds exceeded in
/var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
[Thu Sep 12 01:13:50 2013] [error] [client 10.251.91.107] PHP Fatal error:
Maximum execution time of 60 seconds exceeded in
/var/app/current/lib/Cake/Model/Datasource/CakeSession.php on line 612
[Thu Sep 12 01:15:15 2013] [error] [client 10.251.91.107] PHP Fatal error:
Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800
bytes) in /var/app/current/lib/Cake/Model/Model.php on line 1368
So apparently CakeSession is trying to session_start in a loop that it
can't resolve the session successfully.
Then we found out one serious issue with the *ComboSession.php* mentioned
in the post
http://book.cakephp.org/2.0/en/development/sessions.html#creating-a-custom-session-handler,
that, let's say, if Cache lost the session data, and Cache::delete($id)
fails, parent::destroy() will simply won't be called to destroy expired
session.
That says, we run into this kind of loop:
*Let's assume Cache lost the session data, and RDS retained a piece of
expired session data:*
1. CakeSession::start()
2. CakeSession::_startSession() - session data get loaded from RDS because
Cache::read returns false
3. CakeSession::_checkValid()
4. CakeSession::_validAgentAndTime() - obviously timeout, we got an invalid
data here
5. CakeSession::destroy() - this calls destroy the session and trying to
call session_destroy()
6. ComboSession::destroy($id) - this calls attempted to destroy the session
data from Cache but failed (Memcache engine says not found!), and since
it's failed, parent::destroy() will never get triggered, and so *old
session data is survived*.
7. Go to step 1 and continues looping, and PHP will dies either the whole
memory get filled up or time out.
To reproduce, we use this modified version of ComboSession to simulate the
problem: *(The following code is to demonstrate the bug, not a working
copy!)*
cacheKey = Configure::read('Session.handler.cache');
parent::__construct();
}
// read data from the session.
public function read($id) {
$result = false; //simulate cache read fails
if ($result) {
return $result;
}
return parent::read($id);
}
// write data into the session.
public function write($id, $data) {
$result = Cache::write($id, $data, $this->cacheKey);
if ($result) {
return parent::write($id, $data);
}
return false;
}
// destroy a session.
public function destroy($id) {
$result = false; //simulate Cache::delete fails
if ($result) {
return parent::destroy($id);
}
return false;
}
// removes expired sessions.
public function gc($expires = null) {
return Cache::gc($this->cacheKey) && parent::gc($expires);
}
}
And in the database, try modify your current session with time (in data),
and expires to a earlier time. You should run into infinity loop in the
next run.
---
In the end, we fix it by issue delete on both Cache and RDS session data
regardless if Cache succeed or not:
public function destroy($id) {
//Delete, regardless of cache succeed or not (so to prevent infinity loop)
Cache::delete($id, $this->cacheKey);
return parent::destroy($id);
}
*Suggestion: To prevent someone from having this issue again, I think it's
best if you can update your documentation at *
http://book.cakephp.org/2.0/en/development/sessions.html#c
Re: What happeened to the API Documentation on CakePHP.org?
Yes, I second jodator. Great Job!! -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
That was a quick fix. Nice job :) On Thursday, February 28, 2013 5:46:01 PM UTC+1, José Lorenzo wrote: > > Issues have been fixed now, you can revisit the site and have an overview > of all the classes. :) > > On Thursday, February 28, 2013 2:56:38 PM UTC+1, Renan Gonçalves wrote: >> >> There are some issues that are preventing us to have the full API >> featured on the website. >> >> Check those: https://github.com/cakephp/cakephp-api-docs/issues >> >> On Thursday, February 28, 2013 10:55:54 AM UTC+1, senser wrote: >>> >>> I cannot agree. The new view of API is terrible for me. >>> I liked to browse classes without typing their names and really loved >>> all classes visible on single page. >>> Another annoying change is the order of class methods - it's not >>> alphabetical anymore, but why ?!? How to find a particular method in class >>> - I have to scroll and read (eventually) all class methods to find what I'm >>> looking for. >>> And finally - I've never been interested of cake "packages", I've always >>> looked for "classes". Now while reading HtmlHelperClass (for example) on >>> the left panel I can select other "similar" helpers, but what if I want to >>> read CakeResponse class. I have to use search box on the top, or must know >>> the package that CakeResponse belongs to, and explore the package. >>> >>> 27 февруари 2013, сряда, 08:55:04 UTC+2, jodator написа: Hi there, they've changed the API yesterday, and i found it quite good. Here is 1.3 debugger: http://api.cakephp.org/1.3/class-Debugger.html I've found it by using the search box (it has a very nice autocomplete). Just remember to choose CakePHP version. On Tuesday, February 26, 2013 7:52:10 PM UTC+1, kdubya wrote: > > Exactly. When I used to go there I could choose to see the ALL the > classes and choose from an alphabetical list. Now it shows a structure > off > to the left but when I try to find something like Debugger it is nowhere > I > can find. > > When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) > to the left there is a structure that makes some sense. Debugger is found > under Utilities. Not so under 1.3. > > Is there still some work going on here that the structure is not > complete? > > Ken > > On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: >> >> I can't find the classes anymore. I was specifically looking for the >> Debugger class in 1.3. The structure that used to be there until >> recently >> is gone. What happened? Did I miss something? >> >> Ken >> > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
Issues have been fixed now, you can revisit the site and have an overview of all the classes. :) On Thursday, February 28, 2013 2:56:38 PM UTC+1, Renan Gonçalves wrote: > > There are some issues that are preventing us to have the full API featured > on the website. > > Check those: https://github.com/cakephp/cakephp-api-docs/issues > > On Thursday, February 28, 2013 10:55:54 AM UTC+1, senser wrote: >> >> I cannot agree. The new view of API is terrible for me. >> I liked to browse classes without typing their names and really loved all >> classes visible on single page. >> Another annoying change is the order of class methods - it's not >> alphabetical anymore, but why ?!? How to find a particular method in class >> - I have to scroll and read (eventually) all class methods to find what I'm >> looking for. >> And finally - I've never been interested of cake "packages", I've always >> looked for "classes". Now while reading HtmlHelperClass (for example) on >> the left panel I can select other "similar" helpers, but what if I want to >> read CakeResponse class. I have to use search box on the top, or must know >> the package that CakeResponse belongs to, and explore the package. >> >> 27 февруари 2013, сряда, 08:55:04 UTC+2, jodator написа: >>> >>> Hi there, >>> >>> they've changed the API yesterday, and i found it quite good. >>> >>> Here is 1.3 debugger: http://api.cakephp.org/1.3/class-Debugger.html >>> >>> I've found it by using the search box (it has a very nice autocomplete). >>> >>> Just remember to choose CakePHP version. >>> >>> >>> On Tuesday, February 26, 2013 7:52:10 PM UTC+1, kdubya wrote: Exactly. When I used to go there I could choose to see the ALL the classes and choose from an alphabetical list. Now it shows a structure off to the left but when I try to find something like Debugger it is nowhere I can find. When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) to the left there is a structure that makes some sense. Debugger is found under Utilities. Not so under 1.3. Is there still some work going on here that the structure is not complete? Ken On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: > > I can't find the classes anymore. I was specifically looking for the > Debugger class in 1.3. The structure that used to be there until recently > is gone. What happened? Did I miss something? > > Ken > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
There are some issues that are preventing us to have the full API featured on the website. Check those: https://github.com/cakephp/cakephp-api-docs/issues On Thursday, February 28, 2013 10:55:54 AM UTC+1, senser wrote: > > I cannot agree. The new view of API is terrible for me. > I liked to browse classes without typing their names and really loved all > classes visible on single page. > Another annoying change is the order of class methods - it's not > alphabetical anymore, but why ?!? How to find a particular method in class > - I have to scroll and read (eventually) all class methods to find what I'm > looking for. > And finally - I've never been interested of cake "packages", I've always > looked for "classes". Now while reading HtmlHelperClass (for example) on > the left panel I can select other "similar" helpers, but what if I want to > read CakeResponse class. I have to use search box on the top, or must know > the package that CakeResponse belongs to, and explore the package. > > 27 февруари 2013, сряда, 08:55:04 UTC+2, jodator написа: >> >> Hi there, >> >> they've changed the API yesterday, and i found it quite good. >> >> Here is 1.3 debugger: http://api.cakephp.org/1.3/class-Debugger.html >> >> I've found it by using the search box (it has a very nice autocomplete). >> >> Just remember to choose CakePHP version. >> >> >> On Tuesday, February 26, 2013 7:52:10 PM UTC+1, kdubya wrote: >>> >>> Exactly. When I used to go there I could choose to see the ALL the >>> classes and choose from an alphabetical list. Now it shows a structure off >>> to the left but when I try to find something like Debugger it is nowhere I >>> can find. >>> >>> When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) to >>> the left there is a structure that makes some sense. Debugger is found >>> under Utilities. Not so under 1.3. >>> >>> Is there still some work going on here that the structure is not >>> complete? >>> >>> Ken >>> >>> On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: I can't find the classes anymore. I was specifically looking for the Debugger class in 1.3. The structure that used to be there until recently is gone. What happened? Did I miss something? Ken >>> -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
I cannot agree. The new view of API is terrible for me. I liked to browse classes without typing their names and really loved all classes visible on single page. Another annoying change is the order of class methods - it's not alphabetical anymore, but why ?!? How to find a particular method in class - I have to scroll and read (eventually) all class methods to find what I'm looking for. And finally - I've never been interested of cake "packages", I've always looked for "classes". Now while reading HtmlHelperClass (for example) on the left panel I can select other "similar" helpers, but what if I want to read CakeResponse class. I have to use search box on the top, or must know the package that CakeResponse belongs to, and explore the package. 27 февруари 2013, сряда, 08:55:04 UTC+2, jodator написа: > > Hi there, > > they've changed the API yesterday, and i found it quite good. > > Here is 1.3 debugger: http://api.cakephp.org/1.3/class-Debugger.html > > I've found it by using the search box (it has a very nice autocomplete). > > Just remember to choose CakePHP version. > > > On Tuesday, February 26, 2013 7:52:10 PM UTC+1, kdubya wrote: >> >> Exactly. When I used to go there I could choose to see the ALL the >> classes and choose from an alphabetical list. Now it shows a structure off >> to the left but when I try to find something like Debugger it is nowhere I >> can find. >> >> When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) to >> the left there is a structure that makes some sense. Debugger is found >> under Utilities. Not so under 1.3. >> >> Is there still some work going on here that the structure is not complete? >> >> Ken >> >> On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: >>> >>> I can't find the classes anymore. I was specifically looking for the >>> Debugger class in 1.3. The structure that used to be there until recently >>> is gone. What happened? Did I miss something? >>> >>> Ken >>> >> -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
Thank you for the link. However, this means I can't browse any more. I have to have a pretty good idea of what I'm looking for. I prefer the old interface. I think there should be a simple way to see all classes or at least find it through the Tree. Debugger, for instance, doesn't show up any where on the tree for 1.3. And why doesn't 1.3 have the same categories (e.g. Utility, etc.) that 2.0 does? Just my 2 cents, Ken On Wednesday, February 27, 2013 1:55:04 AM UTC-5, jodator wrote: > > Hi there, > > they've changed the API yesterday, and i found it quite good. > > Here is 1.3 debugger: http://api.cakephp.org/1.3/class-Debugger.html > > I've found it by using the search box (it has a very nice autocomplete). > > Just remember to choose CakePHP version. > > > On Tuesday, February 26, 2013 7:52:10 PM UTC+1, kdubya wrote: >> >> Exactly. When I used to go there I could choose to see the ALL the >> classes and choose from an alphabetical list. Now it shows a structure off >> to the left but when I try to find something like Debugger it is nowhere I >> can find. >> >> When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) to >> the left there is a structure that makes some sense. Debugger is found >> under Utilities. Not so under 1.3. >> >> Is there still some work going on here that the structure is not complete? >> >> Ken >> >> On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: >>> >>> I can't find the classes anymore. I was specifically looking for the >>> Debugger class in 1.3. The structure that used to be there until recently >>> is gone. What happened? Did I miss something? >>> >>> Ken >>> >> -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
Hi there, they've changed the API yesterday, and i found it quite good. Here is 1.3 debugger: http://api.cakephp.org/1.3/class-Debugger.html I've found it by using the search box (it has a very nice autocomplete). Just remember to choose CakePHP version. On Tuesday, February 26, 2013 7:52:10 PM UTC+1, kdubya wrote: > > Exactly. When I used to go there I could choose to see the ALL the classes > and choose from an alphabetical list. Now it shows a structure off to the > left but when I try to find something like Debugger it is nowhere I can > find. > > When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) to > the left there is a structure that makes some sense. Debugger is found > under Utilities. Not so under 1.3. > > Is there still some work going on here that the structure is not complete? > > Ken > > On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: >> >> I can't find the classes anymore. I was specifically looking for the >> Debugger class in 1.3. The structure that used to be there until recently >> is gone. What happened? Did I miss something? >> >> Ken >> > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
Exactly. When I used to go there I could choose to see the ALL the classes and choose from an alphabetical list. Now it shows a structure off to the left but when I try to find something like Debugger it is nowhere I can find. When I go to the 2.0 version of the API (http://api.cakephp.org/2.0) to the left there is a structure that makes some sense. Debugger is found under Utilities. Not so under 1.3. Is there still some work going on here that the structure is not complete? Ken On Tuesday, February 26, 2013 1:26:43 PM UTC-5, kdubya wrote: > > I can't find the classes anymore. I was specifically looking for the > Debugger class in 1.3. The structure that used to be there until recently > is gone. What happened? Did I miss something? > > Ken > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: What happeened to the API Documentation on CakePHP.org?
You mean this api? http://api.cakephp.org/1.3/ On Tue, Feb 26, 2013 at 12:26 PM, kdubya wrote: > I can't find the classes anymore. I was specifically looking for the > Debugger class in 1.3. The structure that used to be there until recently > is gone. What happened? Did I miss something? > > Ken > > -- > 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?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
What happeened to the API Documentation on CakePHP.org?
I can't find the classes anymore. I was specifically looking for the Debugger class in 1.3. The structure that used to be there until recently is gone. What happened? Did I miss something? Ken -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cake 2.0 documentation Vs Cake 1.3 documentation
On Friday, 28 December 2012 06:34:27 UTC+1, Techinfocomp wrote: > > Hello, > > I Feel that Cake 1.3 documentation is much understandable and easier then > Cake 2.0 documentation, I don't know why CakePHP Did that ? > > Eg: > > AuthComponent in 2.0 > - > > http://book.cakephp.org/2.0/en/core-libraries/components/authentication.html > > And > > AuthComponent in 1.3 > > > http://book.cakephp.org/1.3/en/The-Manual/Core-Components/Authentication.html > > In 1.3 it's clearly mention that how can i convert my normal password > string into MD5 but in 2.0 it's not clear to me because there are many > changes in AuthComponent. > > One more example: > > in 1.3 AuthComponent Variables are clearly described but in 2.0 there is > no description regarding AuthComponent Variables > > Any one here can help me to understand this ? > in 1.3 the auth component was much more complex than it is in 2.0 - I'm not sure which variables in 2.x you're wanting a description of but their doc blocks probably explain their purpose if there is nothing about them in the book. > What i am trying to do is i need to convert my password in to Clean MD5 > only i don't want any extra string need to be added other then my password > only like i don't want salt string etc. > md5 is a very weak algorithm - it's a very poor choice for password hashing. Worse, unsalted md5s can be reversed even with google - e.g. http://www.google.co.uk/search?q=5f4dcc3b5aa765d61d8327deb882cf99 Are you _sure_ you want to do that? It's a very³ bad idea - it's barely (and I really do mean only just) better than storing passwords in plaintext. AD > -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: Cake 2.0 documentation Vs Cake 1.3 documentation
Cakephp is an open source project. If you feel there is stuff that can be fixed or updated you can always look into submitting a pull request for updates. I would also suggest looking at the api docs as well for documentation on the components. You're going to get a lot more information form the api then the book. On Dec 28, 2012 8:00 AM, "Techinfocomp" wrote: > Hello, > > I Feel that Cake 1.3 documentation is much understandable and easier then > Cake 2.0 documentation, I don't know why CakePHP Did that ? > > Eg: > > AuthComponent in 2.0 > - > > http://book.cakephp.org/2.0/en/core-libraries/components/authentication.html > > And > > AuthComponent in 1.3 > > > http://book.cakephp.org/1.3/en/The-Manual/Core-Components/Authentication.html > > In 1.3 it's clearly mention that how can i convert my normal password > string into MD5 but in 2.0 it's not clear to me because there are many > changes in AuthComponent. > > One more example: > > in 1.3 AuthComponent Variables are clearly described but in 2.0 there is > no description regarding AuthComponent Variables > > Any one here can help me to understand this ? > > What i am trying to do is i need to convert my password in to Clean MD5 > only i don't want any extra string need to be added other then my password > only like i don't want salt string etc. > > Thanks > > Harsh Gupta > > -- > 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 post to this group, send email to cake-php@googlegroups.com. > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com. > Visit this group at http://groups.google.com/group/cake-php?hl=en. > > > -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Cake 2.0 documentation Vs Cake 1.3 documentation
Hello, I Feel that Cake 1.3 documentation is much understandable and easier then Cake 2.0 documentation, I don't know why CakePHP Did that ? Eg: AuthComponent in 2.0 - http://book.cakephp.org/2.0/en/core-libraries/components/authentication.html And AuthComponent in 1.3 http://book.cakephp.org/1.3/en/The-Manual/Core-Components/Authentication.html In 1.3 it's clearly mention that how can i convert my normal password string into MD5 but in 2.0 it's not clear to me because there are many changes in AuthComponent. One more example: in 1.3 AuthComponent Variables are clearly described but in 2.0 there is no description regarding AuthComponent Variables Any one here can help me to understand this ? What i am trying to do is i need to convert my password in to Clean MD5 only i don't want any extra string need to be added other then my password only like i don't want salt string etc. Thanks Harsh Gupta -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: In CakePHP 2.x Extending Views not working.. I think the documentation for 2.0 is wrong. How to work Extending Views concept ?
Should be plural "Users":
$this->extend('/Users/add');
Cheers!
On Monday, August 27, 2012 4:29:37 PM UTC+2, Steve Babs wrote:
>
> I have created .
>
>
> Views/Users/add.ctp
> ---
> fetch('title'); ?>
> fetch('content'); ?>
>
>
> Related actions
>
> fetch('sidebar'); ?>
>
>
>
> Views/Users/index.ctp
> ---
> $this->extend('/User/add');
> $this->assign('title', $users['User']['0']['username']);
>
> $this->start('sidebar');
> ?>
> echo $this->Html->link('edit', array(
> 'action' => 'edit',
> $users['User']['0']['id']
> )); ?>
>
> end(); ?>
>
> while I am accessing http://localhost/cakesite/users/add.
>
> I am getting blank space in sidebar content. anyone help me..
>
>
> Thanks,
> Steve Babs
>
>
>
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: In CakePHP 2.x Extending Views not working.. I think the documentation for 2.0 is wrong. How to work Extending Views concept ?
On Monday, 27 August 2012 21:22:49 UTC+2, Mancho Murgan wrote: > > Remove white spaces and new lines before models. > That's not a relevant suggestion. AD -- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: In CakePHP 2.x Extending Views not working.. I think the documentation for 2.0 is wrong. How to work Extending Views concept ?
Remove white spaces and new lines before http://groups.google.com/group/cake-php?hl=en-US.
Re: In CakePHP 2.x Extending Views not working.. I think the documentation for 2.0 is wrong. How to work Extending Views concept ?
Well, when you access /users/add - where or what is supposed to be putting
content in the "sidebar" content block? There's nothing in the add view to
do that; the contents of your index.ctcp file are irrelevant because your
add.ctp file neither references it nor extends it.
AD
On Monday, 27 August 2012 16:29:37 UTC+2, Steve Babs wrote:
>
> I have created .
>
>
> Views/Users/add.ctp
> ---
> fetch('title'); ?>
> fetch('content'); ?>
>
>
> Related actions
>
> fetch('sidebar'); ?>
>
>
>
> Views/Users/index.ctp
> ---
> $this->extend('/User/add');
> $this->assign('title', $users['User']['0']['username']);
>
> $this->start('sidebar');
> ?>
> echo $this->Html->link('edit', array(
> 'action' => 'edit',
> $users['User']['0']['id']
> )); ?>
>
> end(); ?>
>
> while I am accessing http://localhost/cakesite/users/add.
>
> I am getting blank space in sidebar content. anyone help me..
>
>
> Thanks,
> Steve Babs
>
>
>
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
In CakePHP 2.x Extending Views not working.. I think the documentation for 2.0 is wrong. How to work Extending Views concept ?
I have created .
Views/Users/add.ctp
---
fetch('title'); ?>
fetch('content'); ?>
Related actions
fetch('sidebar'); ?>
Views/Users/index.ctp
---
extend('/User/add');
$this->assign('title', $users['User']['0']['username']);
$this->start('sidebar');
?>
Html->link('edit', array(
'action' => 'edit',
$users['User']['0']['id']
)); ?>
end(); ?>
while I am accessing http://localhost/cakesite/users/add.
I am getting blank space in sidebar content. anyone help me..
Thanks,
Steve Babs
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: Documentation on modifying default REST routes
On Fri, Aug 10, 2012 at 9:58 AM, Lightee wrote:
> Thanks for your patient replies. Yes, I did read it even a few times but
> cannot be sure if I understand correctly. The problem is there is no sample
> code to test one's understanding.
>
> Router::connect(
> "/:controller/:id",
> array("action" => "edit", "[method]" => "PUT"),
> array("id" => "[0-9]+")
> );
>
> I am guessing that what it means is that the action "edit" uses HTTP PUT and
> the parameter passed in is the id field. id field is a digit. What if I want
> to pass in 2 or more parameters which are not primary keys? May I know if
> this can be done in CakePHP?
>
What have you tried?
You can get more documentation in the API
http://api.cakephp.org/class/router#method-Routerconnect
Mike.
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: Documentation on modifying default REST routes
Thanks for your patient replies. Yes, I did read it even a few times but
cannot be sure if I understand correctly. The problem is there is no sample
code to test one's understanding.
"edit", "[method]" => "PUT"),
array("id" => "[0-9]+"));
I am guessing that what it means is that the action "edit" uses HTTP PUT
and the parameter passed in is the id field. id field is a digit. What if I
want to pass in 2 or more parameters which are not primary keys? May I know
if this can be done in CakePHP?
Thank you very much.
On Friday, August 10, 2012 4:43:35 PM UTC+8, Mike Griffin wrote:
>
> On Thu, Aug 9, 2012 at 4:38 PM, Lightee >
> wrote:
> > What if the wanted data to be returned is based on data fields other
> than
> > the id? It is restricting to get data based on id only. Is there some
> way to
> > get data based on other fields of the table?
> >
>
> Did you look here:
> http://book.cakephp.org/2.0/en/development/rest.html#custom-rest-routing
>
> Mike.
>
On Friday, August 10, 2012 4:43:35 PM UTC+8, Mike Griffin wrote:
>
> On Thu, Aug 9, 2012 at 4:38 PM, Lightee >
> wrote:
> > What if the wanted data to be returned is based on data fields other
> than
> > the id? It is restricting to get data based on id only. Is there some
> way to
> > get data based on other fields of the table?
> >
>
> Did you look here:
> http://book.cakephp.org/2.0/en/development/rest.html#custom-rest-routing
>
> Mike.
>
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: Documentation on modifying default REST routes
On Thu, Aug 9, 2012 at 4:38 PM, Lightee wrote: > What if the wanted data to be returned is based on data fields other than > the id? It is restricting to get data based on id only. Is there some way to > get data based on other fields of the table? > Did you look here: http://book.cakephp.org/2.0/en/development/rest.html#custom-rest-routing Mike. -- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: Documentation on modifying default REST routes
What if the wanted data to be returned is based on data fields other than the id? It is restricting to get data based on id only. Is there some way to get data based on other fields of the table? The id bit probably means that an id is being sent to the method. A > view method needs an id to return the single thing that is being > viewed whereas the index doesn't need one as it returns a list of all > things. > > The same for each of the other methods. > > Hope this helps. > Mike. > -- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: Documentation on modifying default REST routes
On Thu, Aug 9, 2012 at 1:41 PM, Lightee wrote:
> Dear Cakephp gurus,
>
> Router::resourceMap(array(
> array('action' => 'index', 'method' => 'GET', 'id' => false),
> array('action' => 'view', 'method' => 'GET', 'id' => true),
> array('action' => 'add', 'method' => 'POST', 'id' => false),
> array('action' => 'edit', 'method' => 'PUT', 'id' => true),
> array('action' => 'delete', 'method' => 'DELETE', 'id' => true),
> array('action' => 'update', 'method' => 'POST', 'id' => true)
> ));
>
> What does 'id'=>false or true means? I cannot find sufficient documentation
> in the API documentation.
>
The id bit probably means that an id is being sent to the method. A
view method needs an id to return the single thing that is being
viewed whereas the index doesn't need one as it returns a list of all
things.
The same for each of the other methods.
Hope this helps.
Mike.
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Documentation on modifying default REST routes
Dear Cakephp gurus,
I am trying to build web services using CakePHP. The default REST routes
are not suitable for me as add, edit, update, delete are already taken up
for other purposes.
I need to modify the default rates. From
http://book.cakephp.org/2.0/en/development/rest.html,
'index', 'method' => 'GET', 'id' => false),
array('action' => 'view', 'method' => 'GET', 'id' => true),
array('action' => 'add', 'method' => 'POST', 'id' => false),
array('action' => 'edit', 'method' => 'PUT', 'id' => true),
array('action' => 'delete', 'method' => 'DELETE', 'id' => true),
array('action' => 'update', 'method' => 'POST', 'id' => true)));
What does 'id'=>false or true means? I cannot find sufficient documentation in
the API documentation.
I have tried to search everywhere on sample code for CakePHP web services. But
all I found are 2 links on related documentation
http://book.cakephp.org/2.0/en/development/rest.html
http://book.cakephp.org/2.0/en/views/json-and-xml-views.html
To newbies like me, it is not very helpful although it may be enough for the
experts. Can someone point me to more links?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: v2.x documentation error / typo
yes, it is.
the format behind the hood (model level) should always be unified and
not dependent on the locale settings of the current user/language/
country etc
therefore the format there will always be -MM-DD.
how you display the date in the form is your locale choice and is not
affected by anything outside the view scope.
On 27 Jan., 09:26, stig wrote:
> > On Jan 26, 2:38 pm, stig wrote:
>
> > > In the 2.0 manual. Caused some
> > > headache.http://book.cakephp.org/2.0/en/models/data-validation.html
> > > -> Validation::datetime says to specify datetime format as
> > > array('datetime', 'dmy'), when really it's supposed to be
> > > array('datetime' => 'dmy')
>
> Actually, I was wrong. It's supposed to be array('datetime', 'dmy'). I
> just had some trouble with this, because even though you have
> specified a format like ('DMY') in your FormHelper::input in the View,
> $validation in Model still receives YMD. Is this expected behavior?
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
Re: v2.x documentation error / typo
> On Jan 26, 2:38 pm, stig wrote:
>
> > In the 2.0 manual. Caused some
> > headache.http://book.cakephp.org/2.0/en/models/data-validation.html
> > -> Validation::datetime says to specify datetime format as
> > array('datetime', 'dmy'), when really it's supposed to be
> > array('datetime' => 'dmy')
Actually, I was wrong. It's supposed to be array('datetime', 'dmy'). I
just had some trouble with this, because even though you have
specified a format like ('DMY') in your FormHelper::input in the View,
$validation in Model still receives YMD. Is this expected behavior?
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
Re: v2.x documentation error / typo
On Jan 26, 2:38 pm, stig wrote:
> In the 2.0 manual. Caused some
> headache.http://book.cakephp.org/2.0/en/models/data-validation.html
> -> Validation::datetime says to specify datetime format as
> array('datetime', 'dmy'), when really it's supposed to be
> array('datetime' => 'dmy')
Please correct the root of the problem: https://github.com/cakephp/docs
Thanks,
AD
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
v2.x documentation error / typo
In the 2.0 manual. Caused some headache.
http://book.cakephp.org/2.0/en/models/data-validation.html
-> Validation::datetime says to specify datetime format as
array('datetime', 'dmy'), when really it's supposed to be
array('datetime' => 'dmy')
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
Re: Any best easy to understan documentation or book
Jamie Munro has a good (low cost) book on Cake Php on Amazon Kindle ($4) that I'm enjoying right now, along with Matt Weisfeld's OOP Thought Processes - light reading actually that really helps tie things together :) On Friday, January 13, 2012, jeremyharris wrote: > Also this group, Google, tv.cakephp.org, training.cakephp.org, IRC > > -- > Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php > -- | cellphone: +18579280348 | | 123 10th Street | San Francisco | CA 94103 | | web: www.zign.me | skype: timothy.o.reilly | twitter: @timothyjoreilly | -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Any best easy to understan documentation or book
Also this group, Google, tv.cakephp.org, training.cakephp.org, IRC -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Any best easy to understan documentation or book
Yes. http://book.cakephp.org/ + code + test cases. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Any best easy to understan documentation or book
Hi , Is there any resource to understand cakePHP than documentation. Cheers -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Paginator issue resolved: Incorrect documentation
Yeah I figured what the hey, this is a great opp to give documentation editing a whirl. Only thing is that it's a bit of a serious overhaul, not terrible, but will take some time to rewrite the necessary contents. I'd certainly like to help, though, so will get on this asap. Thanks, -Brian On Dec 13, 3:04 am, phpMagpie wrote: > Details on how to contribute your changes to the documentation can be found > here:http://book.cakephp.org/2.0/en/contributing/documentation.html -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Paginator issue resolved: Incorrect documentation
Details on how to contribute your changes to the documentation can be found here: http://book.cakephp.org/2.0/en/contributing/documentation.html -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Paginator issue resolved: Incorrect documentation
Can you please add the changes to the book yourself? that would be greatly appreciated -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Paginator issue resolved: Incorrect documentation
Hi again,
Here's what I found out. Looking at the main Controller class in lib/
Cake/Controller, the phpdoc for the method paginate() says:
@deprecated Use PaginatorComponent instead
So, I changed my code to read:
$this->Paginator->settings = array(
'recursive' => 0,
'conditions' => array('Article.reporter_id' => 1)
);
$this->set('articles', $this->Paginator->paginate());
And now everything is working fine.
This is not mentioned in the documentation! Here:
http://book.cakephp.org/2.0/en/core-libraries/components/pagination.html
It specifically recommends using the $paginate property and paginate()
method of the controller, but this does not work when setting
conditions and, as aforementioned, is deprecated. Moreover, the cake
baking process will generate controllers using the deprecated code.
Hope that info is helpful. Cheers,
-Brian
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
Am I right to assume that was there all along Mark? If so, sorry :) I am yet to make the switch to Cake 2.0 so not spent much time in the 2.0 book. I only got involved in this thread as seeing various threads discussing the new documentation where the answer has been for them to contribute so assumed (I know - a dangerous thing to do) that there were no guide on how to contribute. Paul. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
Tada! http://book.cakephp.org/2.0/en/contributing/documentation.html -Mark On Dec 8, 4:14 pm, aries wrote: > Got it. What I'm hungering for is an easier way to submit changes and/ > or supplementation. A sticky guide as you suggest would help. > > I hasten to add that I think the documentation is very well written. I > usually find what I'm looking for, even if it takes some time to find > it. > > Best, > -Brian > > On Dec 8, 5:47 am, phpMagpie wrote: > > > > > > > > > The argument is simple, it is wrong to add a comment if it is > > to supplement missing or correct existing documentation. You should edit > > the documentation then the problem is resolved for all others who read it > > thereafter. > > > I think this is a brilliant advancement for the new book, but maybe we > > could do with some form of sticky guide (maybe linked from where the old > > comment link was) which shows people how they can contribute changes via > > GitHub. > > > Paul. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
Got it. What I'm hungering for is an easier way to submit changes and/ or supplementation. A sticky guide as you suggest would help. I hasten to add that I think the documentation is very well written. I usually find what I'm looking for, even if it takes some time to find it. Best, -Brian On Dec 8, 5:47 am, phpMagpie wrote: > The argument is simple, it is wrong to add a comment if it is > to supplement missing or correct existing documentation. You should edit > the documentation then the problem is resolved for all others who read it > thereafter. > > I think this is a brilliant advancement for the new book, but maybe we > could do with some form of sticky guide (maybe linked from where the old > comment link was) which shows people how they can contribute changes via > GitHub. > > Paul. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
The argument is simple, it is wrong to add a comment if it is to supplement missing or correct existing documentation. You should edit the documentation then the problem is resolved for all others who read it thereafter. I think this is a brilliant advancement for the new book, but maybe we could do with some form of sticky guide (maybe linked from where the old comment link was) which shows people how they can contribute changes via GitHub. Paul. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
Oh, and after having it locally, make changes to it and push to your fork in github. The rest is just doing a pull request to us. Please let me know if you need help with anything. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
Got to repository in github, browse the file you need to change, click edit and that's it. If you need to do changes to the layout, I would suggest to download the source, and follow the instructions to get it running. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
AD, Thanks for the link to the source. I get what you're saying about comments vs document edits, and though I might disagree (haven't read through all the arguments), I have no desire to fire up an old debate, especially if the matter is for all intents and purposes closed. What is the best method by which someone can submit documentation additions/ edits? Mark -- Thanks for your reply as well. On-page sub-section TOC would be, IMO, a great help. Best, -Brian On Dec 7, 11:19 am, mark_story wrote: > I've toyed with adding an on-page TOC for the sub-sections not in the > master TOC, but haven't had the time to add it in. It shouldn't be > hard to do on longer pages with lots of subsections. Its probably > mostly a matter of updating the CSS and adding the toctree directives > where necessary. > > -Mark > > On Dec 7, 4:47 am, AD7six wrote: > > > > > > > > > On Dec 6, 11:34 pm, aries wrote: > > > > Hi, > > > > I'm not sure if this is the right place to post my comments, but I'm > > > unable to find a more appropriate venue. Feel free to redirect me. > > > > Unlike previous versions, the 2.0 documentation lacks heading links > > > within the TOC. It used to be that when viewing a particular topic you > > > could access subtopics easily. For example, the 2.0 page on FormHelper > > > is extremely long and finding information on, say, structuring a > > > select options array can be maddening if you don't know where in the > > > page to look. Once found you can bookmark the paragraph's permalink, > > > but that's not very useful for quick reference lookups. > > > > Also, the current topic is not highlighted in the TOC navigation. It > > > would be helpful for the user to know where they are at any given > > > point. A breadcrumb trail might help here. > > > > Lastly, I'm wondering why user comments aren't allowed. I know that a > > > lot of comments can make a page unwieldy, but I thought the pre-1.3 > > > doc pages handled it well, with comments for each section available by > > > click. I often found those comments quite helpful. > > > A comment in place of simply editing the docs is not helpful. There > > aren't any useful comments on the old book that should not be edits > > (and that's if you can find one at all). This point has already been > > discussed ad nausium (here, on the group). > > > > I greatly appreciate the amount of information contained in the book > > > as well as the time and effort it must have taken to put these docs > > > together, but it seems to me that some attention to some basic > > > navigation UI would help tremendously. > > > I'm not clear on exactly what it is you're asking for - but the source > > for the docs are herehttps://github.com/cakephp/docs > > > AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
it would also be nice if one could jump from 1.3 => 2.0 for the same thing often times the google results are still on 1.3 but then I have to "research" in the ajax box what I have been looking for before because there is no direct link On 7 Dez., 18:19, mark_story wrote: > I've toyed with adding an on-page TOC for the sub-sections not in the > master TOC, but haven't had the time to add it in. It shouldn't be > hard to do on longer pages with lots of subsections. Its probably > mostly a matter of updating the CSS and adding the toctree directives > where necessary. > > -Mark > > On Dec 7, 4:47 am, AD7six wrote: > > > > > > > > > On Dec 6, 11:34 pm, aries wrote: > > > > Hi, > > > > I'm not sure if this is the right place to post my comments, but I'm > > > unable to find a more appropriate venue. Feel free to redirect me. > > > > Unlike previous versions, the 2.0 documentation lacks heading links > > > within the TOC. It used to be that when viewing a particular topic you > > > could access subtopics easily. For example, the 2.0 page on FormHelper > > > is extremely long and finding information on, say, structuring a > > > select options array can be maddening if you don't know where in the > > > page to look. Once found you can bookmark the paragraph's permalink, > > > but that's not very useful for quick reference lookups. > > > > Also, the current topic is not highlighted in the TOC navigation. It > > > would be helpful for the user to know where they are at any given > > > point. A breadcrumb trail might help here. > > > > Lastly, I'm wondering why user comments aren't allowed. I know that a > > > lot of comments can make a page unwieldy, but I thought the pre-1.3 > > > doc pages handled it well, with comments for each section available by > > > click. I often found those comments quite helpful. > > > A comment in place of simply editing the docs is not helpful. There > > aren't any useful comments on the old book that should not be edits > > (and that's if you can find one at all). This point has already been > > discussed ad nausium (here, on the group). > > > > I greatly appreciate the amount of information contained in the book > > > as well as the time and effort it must have taken to put these docs > > > together, but it seems to me that some attention to some basic > > > navigation UI would help tremendously. > > > I'm not clear on exactly what it is you're asking for - but the source > > for the docs are herehttps://github.com/cakephp/docs > > > AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
I've toyed with adding an on-page TOC for the sub-sections not in the master TOC, but haven't had the time to add it in. It shouldn't be hard to do on longer pages with lots of subsections. Its probably mostly a matter of updating the CSS and adding the toctree directives where necessary. -Mark On Dec 7, 4:47 am, AD7six wrote: > On Dec 6, 11:34 pm, aries wrote: > > > > > > > > > > > Hi, > > > I'm not sure if this is the right place to post my comments, but I'm > > unable to find a more appropriate venue. Feel free to redirect me. > > > Unlike previous versions, the 2.0 documentation lacks heading links > > within the TOC. It used to be that when viewing a particular topic you > > could access subtopics easily. For example, the 2.0 page on FormHelper > > is extremely long and finding information on, say, structuring a > > select options array can be maddening if you don't know where in the > > page to look. Once found you can bookmark the paragraph's permalink, > > but that's not very useful for quick reference lookups. > > > Also, the current topic is not highlighted in the TOC navigation. It > > would be helpful for the user to know where they are at any given > > point. A breadcrumb trail might help here. > > > Lastly, I'm wondering why user comments aren't allowed. I know that a > > lot of comments can make a page unwieldy, but I thought the pre-1.3 > > doc pages handled it well, with comments for each section available by > > click. I often found those comments quite helpful. > > A comment in place of simply editing the docs is not helpful. There > aren't any useful comments on the old book that should not be edits > (and that's if you can find one at all). This point has already been > discussed ad nausium (here, on the group). > > > > > I greatly appreciate the amount of information contained in the book > > as well as the time and effort it must have taken to put these docs > > together, but it seems to me that some attention to some basic > > navigation UI would help tremendously. > > I'm not clear on exactly what it is you're asking for - but the source > for the docs are herehttps://github.com/cakephp/docs > > AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Cake 2.0 documentation
On Dec 6, 11:34 pm, aries wrote: > Hi, > > I'm not sure if this is the right place to post my comments, but I'm > unable to find a more appropriate venue. Feel free to redirect me. > > Unlike previous versions, the 2.0 documentation lacks heading links > within the TOC. It used to be that when viewing a particular topic you > could access subtopics easily. For example, the 2.0 page on FormHelper > is extremely long and finding information on, say, structuring a > select options array can be maddening if you don't know where in the > page to look. Once found you can bookmark the paragraph's permalink, > but that's not very useful for quick reference lookups. > > Also, the current topic is not highlighted in the TOC navigation. It > would be helpful for the user to know where they are at any given > point. A breadcrumb trail might help here. > > Lastly, I'm wondering why user comments aren't allowed. I know that a > lot of comments can make a page unwieldy, but I thought the pre-1.3 > doc pages handled it well, with comments for each section available by > click. I often found those comments quite helpful. A comment in place of simply editing the docs is not helpful. There aren't any useful comments on the old book that should not be edits (and that's if you can find one at all). This point has already been discussed ad nausium (here, on the group). > > I greatly appreciate the amount of information contained in the book > as well as the time and effort it must have taken to put these docs > together, but it seems to me that some attention to some basic > navigation UI would help tremendously. I'm not clear on exactly what it is you're asking for - but the source for the docs are here https://github.com/cakephp/docs AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Cake 2.0 documentation
Hi, I'm not sure if this is the right place to post my comments, but I'm unable to find a more appropriate venue. Feel free to redirect me. Unlike previous versions, the 2.0 documentation lacks heading links within the TOC. It used to be that when viewing a particular topic you could access subtopics easily. For example, the 2.0 page on FormHelper is extremely long and finding information on, say, structuring a select options array can be maddening if you don't know where in the page to look. Once found you can bookmark the paragraph's permalink, but that's not very useful for quick reference lookups. Also, the current topic is not highlighted in the TOC navigation. It would be helpful for the user to know where they are at any given point. A breadcrumb trail might help here. Lastly, I'm wondering why user comments aren't allowed. I know that a lot of comments can make a page unwieldy, but I thought the pre-1.3 doc pages handled it well, with comments for each section available by click. I often found those comments quite helpful. I greatly appreciate the amount of information contained in the book as well as the time and effort it must have taken to put these docs together, but it seems to me that some attention to some basic navigation UI would help tremendously. Many thanks, -Brian -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 2.0 "Testing Controllers" documentation suggestion/correction
On Oct 28, 6:50 am, Thiago Campezzi wrote:
> Hi everyone,
>
> I was taking a look at the documentation for the test suite in CakePHP
> 2.0 - more specifically the part about testing controller code:
>
> http://book.cakephp.org/2.0/en/development/testing.html#testing-contr...
>
> The code example provided in this heading doesn't include the "public
> $fixtures" line - if you just copy and paste that example, it will run
> using the default database connection instead of the test one. This
> might have been omitted to make the example simpler, but I think the
> consequences of forgetting this line are potentially very dangerous
> (you might delete or update live data accidentally!).
>
> Here's a version of the same example that uses test fixtures, thus
> causing the test suite to use the test database connection:
>
> class ArticlesControllerTest extends ControllerTestCase {
>
> public $fixtures = array('app.article');
>
> function testIndex() {
> $result = $this->testAction('/articles/index');
> debug($result);
> }
>
> ... and so on until the end of the class
>
> I hope this saves someone some trouble when running and debugging
> their tests :)
Please click "Edit this file"
https://github.com/cakephp/docs/blob/master/en/development/testing.rst
Go on... you know you want to.
AD
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
2.0 "Testing Controllers" documentation suggestion/correction
Hi everyone,
I was taking a look at the documentation for the test suite in CakePHP
2.0 - more specifically the part about testing controller code:
http://book.cakephp.org/2.0/en/development/testing.html#testing-controllers
The code example provided in this heading doesn't include the "public
$fixtures" line - if you just copy and paste that example, it will run
using the default database connection instead of the test one. This
might have been omitted to make the example simpler, but I think the
consequences of forgetting this line are potentially very dangerous
(you might delete or update live data accidentally!).
Here's a version of the same example that uses test fixtures, thus
causing the test suite to use the test database connection:
class ArticlesControllerTest extends ControllerTestCase {
public $fixtures = array('app.article');
function testIndex() {
$result = $this->testAction('/articles/index');
debug($result);
}
... and so on until the end of the class
I hope this saves someone some trouble when running and debugging
their tests :)
Cheers,
Thiago
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
Re: CakePHP 1.3.11 and 2.0.0-beta released / any documentation
the documentation is here https://github.com/cakephp/docs 2011/7/28 Serkan Sipahi > hi there, > any documentation about cakephp 2.0 ? > > sipatshi > > -- > ** > Generally after a beta any existing functionality should stay the > same. New features will probably work their way in. But what is > already there shouldn't change too much unless there are serious > problems. > > -Mark > > On Jul 27, 5:22 am, Jens Dittrich wrote: > > Great Job! > > > > I would like to know if this beta release of 2.0 is also feature freeze > or > > are there still things to come? > > > > regards, > > Jens > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group > at http://groups.google.com/group/cake-php > > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group > at http://groups.google.com/group/cake-php > -- *Vitor Pacheco* *Skype: vitor.pacheco.costa Msn: vitor-...@hotmail.com* *Cel.: 71 8626-7909 Tel.: 71 3378-5778 **Tel.: 71 3287-3475* -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: CakePHP 1.3.11 and 2.0.0-beta released / any documentation
hi there, any documentation about cakephp 2.0 ? sipatshi Generally after a beta any existing functionality should stay the same. New features will probably work their way in. But what is already there shouldn't change too much unless there are serious problems. -Mark On Jul 27, 5:22 am, Jens Dittrich wrote: > Great Job! > > I would like to know if this beta release of 2.0 is also feature freeze or > are there still things to come? > > regards, > Jens -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Documentation changes
I've started work on converting the documentation into the format sphinx uses, as well as updating the content for 2.0. If you want to help you can fork the repository and make the changes you'd like to see. https://github.com/markstory/cakebook-experiment is the url for the repo, it will soon move into the official CakePHP github account, as the feedback so far has been pretty good. -Mark On Mar 20, 10:45 am, confidentia...@gmail.com wrote: > The documentation is very well done but has a few areas that could use > improvement. > > The self-help diagnosis centre is a great idea. And I agree 100% that > documentation on Ajax and Acl needs to be improved. > > Is anybody working on this? I am willing to lend a hand or even get this > started. > Sent from my BlackBerry device on the Rogers Wireless Network > > > > -Original Message- > From: Jeremy Burns | Class Outfit > > Sender: cake-php@googlegroups.com > Date: Fri, 18 Mar 2011 05:45:54 > To: > Reply-To: cake-php@googlegroups.com > Subject: Re: Documentation changes > > Sort of related to cricket's points, but I'd like to see the validation > section moved nearer to the model, rather than in a 'common tasks' section (I > couldn't see any reference to either validation or common tasks in the > proposed structure). Pleased common tasks has gone - it's contents ought to > be in the main body; a search will always show them anyway. > > I know you've only presented a tree and no indication of text > quality/quantity, so this might be premature. There are a couple of chestnuts > that always come up on the forum; ajax/js and ACL. I wonder if it is worth > adding some hearty text about them too? I think it is often acknowledged that > the section on the Js helper is a bit thin at present (also pleased to see > the Ajax and JavaScript helpers have gone - they are confusing still being in > the 1.3 doc when they have been deprecated). > > Another suggestion I'd make is some sort of self-help diagnosis centre (are > the files spelled correctly, have you stuck to conventions, do you have > mod_rewrite etc) and a flow chart that shows the order in which code is > processed (this file, then this action, then this callback etc). > > Thanks Mark & team. Great work. Can't wait to start using 2.0. > > Jeremy Burns > Class Outfit > > jeremybu...@classoutfit.comhttp://www.classoutfit.com > > On 18 Mar 2011, at 01:05, mark_story wrote: > > > On Mar 12, 3:58 pm, cricket wrote: > >> On Sat, Mar 12, 2011 at 12:48 PM, mark_story wrote: > >>> In the 1.3.7 release announcement, we announced the possible move to > >>> sphinx + git fordocumentation. The following experiments have turned > >>> up promising results, and the temporary repository contains functional > >>> documentation, that still needs some improvement. > > >>> One of the improvements that needs to occur is a restructuring of the > >>> documentation. The current structure of the cookbook, often confuses > >>> both new and experienced developers, as its not the most logical or > >>> best planned layout for thedocumentation. > > >>> We've hashed out what we think would be a better structure, but since > >>> the community uses thedocumentationfar more than we do, we want your > >>> opinions on how a new book should be structured. > > >>>https://github.com/markstory/cakebook-experiment/wiki/alternate-struc... > > >>> If you have the time look over the above link, and reply with any > >>> comments or alarm bells about this structure, or any glaring omissions > >>> that should be included. > > >> Thanks, Mark. My $0.02: > > >> I think it would be much better to put core components, helpers, and > >> behaviors in their respective sections instead of later, in the "Core > >> Libraries" section. It's the logical place to look them up, as well as > >> to introduce them right after explaining what a component, helper, or > >> behavior is. > > >> That's abou it. In all this looks like a really big improvement for > >> thedocumentationstructure. > > >> One other thing, although it's not a point about the structure. Make > >> sure that it's more obvious why 404s can happen when debug == 0. So > >> many people trip up on this. It's a great idea but it's not at all > >> obvious (which is the point, of course). And Cake has this mysterious > >> routing thing (not to mention mod_rewrite being involved), so a lot of > >>
Re: Documentation changes
The documentation is very well done but has a few areas that could use improvement. The self-help diagnosis centre is a great idea. And I agree 100% that documentation on Ajax and Acl needs to be improved. Is anybody working on this? I am willing to lend a hand or even get this started. Sent from my BlackBerry device on the Rogers Wireless Network -Original Message- From: Jeremy Burns | Class Outfit Sender: cake-php@googlegroups.com Date: Fri, 18 Mar 2011 05:45:54 To: Reply-To: cake-php@googlegroups.com Subject: Re: Documentation changes Sort of related to cricket's points, but I'd like to see the validation section moved nearer to the model, rather than in a 'common tasks' section (I couldn't see any reference to either validation or common tasks in the proposed structure). Pleased common tasks has gone - it's contents ought to be in the main body; a search will always show them anyway. I know you've only presented a tree and no indication of text quality/quantity, so this might be premature. There are a couple of chestnuts that always come up on the forum; ajax/js and ACL. I wonder if it is worth adding some hearty text about them too? I think it is often acknowledged that the section on the Js helper is a bit thin at present (also pleased to see the Ajax and JavaScript helpers have gone - they are confusing still being in the 1.3 doc when they have been deprecated). Another suggestion I'd make is some sort of self-help diagnosis centre (are the files spelled correctly, have you stuck to conventions, do you have mod_rewrite etc) and a flow chart that shows the order in which code is processed (this file, then this action, then this callback etc). Thanks Mark & team. Great work. Can't wait to start using 2.0. Jeremy Burns Class Outfit jeremybu...@classoutfit.com http://www.classoutfit.com On 18 Mar 2011, at 01:05, mark_story wrote: > On Mar 12, 3:58 pm, cricket wrote: >> On Sat, Mar 12, 2011 at 12:48 PM, mark_story wrote: >>> In the 1.3.7 release announcement, we announced the possible move to >>> sphinx + git fordocumentation. The following experiments have turned >>> up promising results, and the temporary repository contains functional >>> documentation, that still needs some improvement. >> >>> One of the improvements that needs to occur is a restructuring of the >>> documentation. The current structure of the cookbook, often confuses >>> both new and experienced developers, as its not the most logical or >>> best planned layout for thedocumentation. >> >>> We've hashed out what we think would be a better structure, but since >>> the community uses thedocumentationfar more than we do, we want your >>> opinions on how a new book should be structured. >> >>> https://github.com/markstory/cakebook-experiment/wiki/alternate-struc... >> >>> If you have the time look over the above link, and reply with any >>> comments or alarm bells about this structure, or any glaring omissions >>> that should be included. >> >> Thanks, Mark. My $0.02: >> >> I think it would be much better to put core components, helpers, and >> behaviors in their respective sections instead of later, in the "Core >> Libraries" section. It's the logical place to look them up, as well as >> to introduce them right after explaining what a component, helper, or >> behavior is. >> >> That's abou it. In all this looks like a really big improvement for >> thedocumentationstructure. >> >> One other thing, although it's not a point about the structure. Make >> sure that it's more obvious why 404s can happen when debug == 0. So >> many people trip up on this. It's a great idea but it's not at all >> obvious (which is the point, of course). And Cake has this mysterious >> routing thing (not to mention mod_rewrite being involved), so a lot of >> new users go chasing down that path (heh) instead of looking for the >> error in their code. I'm not sure what the text should read but it >> should be repeated in several prominent places in the book, IMHO. > > Thanks for the feedback Cricket. I was planning on mostly re-writing > the error handling docs as most of the behaviour has changed for 2.0. > Including information on how 404's can be triggered is a good idea as > well. > > -Mark > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > cake-php+uns
Re: Is there any good documentation on $form->inputs()?
Nevermind, figured it out! Thanks! On Mar 18, 1:27 pm, Parris wrote: > Not input singular... inputs, plural. > > On Mar 18, 12:52 pm, euromark wrote: > > > i think there is pretty much everything > > covered...http://book.cakephp.org/view/1390/Automagic-Form-Elements > > > On 18 Mrz., 20:19, Parris wrote: > > > > Everytime I use it (and I really love using it), I need to look up > > > info about it. It is no problem with datatime, text, textfields, and > > > checkboxes; however, on off change I need a select or upload field, I > > > need to do some work. Furthermore, if I want to change the label I > > > need to experiment a million times, and figure out what it is looking > > > for... Has this function been documented in more detail anywhere? The > > > API doc is pretty useless for this function. It isn't even in the book > > > anymore. > > > > Thanks, > > > Parris -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Is there any good documentation on $form->inputs()?
http://api13.cakephp.org/class/form-helper#method-FormHelperinputs On Mar 18, 12:52 pm, euromark wrote: > i think there is pretty much everything > covered...http://book.cakephp.org/view/1390/Automagic-Form-Elements > > On 18 Mrz., 20:19, Parris wrote: > > > Everytime I use it (and I really love using it), I need to look up > > info about it. It is no problem with datatime, text, textfields, and > > checkboxes; however, on off change I need a select or upload field, I > > need to do some work. Furthermore, if I want to change the label I > > need to experiment a million times, and figure out what it is looking > > for... Has this function been documented in more detail anywhere? The > > API doc is pretty useless for this function. It isn't even in the book > > anymore. > > > Thanks, > > Parris -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Is there any good documentation on $form->inputs()?
Not input singular... inputs, plural. On Mar 18, 12:52 pm, euromark wrote: > i think there is pretty much everything > covered...http://book.cakephp.org/view/1390/Automagic-Form-Elements > > On 18 Mrz., 20:19, Parris wrote: > > > Everytime I use it (and I really love using it), I need to look up > > info about it. It is no problem with datatime, text, textfields, and > > checkboxes; however, on off change I need a select or upload field, I > > need to do some work. Furthermore, if I want to change the label I > > need to experiment a million times, and figure out what it is looking > > for... Has this function been documented in more detail anywhere? The > > API doc is pretty useless for this function. It isn't even in the book > > anymore. > > > Thanks, > > Parris -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Is there any good documentation on $form->inputs()?
i think there is pretty much everything covered... http://book.cakephp.org/view/1390/Automagic-Form-Elements On 18 Mrz., 20:19, Parris wrote: > Everytime I use it (and I really love using it), I need to look up > info about it. It is no problem with datatime, text, textfields, and > checkboxes; however, on off change I need a select or upload field, I > need to do some work. Furthermore, if I want to change the label I > need to experiment a million times, and figure out what it is looking > for... Has this function been documented in more detail anywhere? The > API doc is pretty useless for this function. It isn't even in the book > anymore. > > Thanks, > Parris -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Is there any good documentation on $form->inputs()?
Everytime I use it (and I really love using it), I need to look up info about it. It is no problem with datatime, text, textfields, and checkboxes; however, on off change I need a select or upload field, I need to do some work. Furthermore, if I want to change the label I need to experiment a million times, and figure out what it is looking for... Has this function been documented in more detail anywhere? The API doc is pretty useless for this function. It isn't even in the book anymore. Thanks, Parris -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Documentation changes
Sort of related to cricket's points, but I'd like to see the validation section moved nearer to the model, rather than in a 'common tasks' section (I couldn't see any reference to either validation or common tasks in the proposed structure). Pleased common tasks has gone - it's contents ought to be in the main body; a search will always show them anyway. I know you've only presented a tree and no indication of text quality/quantity, so this might be premature. There are a couple of chestnuts that always come up on the forum; ajax/js and ACL. I wonder if it is worth adding some hearty text about them too? I think it is often acknowledged that the section on the Js helper is a bit thin at present (also pleased to see the Ajax and JavaScript helpers have gone - they are confusing still being in the 1.3 doc when they have been deprecated). Another suggestion I'd make is some sort of self-help diagnosis centre (are the files spelled correctly, have you stuck to conventions, do you have mod_rewrite etc) and a flow chart that shows the order in which code is processed (this file, then this action, then this callback etc). Thanks Mark & team. Great work. Can't wait to start using 2.0. Jeremy Burns Class Outfit jeremybu...@classoutfit.com http://www.classoutfit.com On 18 Mar 2011, at 01:05, mark_story wrote: > On Mar 12, 3:58 pm, cricket wrote: >> On Sat, Mar 12, 2011 at 12:48 PM, mark_story wrote: >>> In the 1.3.7 release announcement, we announced the possible move to >>> sphinx + git fordocumentation. The following experiments have turned >>> up promising results, and the temporary repository contains functional >>> documentation, that still needs some improvement. >> >>> One of the improvements that needs to occur is a restructuring of the >>> documentation. The current structure of the cookbook, often confuses >>> both new and experienced developers, as its not the most logical or >>> best planned layout for thedocumentation. >> >>> We've hashed out what we think would be a better structure, but since >>> the community uses thedocumentationfar more than we do, we want your >>> opinions on how a new book should be structured. >> >>> https://github.com/markstory/cakebook-experiment/wiki/alternate-struc... >> >>> If you have the time look over the above link, and reply with any >>> comments or alarm bells about this structure, or any glaring omissions >>> that should be included. >> >> Thanks, Mark. My $0.02: >> >> I think it would be much better to put core components, helpers, and >> behaviors in their respective sections instead of later, in the "Core >> Libraries" section. It's the logical place to look them up, as well as >> to introduce them right after explaining what a component, helper, or >> behavior is. >> >> That's abou it. In all this looks like a really big improvement for >> thedocumentationstructure. >> >> One other thing, although it's not a point about the structure. Make >> sure that it's more obvious why 404s can happen when debug == 0. So >> many people trip up on this. It's a great idea but it's not at all >> obvious (which is the point, of course). And Cake has this mysterious >> routing thing (not to mention mod_rewrite being involved), so a lot of >> new users go chasing down that path (heh) instead of looking for the >> error in their code. I'm not sure what the text should read but it >> should be repeated in several prominent places in the book, IMHO. > > Thanks for the feedback Cricket. I was planning on mostly re-writing > the error handling docs as most of the behaviour has changed for 2.0. > Including information on how 404's can be triggered is a good idea as > well. > > -Mark > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group at > http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Documentation changes
On Thu, Mar 17, 2011 at 9:05 PM, mark_story wrote: > > Thanks for the feedback Cricket. I was planning on mostly re-writing > the error handling docs as most of the behaviour has changed for 2.0. > Including information on how 404's can be triggered is a good idea as > well. Of course, most people won't get to error handling--if ever--until they've got a pretty good grasp of Cake. Maybe random FAQs could pop up every so many page views. "Getting 404 errors? Click here!" heh -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Documentation changes
On Mar 12, 3:58 pm, cricket wrote: > On Sat, Mar 12, 2011 at 12:48 PM, mark_story wrote: > > In the 1.3.7 release announcement, we announced the possible move to > > sphinx + git fordocumentation. The following experiments have turned > > up promising results, and the temporary repository contains functional > >documentation, that still needs some improvement. > > > One of the improvements that needs to occur is a restructuring of the > >documentation. The current structure of the cookbook, often confuses > > both new and experienced developers, as its not the most logical or > > best planned layout for thedocumentation. > > > We've hashed out what we think would be a better structure, but since > > the community uses thedocumentationfar more than we do, we want your > > opinions on how a new book should be structured. > > >https://github.com/markstory/cakebook-experiment/wiki/alternate-struc... > > > If you have the time look over the above link, and reply with any > > comments or alarm bells about this structure, or any glaring omissions > > that should be included. > > Thanks, Mark. My $0.02: > > I think it would be much better to put core components, helpers, and > behaviors in their respective sections instead of later, in the "Core > Libraries" section. It's the logical place to look them up, as well as > to introduce them right after explaining what a component, helper, or > behavior is. > > That's abou it. In all this looks like a really big improvement for > thedocumentationstructure. > > One other thing, although it's not a point about the structure. Make > sure that it's more obvious why 404s can happen when debug == 0. So > many people trip up on this. It's a great idea but it's not at all > obvious (which is the point, of course). And Cake has this mysterious > routing thing (not to mention mod_rewrite being involved), so a lot of > new users go chasing down that path (heh) instead of looking for the > error in their code. I'm not sure what the text should read but it > should be repeated in several prominent places in the book, IMHO. Thanks for the feedback Cricket. I was planning on mostly re-writing the error handling docs as most of the behaviour has changed for 2.0. Including information on how 404's can be triggered is a good idea as well. -Mark -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: Documentation changes
On Sat, Mar 12, 2011 at 12:48 PM, mark_story wrote: > In the 1.3.7 release announcement, we announced the possible move to > sphinx + git for documentation. The following experiments have turned > up promising results, and the temporary repository contains functional > documentation, that still needs some improvement. > > One of the improvements that needs to occur is a restructuring of the > documentation. The current structure of the cookbook, often confuses > both new and experienced developers, as its not the most logical or > best planned layout for the documentation. > > We've hashed out what we think would be a better structure, but since > the community uses the documentation far more than we do, we want your > opinions on how a new book should be structured. > > https://github.com/markstory/cakebook-experiment/wiki/alternate-structure > > If you have the time look over the above link, and reply with any > comments or alarm bells about this structure, or any glaring omissions > that should be included. Thanks, Mark. My $0.02: I think it would be much better to put core components, helpers, and behaviors in their respective sections instead of later, in the "Core Libraries" section. It's the logical place to look them up, as well as to introduce them right after explaining what a component, helper, or behavior is. That's abou it. In all this looks like a really big improvement for the documentation structure. One other thing, although it's not a point about the structure. Make sure that it's more obvious why 404s can happen when debug == 0. So many people trip up on this. It's a great idea but it's not at all obvious (which is the point, of course). And Cake has this mysterious routing thing (not to mention mod_rewrite being involved), so a lot of new users go chasing down that path (heh) instead of looking for the error in their code. I'm not sure what the text should read but it should be repeated in several prominent places in the book, IMHO. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Documentation changes
In the 1.3.7 release announcement, we announced the possible move to sphinx + git for documentation. The following experiments have turned up promising results, and the temporary repository contains functional documentation, that still needs some improvement. One of the improvements that needs to occur is a restructuring of the documentation. The current structure of the cookbook, often confuses both new and experienced developers, as its not the most logical or best planned layout for the documentation. We've hashed out what we think would be a better structure, but since the community uses the documentation far more than we do, we want your opinions on how a new book should be structured. https://github.com/markstory/cakebook-experiment/wiki/alternate-structure If you have the time look over the above link, and reply with any comments or alarm bells about this structure, or any glaring omissions that should be included. -Mark -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: XML Helper Documentation needed
Hi Sam On 18 February 2011 16:13, Sam Sherlock wrote: > Here I have adjusted NCM's code as it did not use the File class > > - S > > Thanks for the amendment, I will update my blog post accordingly and my file in the previous project. I agree the File class is better than using fopen, my fopen line in my code is actually a full path from root. -- Kind Regards Stephen @ NinjaCoderMonkey www.ninjacodermonkey.co.uk -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: XML Helper Documentation needed
Here I have adjusted NCM's code as it did not use the File class
and was outputting the generated xml to the file twice (one after the other)
also I have amended to have a id which is Stephen22
$xmlData = array(
'person' => array(
'id' => 'Stephen22',
'name' => 'Stephen',
'age' => 22,
'hair' => array(
'length' => 'medium',
'colour' => 'dark brown'
)
)
);
App::import('Helper', 'Xml');
App::import('Core', 'File');
$xml = new XmlHelper();
$file = $xml->header(); // We need the XML header before our data.
$file .= $xml->serialize($xmlData, array('whitespace' => true));
// Write the file.
$xmlFile = new File(TMP . '/filename.xml');
$xmlFile->write($file, 'w');
$xmlFile->close();
Whereas
$xmlData = array(
'person' => array(
'id' => 'Stephen22',
'name' => 'Stephen',
'age' => 22,
'hair' => array(
'length' => 'medium',
'colour' => 'dark brown'
),
'being' => array('I am a fish')
)
);
outputs
- S
On 18 February 2011 15:19, Matthew McNaughton wrote:
> Greetings all,
> I was wondering if someone could point me to a more detailed description of
> the XML Helper and how to produce a desired xml file from a php array.
>
> I've gone through the following documentation
> http://book.cakephp.org/view/1485/Xml
> http://book.cakephp.org/view/1473/XML
> http://book.cakephp.org/view/1238/REST
>
> Even found this external link, which I thought to be the most useful
>
> http://www.ninjacodermonkey.co.uk/2010/11/cakephp-array-to-xml-from-within-controller/
>
> Essentially, what I'd like to know some more about is whether the xml
> helper allows you to do things like add tag ids. Also, if there were any
> more resources out there that others had come accross on how the php arrays
> should be structured etc.
>
> Let me know.
>
> Regards,
> Mmm
> --
> Our newest site for the community: CakePHP Video Tutorials
> http://tv.cakephp.org
> Check out the new CakePHP Questions site http://ask.cakephp.org and help
> others with their CakePHP related questions.
>
>
> To unsubscribe from this group, send email to
> cake-php+unsubscr...@googlegroups.com For more options, visit this group
> at http://groups.google.com/group/cake-php
>
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php
XML Helper Documentation needed
Greetings all, I was wondering if someone could point me to a more detailed description of the XML Helper and how to produce a desired xml file from a php array. I've gone through the following documentation http://book.cakephp.org/view/1485/Xml http://book.cakephp.org/view/1473/XML http://book.cakephp.org/view/1238/REST Even found this external link, which I thought to be the most useful http://www.ninjacodermonkey.co.uk/2010/11/cakephp-array-to-xml-from-within-controller/ Essentially, what I'd like to know some more about is whether the xml helper allows you to do things like add tag ids. Also, if there were any more resources out there that others had come accross on how the php arrays should be structured etc. Let me know. Regards, Mmm -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
CakePOWER Services documentation (first review)
Hi coders, I'm developing a CakePHP extension to enhance cake with professional coding needs and requirements. I just published a page to describe a code practice named "service". I please you to read this page and suggest me mistakes because I'm not very up to date with english! http://www.cakepower.org/wiki/doku.php?id=services:index Thank you! Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Function documentation?
@Anthony Other than the fact that you can submit edits for the docs, I would argue that you can submit articles to the bakery and edit cookbook sections if you have or need relevant examples. There are also hundreds of blog posts showing examples on how to fix common problems. Part of being a developer is learning on your own, by digging in and trying things out, and if someone isn't going to do that they might be better off working with Joomla or Wordpress. tldr; Please RTFM and "works for me" On Aug 30, 1:03 pm, Anthony wrote: > @geoB>Thank you for the valuable insight into the Cake Way. > > Any time. Keep at it, cake is really really awesome! > > @j.blotus > And there are thousands more who likely disagree with you. People > like you chime in any time the documentation is knocked. For most > people wanting to use cake I assume they are amateur developers like > myself and my not be so familiar with the MVC design. I understood > the concept but using something in practice is a much different ball > game. > > Here's a simple scenario that I see often: how do you pass info from > one action to another. Most people really aren't so stupid to know > they can pass information via a cookie, session, URL parameters, > etc...so I assume when people ask this elementary web-development > question I always they mean "the cake way" unless they prove > otherwise. Why some of you are so against the inclusion of more > examples of "the cake way" of doing common tasks into the common tasks > section of the handbook completely baffles me. The "real" world > example (blog post) only demonstrates so much and unfortunately it's > barely the tip of the ice burg. > > On Aug 30, 7:27 am, geoB wrote: > > > > > @Anthony: > > > Thank you for the valuable insight into the Cake Way. > > > I started with it with the intention of rewriting an existing online > > application. The documentation struck me as a good set of reminders > > for those who already "got it". I've only rebuilt my database once. > > So far. I suppose "rapid development" is relative. Since my > > development is all volunteer I guess I'm a bit impatient. > > > George > > > On Aug 29, 9:28 pm, Anthony wrote: > > > > The documentation covers this but you REALLY gotta read into it > > > > These two pages are vital to "getting" cake IMO. > > > >http://book.cakephp.org/view/890/Understanding-Model-View-Controllerh... > > > > Once these two really begin sinking in these two pages will likely > > > become your next best source of info: > > > >http://book.cakephp.org/view/1039/Associations-Linking-Models-Togethe... > > > > I'm with you in that some of the documentation is lacking on examples > > > on doing things the "cake way" but really good on the technical side > > > once you figure out the "cake way". > > > > FWIW, I've been building a site in my spare time but have restructured > > > everything twice because I find something new in cake that makes most > > > of what I've already done redundant. IE: not making use of elements > > > or not understanding how bad-ass contain is, or realizing that > > > ultimately I have the control and the index, view, delete, add > > > functions that the tutorial goes on about aren't really important, its > > > all in the naming, keying and structuring. > > > > On Aug 29, 9:31 pm, geoB wrote: > > > > > "When someone browsers to /controller/index, it calls the index() > > > > method for > > > > the controller, which usually contains a find call for the model > > > > associated > > > > with the controller and sets a variable which is available in the > > > > index view > > > > for the controller in question. " > > > > > This is the kind of information I was looking for. I am more of a > > > > deductive than inductive logic person. The use of the method in the > > > > tutorial doesn't explain to me what it's doing there or how it is > > > > used. (I've not found any mention of an index() method in any > > > > controller. Why is that?) > > > > > Thanks immensely for clearing this up. > > > > > George > > > > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > > > > the index() method in your controllers wont have any parameters...or > > > > > maybe > > > > > it will - its up to you. >
Re: Function documentation?
@geoB >Thank you for the valuable insight into the Cake Way. Any time. Keep at it, cake is really really awesome! @j.blotus And there are thousands more who likely disagree with you. People like you chime in any time the documentation is knocked. For most people wanting to use cake I assume they are amateur developers like myself and my not be so familiar with the MVC design. I understood the concept but using something in practice is a much different ball game. Here's a simple scenario that I see often: how do you pass info from one action to another. Most people really aren't so stupid to know they can pass information via a cookie, session, URL parameters, etc...so I assume when people ask this elementary web-development question I always they mean "the cake way" unless they prove otherwise. Why some of you are so against the inclusion of more examples of "the cake way" of doing common tasks into the common tasks section of the handbook completely baffles me. The "real" world example (blog post) only demonstrates so much and unfortunately it's barely the tip of the ice burg. On Aug 30, 7:27 am, geoB wrote: > @Anthony: > > Thank you for the valuable insight into the Cake Way. > > I started with it with the intention of rewriting an existing online > application. The documentation struck me as a good set of reminders > for those who already "got it". I've only rebuilt my database once. > So far. I suppose "rapid development" is relative. Since my > development is all volunteer I guess I'm a bit impatient. > > George > > On Aug 29, 9:28 pm, Anthony wrote: > > > The documentation covers this but you REALLY gotta read into it > > > These two pages are vital to "getting" cake IMO. > > >http://book.cakephp.org/view/890/Understanding-Model-View-Controllerh... > > > Once these two really begin sinking in these two pages will likely > > become your next best source of info: > > >http://book.cakephp.org/view/1039/Associations-Linking-Models-Togethe... > > > I'm with you in that some of the documentation is lacking on examples > > on doing things the "cake way" but really good on the technical side > > once you figure out the "cake way". > > > FWIW, I've been building a site in my spare time but have restructured > > everything twice because I find something new in cake that makes most > > of what I've already done redundant. IE: not making use of elements > > or not understanding how bad-ass contain is, or realizing that > > ultimately I have the control and the index, view, delete, add > > functions that the tutorial goes on about aren't really important, its > > all in the naming, keying and structuring. > > > On Aug 29, 9:31 pm, geoB wrote: > > > > "When someone browsers to /controller/index, it calls the index() > > > method for > > > the controller, which usually contains a find call for the model > > > associated > > > with the controller and sets a variable which is available in the > > > index view > > > for the controller in question. " > > > > This is the kind of information I was looking for. I am more of a > > > deductive than inductive logic person. The use of the method in the > > > tutorial doesn't explain to me what it's doing there or how it is > > > used. (I've not found any mention of an index() method in any > > > controller. Why is that?) > > > > Thanks immensely for clearing this up. > > > > George > > > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > > > the index() method in your controllers wont have any parameters...or > > > > maybe > > > > it will - its up to you. > > > > > Hell you don't even have to define one if you don't want to. > > > > > When someone browsers to /controller/index, it calls the index() method > > > > for > > > > the controller, which usually contains a find call for the model > > > > associated > > > > with the controller and sets a variable which is available in the index > > > > view > > > > for the controller in question. > > > > > Take a look at the blog tutorial in the book - it'll show you exactly > > > > how > > > > this works. > > > > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > > > > I have searched Google, CakePHP Google Group, API Controller > > > > > documentation (versions 1.2, 1.3), API AppController docum
Re: Function documentation?
I have to disagree with your notion that the cookbook is just for people who already "got it". I learned from the cookbook, and so did thousands of others. Here are some pages to look at: http://book.cakephp.org/view/955/Controllers http://book.cakephp.org/view/1001/Understanding-Models http://book.cakephp.org/view/898/A-Typical-CakePHP-Request On Aug 30, 8:27 am, geoB wrote: > @Anthony: > > Thank you for the valuable insight into the Cake Way. > > I started with it with the intention of rewriting an existing online > application. The documentation struck me as a good set of reminders > for those who already "got it". I've only rebuilt my database once. > So far. I suppose "rapid development" is relative. Since my > development is all volunteer I guess I'm a bit impatient. > > George > > On Aug 29, 9:28 pm, Anthony wrote: > > > > > The documentation covers this but you REALLY gotta read into it > > > These two pages are vital to "getting" cake IMO. > > >http://book.cakephp.org/view/890/Understanding-Model-View-Controllerh... > > > Once these two really begin sinking in these two pages will likely > > become your next best source of info: > > >http://book.cakephp.org/view/1039/Associations-Linking-Models-Togethe... > > > I'm with you in that some of the documentation is lacking on examples > > on doing things the "cake way" but really good on the technical side > > once you figure out the "cake way". > > > FWIW, I've been building a site in my spare time but have restructured > > everything twice because I find something new in cake that makes most > > of what I've already done redundant. IE: not making use of elements > > or not understanding how bad-ass contain is, or realizing that > > ultimately I have the control and the index, view, delete, add > > functions that the tutorial goes on about aren't really important, its > > all in the naming, keying and structuring. > > > On Aug 29, 9:31 pm, geoB wrote: > > > > "When someone browsers to /controller/index, it calls the index() > > > method for > > > the controller, which usually contains a find call for the model > > > associated > > > with the controller and sets a variable which is available in the > > > index view > > > for the controller in question. " > > > > This is the kind of information I was looking for. I am more of a > > > deductive than inductive logic person. The use of the method in the > > > tutorial doesn't explain to me what it's doing there or how it is > > > used. (I've not found any mention of an index() method in any > > > controller. Why is that?) > > > > Thanks immensely for clearing this up. > > > > George > > > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > > > the index() method in your controllers wont have any parameters...or > > > > maybe > > > > it will - its up to you. > > > > > Hell you don't even have to define one if you don't want to. > > > > > When someone browsers to /controller/index, it calls the index() method > > > > for > > > > the controller, which usually contains a find call for the model > > > > associated > > > > with the controller and sets a variable which is available in the index > > > > view > > > > for the controller in question. > > > > > Take a look at the blog tutorial in the book - it'll show you exactly > > > > how > > > > this works. > > > > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > > > > I have searched Google, CakePHP Google Group, API Controller > > > > > documentation (versions 1.2, 1.3), API AppController documentation > > > > > (versions 1.2, 1.3) and have found no useful information on the > > > > > parameters used by the index method. Search terms include "index > > > > > method", "index method" & documentation, "Index method" & syntax. I > > > > > ain't no dummy, and I don't expect to be spoon-fed. > > > > > > Sure, my understanding isn't what it could be. That's why I read the > > > > > documentation. But reading alone does not create comprehension. > > > > > Actual use of the material to observe its effects is required as > > > > > well. But I can't try to recreate something I cannot find > >
Re: Function documentation?
@Anthony: Thank you for the valuable insight into the Cake Way. I started with it with the intention of rewriting an existing online application. The documentation struck me as a good set of reminders for those who already "got it". I've only rebuilt my database once. So far. I suppose "rapid development" is relative. Since my development is all volunteer I guess I'm a bit impatient. George On Aug 29, 9:28 pm, Anthony wrote: > The documentation covers this but you REALLY gotta read into it > > These two pages are vital to "getting" cake IMO. > > http://book.cakephp.org/view/890/Understanding-Model-View-Controllerhttp://book.cakephp.org/view/901/CakePHP-Conventions > > Once these two really begin sinking in these two pages will likely > become your next best source of info: > > http://book.cakephp.org/view/1039/Associations-Linking-Models-Togetherhttp://book.cakephp.org/view/1017/Retrieving-Your-Data > > I'm with you in that some of the documentation is lacking on examples > on doing things the "cake way" but really good on the technical side > once you figure out the "cake way". > > FWIW, I've been building a site in my spare time but have restructured > everything twice because I find something new in cake that makes most > of what I've already done redundant. IE: not making use of elements > or not understanding how bad-ass contain is, or realizing that > ultimately I have the control and the index, view, delete, add > functions that the tutorial goes on about aren't really important, its > all in the naming, keying and structuring. > > On Aug 29, 9:31 pm, geoB wrote: > > > "When someone browsers to /controller/index, it calls the index() > > method for > > the controller, which usually contains a find call for the model > > associated > > with the controller and sets a variable which is available in the > > index view > > for the controller in question. " > > > This is the kind of information I was looking for. I am more of a > > deductive than inductive logic person. The use of the method in the > > tutorial doesn't explain to me what it's doing there or how it is > > used. (I've not found any mention of an index() method in any > > controller. Why is that?) > > > Thanks immensely for clearing this up. > > > George > > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > > the index() method in your controllers wont have any parameters...or maybe > > > it will - its up to you. > > > > Hell you don't even have to define one if you don't want to. > > > > When someone browsers to /controller/index, it calls the index() method > > > for > > > the controller, which usually contains a find call for the model > > > associated > > > with the controller and sets a variable which is available in the index > > > view > > > for the controller in question. > > > > Take a look at the blog tutorial in the book - it'll show you exactly how > > > this works. > > > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > > > I have searched Google, CakePHP Google Group, API Controller > > > > documentation (versions 1.2, 1.3), API AppController documentation > > > > (versions 1.2, 1.3) and have found no useful information on the > > > > parameters used by the index method. Search terms include "index > > > > method", "index method" & documentation, "Index method" & syntax. I > > > > ain't no dummy, and I don't expect to be spoon-fed. > > > > > Sure, my understanding isn't what it could be. That's why I read the > > > > documentation. But reading alone does not create comprehension. > > > > Actual use of the material to observe its effects is required as > > > > well. But I can't try to recreate something I cannot find > > > > documentation on. > > > > > Perhaps a more specific reference would be useful. I have read the > > > > manual at least twice now, and I know I'm not ready for the exam. > > > > > g > > > > > On Aug 29, 1:18 pm, "j.blotus" wrote: > > > > > i think you need to start again from the beginning of the manual. > > > > > index() is controller action. It gets records from the Model and sends > > > > > them to the view. It sounds like you don't really understand the way > > > > > CakePHP uses MVC. Also, the core has an extensive API for
Re: Function documentation?
The documentation covers this but you REALLY gotta read into it These two pages are vital to "getting" cake IMO. http://book.cakephp.org/view/890/Understanding-Model-View-Controller http://book.cakephp.org/view/901/CakePHP-Conventions Once these two really begin sinking in these two pages will likely become your next best source of info: http://book.cakephp.org/view/1039/Associations-Linking-Models-Together http://book.cakephp.org/view/1017/Retrieving-Your-Data I'm with you in that some of the documentation is lacking on examples on doing things the "cake way" but really good on the technical side once you figure out the "cake way". FWIW, I've been building a site in my spare time but have restructured everything twice because I find something new in cake that makes most of what I've already done redundant. IE: not making use of elements or not understanding how bad-ass contain is, or realizing that ultimately I have the control and the index, view, delete, add functions that the tutorial goes on about aren't really important, its all in the naming, keying and structuring. On Aug 29, 9:31 pm, geoB wrote: > "When someone browsers to /controller/index, it calls the index() > method for > the controller, which usually contains a find call for the model > associated > with the controller and sets a variable which is available in the > index view > for the controller in question. " > > This is the kind of information I was looking for. I am more of a > deductive than inductive logic person. The use of the method in the > tutorial doesn't explain to me what it's doing there or how it is > used. (I've not found any mention of an index() method in any > controller. Why is that?) > > Thanks immensely for clearing this up. > > George > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > the index() method in your controllers wont have any parameters...or maybe > > it will - its up to you. > > > Hell you don't even have to define one if you don't want to. > > > When someone browsers to /controller/index, it calls the index() method for > > the controller, which usually contains a find call for the model associated > > with the controller and sets a variable which is available in the index view > > for the controller in question. > > > Take a look at the blog tutorial in the book - it'll show you exactly how > > this works. > > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > > I have searched Google, CakePHP Google Group, API Controller > > > documentation (versions 1.2, 1.3), API AppController documentation > > > (versions 1.2, 1.3) and have found no useful information on the > > > parameters used by the index method. Search terms include "index > > > method", "index method" & documentation, "Index method" & syntax. I > > > ain't no dummy, and I don't expect to be spoon-fed. > > > > Sure, my understanding isn't what it could be. That's why I read the > > > documentation. But reading alone does not create comprehension. > > > Actual use of the material to observe its effects is required as > > > well. But I can't try to recreate something I cannot find > > > documentation on. > > > > Perhaps a more specific reference would be useful. I have read the > > > manual at least twice now, and I know I'm not ready for the exam. > > > > g > > > > On Aug 29, 1:18 pm, "j.blotus" wrote: > > > > i think you need to start again from the beginning of the manual. > > > > index() is controller action. It gets records from the Model and sends > > > > them to the view. It sounds like you don't really understand the way > > > > CakePHP uses MVC. Also, the core has an extensive API for versions > > > > 1.1, 1.2, and 1.3. > > > > > On Aug 28, 1:08 pm, geoB wrote: > > > > > > I am trying to get started with CakePHP and am experiencing some > > > > > frustration with the documentation. (fwiw, I am moderately well > > > > > experienced with PHP.) For example, I was following the blog tutorial > > > > > at the CakePHP website, only trying to adapt it to the database I > > > > > intend to work with. I learned that the index() function was > > > > > referring to an index of a table. So I started to look for the syntax > > > > > of the index() function to no avail. There does not appear to be a > > > > > function reference anywhere that I can find. > > > > > &g
Re: Function documentation?
The documentation covers this but you REALLY gotta read into it These two pages are vital to "getting" cake IMO. http://book.cakephp.org/view/890/Understanding-Model-View-Controller http://book.cakephp.org/view/901/CakePHP-Conventions Once these two really begin sinking in these two pages will likely become your next best source of info: http://book.cakephp.org/view/1039/Associations-Linking-Models-Together http://book.cakephp.org/view/1017/Retrieving-Your-Data I'm with you in that some of the documentation is lacking on examples on doing things the "cake way" but really good on the technical side once you figure out the "cake way". FWIW, I've been building a site in my spare time but have restructured everything twice because I find something new in cake that makes most of what I've already done redundant. IE: not making use of elements or not understanding how bad-ass contain is, or realizing that ultimately I have the control and the index, view, delete, add functions that the tutorial goes on about aren't really important, its all in the naming, keying and structuring. On Aug 29, 9:31 pm, geoB wrote: > "When someone browsers to /controller/index, it calls the index() > method for > the controller, which usually contains a find call for the model > associated > with the controller and sets a variable which is available in the > index view > for the controller in question. " > > This is the kind of information I was looking for. I am more of a > deductive than inductive logic person. The use of the method in the > tutorial doesn't explain to me what it's doing there or how it is > used. (I've not found any mention of an index() method in any > controller. Why is that?) > > Thanks immensely for clearing this up. > > George > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > the index() method in your controllers wont have any parameters...or maybe > > it will - its up to you. > > > Hell you don't even have to define one if you don't want to. > > > When someone browsers to /controller/index, it calls the index() method for > > the controller, which usually contains a find call for the model associated > > with the controller and sets a variable which is available in the index view > > for the controller in question. > > > Take a look at the blog tutorial in the book - it'll show you exactly how > > this works. > > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > > I have searched Google, CakePHP Google Group, API Controller > > > documentation (versions 1.2, 1.3), API AppController documentation > > > (versions 1.2, 1.3) and have found no useful information on the > > > parameters used by the index method. Search terms include "index > > > method", "index method" & documentation, "Index method" & syntax. I > > > ain't no dummy, and I don't expect to be spoon-fed. > > > > Sure, my understanding isn't what it could be. That's why I read the > > > documentation. But reading alone does not create comprehension. > > > Actual use of the material to observe its effects is required as > > > well. But I can't try to recreate something I cannot find > > > documentation on. > > > > Perhaps a more specific reference would be useful. I have read the > > > manual at least twice now, and I know I'm not ready for the exam. > > > > g > > > > On Aug 29, 1:18 pm, "j.blotus" wrote: > > > > i think you need to start again from the beginning of the manual. > > > > index() is controller action. It gets records from the Model and sends > > > > them to the view. It sounds like you don't really understand the way > > > > CakePHP uses MVC. Also, the core has an extensive API for versions > > > > 1.1, 1.2, and 1.3. > > > > > On Aug 28, 1:08 pm, geoB wrote: > > > > > > I am trying to get started with CakePHP and am experiencing some > > > > > frustration with the documentation. (fwiw, I am moderately well > > > > > experienced with PHP.) For example, I was following the blog tutorial > > > > > at the CakePHP website, only trying to adapt it to the database I > > > > > intend to work with. I learned that the index() function was > > > > > referring to an index of a table. So I started to look for the syntax > > > > > of the index() function to no avail. There does not appear to be a > > > > > function reference anywhere that I can find. > > > > > &g
Re: Function documentation?
There is no documentation for an index() method in the API docs because no such method exists. Its a method you create as part of the tutorial to handle requests for a list of posts. Controller actions, or controller methods are accessible by the url. Generally these methods are created by you the application developer. -Mark On Aug 29, 10:31 pm, geoB wrote: > "When someone browsers to /controller/index, it calls the index() > method for > the controller, which usually contains a find call for the model > associated > with the controller and sets a variable which is available in the > index view > for the controller in question. " > > This is the kind of information I was looking for. I am more of a > deductive than inductive logic person. The use of the method in the > tutorial doesn't explain to me what it's doing there or how it is > used. (I've not found any mention of an index() method in any > controller. Why is that?) > > Thanks immensely for clearing this up. > > George > > On Aug 29, 7:01 pm, Greg Skerman wrote: > > > > > > > > > the index() method in your controllers wont have any parameters...or maybe > > it will - its up to you. > > > Hell you don't even have to define one if you don't want to. > > > When someone browsers to /controller/index, it calls the index() method for > > the controller, which usually contains a find call for the model associated > > with the controller and sets a variable which is available in the index view > > for the controller in question. > > > Take a look at the blog tutorial in the book - it'll show you exactly how > > this works. > > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > > I have searched Google, CakePHP Google Group, API Controller > > > documentation (versions 1.2, 1.3), API AppController documentation > > > (versions 1.2, 1.3) and have found no useful information on the > > > parameters used by the index method. Search terms include "index > > > method", "index method" & documentation, "Index method" & syntax. I > > > ain't no dummy, and I don't expect to be spoon-fed. > > > > Sure, my understanding isn't what it could be. That's why I read the > > > documentation. But reading alone does not create comprehension. > > > Actual use of the material to observe its effects is required as > > > well. But I can't try to recreate something I cannot find > > > documentation on. > > > > Perhaps a more specific reference would be useful. I have read the > > > manual at least twice now, and I know I'm not ready for the exam. > > > > g > > > > On Aug 29, 1:18 pm, "j.blotus" wrote: > > > > i think you need to start again from the beginning of the manual. > > > > index() is controller action. It gets records from the Model and sends > > > > them to the view. It sounds like you don't really understand the way > > > > CakePHP uses MVC. Also, the core has an extensive API for versions > > > > 1.1, 1.2, and 1.3. > > > > > On Aug 28, 1:08 pm, geoB wrote: > > > > > > I am trying to get started with CakePHP and am experiencing some > > > > > frustration with the documentation. (fwiw, I am moderately well > > > > > experienced with PHP.) For example, I was following the blog tutorial > > > > > at the CakePHP website, only trying to adapt it to the database I > > > > > intend to work with. I learned that the index() function was > > > > > referring to an index of a table. So I started to look for the syntax > > > > > of the index() function to no avail. There does not appear to be a > > > > > function reference anywhere that I can find. > > > > > > In general, how does one learn the syntax of a specific function? I > > > > > hope it's not trial and error. Please point me in the right direction > > > > > for documentation resources. > > > > > > Thanks. > > > > > > George > > > > Check out the new CakePHP Questions sitehttp://cakeqs.organdhelp others > > > with their CakePHP related questions. > > > > You received this message because you are subscribed to the Google Groups > > > "CakePHP" group. > > > To post to this group, send email to cake-php@googlegroups.com > > > To unsubscribe from this group, send email to > > > cake-php+unsubscr...@googlegroups.com > > om>For more options, visit this group at > > >http://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Function documentation?
"When someone browsers to /controller/index, it calls the index() method for the controller, which usually contains a find call for the model associated with the controller and sets a variable which is available in the index view for the controller in question. " This is the kind of information I was looking for. I am more of a deductive than inductive logic person. The use of the method in the tutorial doesn't explain to me what it's doing there or how it is used. (I've not found any mention of an index() method in any controller. Why is that?) Thanks immensely for clearing this up. George On Aug 29, 7:01 pm, Greg Skerman wrote: > the index() method in your controllers wont have any parameters...or maybe > it will - its up to you. > > Hell you don't even have to define one if you don't want to. > > When someone browsers to /controller/index, it calls the index() method for > the controller, which usually contains a find call for the model associated > with the controller and sets a variable which is available in the index view > for the controller in question. > > Take a look at the blog tutorial in the book - it'll show you exactly how > this works. > > On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > > I have searched Google, CakePHP Google Group, API Controller > > documentation (versions 1.2, 1.3), API AppController documentation > > (versions 1.2, 1.3) and have found no useful information on the > > parameters used by the index method. Search terms include "index > > method", "index method" & documentation, "Index method" & syntax. I > > ain't no dummy, and I don't expect to be spoon-fed. > > > Sure, my understanding isn't what it could be. That's why I read the > > documentation. But reading alone does not create comprehension. > > Actual use of the material to observe its effects is required as > > well. But I can't try to recreate something I cannot find > > documentation on. > > > Perhaps a more specific reference would be useful. I have read the > > manual at least twice now, and I know I'm not ready for the exam. > > > g > > > On Aug 29, 1:18 pm, "j.blotus" wrote: > > > i think you need to start again from the beginning of the manual. > > > index() is controller action. It gets records from the Model and sends > > > them to the view. It sounds like you don't really understand the way > > > CakePHP uses MVC. Also, the core has an extensive API for versions > > > 1.1, 1.2, and 1.3. > > > > On Aug 28, 1:08 pm, geoB wrote: > > > > > I am trying to get started with CakePHP and am experiencing some > > > > frustration with the documentation. (fwiw, I am moderately well > > > > experienced with PHP.) For example, I was following the blog tutorial > > > > at the CakePHP website, only trying to adapt it to the database I > > > > intend to work with. I learned that the index() function was > > > > referring to an index of a table. So I started to look for the syntax > > > > of the index() function to no avail. There does not appear to be a > > > > function reference anywhere that I can find. > > > > > In general, how does one learn the syntax of a specific function? I > > > > hope it's not trial and error. Please point me in the right direction > > > > for documentation resources. > > > > > Thanks. > > > > > George > > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others > > with their CakePHP related questions. > > > You received this message because you are subscribed to the Google Groups > > "CakePHP" group. > > To post to this group, send email to cake-php@googlegroups.com > > To unsubscribe from this group, send email to > > cake-php+unsubscr...@googlegroups.comFor > > more options, visit this group at > >http://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Function documentation?
the index() method in your controllers wont have any parameters...or maybe it will - its up to you. Hell you don't even have to define one if you don't want to. When someone browsers to /controller/index, it calls the index() method for the controller, which usually contains a find call for the model associated with the controller and sets a variable which is available in the index view for the controller in question. Take a look at the blog tutorial in the book - it'll show you exactly how this works. On Mon, Aug 30, 2010 at 10:57 AM, geoB wrote: > I have searched Google, CakePHP Google Group, API Controller > documentation (versions 1.2, 1.3), API AppController documentation > (versions 1.2, 1.3) and have found no useful information on the > parameters used by the index method. Search terms include "index > method", "index method" & documentation, "Index method" & syntax. I > ain't no dummy, and I don't expect to be spoon-fed. > > Sure, my understanding isn't what it could be. That's why I read the > documentation. But reading alone does not create comprehension. > Actual use of the material to observe its effects is required as > well. But I can't try to recreate something I cannot find > documentation on. > > Perhaps a more specific reference would be useful. I have read the > manual at least twice now, and I know I'm not ready for the exam. > > g > > On Aug 29, 1:18 pm, "j.blotus" wrote: > > i think you need to start again from the beginning of the manual. > > index() is controller action. It gets records from the Model and sends > > them to the view. It sounds like you don't really understand the way > > CakePHP uses MVC. Also, the core has an extensive API for versions > > 1.1, 1.2, and 1.3. > > > > On Aug 28, 1:08 pm, geoB wrote: > > > > > I am trying to get started with CakePHP and am experiencing some > > > frustration with the documentation. (fwiw, I am moderately well > > > experienced with PHP.) For example, I was following the blog tutorial > > > at the CakePHP website, only trying to adapt it to the database I > > > intend to work with. I learned that the index() function was > > > referring to an index of a table. So I started to look for the syntax > > > of the index() function to no avail. There does not appear to be a > > > function reference anywhere that I can find. > > > > > In general, how does one learn the syntax of a specific function? I > > > hope it's not trial and error. Please point me in the right direction > > > for documentation resources. > > > > > Thanks. > > > > > George > > Check out the new CakePHP Questions site http://cakeqs.org and help others > with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.comFor > more options, visit this group at > http://groups.google.com/group/cake-php?hl=en > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Function documentation?
I have searched Google, CakePHP Google Group, API Controller documentation (versions 1.2, 1.3), API AppController documentation (versions 1.2, 1.3) and have found no useful information on the parameters used by the index method. Search terms include "index method", "index method" & documentation, "Index method" & syntax. I ain't no dummy, and I don't expect to be spoon-fed. Sure, my understanding isn't what it could be. That's why I read the documentation. But reading alone does not create comprehension. Actual use of the material to observe its effects is required as well. But I can't try to recreate something I cannot find documentation on. Perhaps a more specific reference would be useful. I have read the manual at least twice now, and I know I'm not ready for the exam. g On Aug 29, 1:18 pm, "j.blotus" wrote: > i think you need to start again from the beginning of the manual. > index() is controller action. It gets records from the Model and sends > them to the view. It sounds like you don't really understand the way > CakePHP uses MVC. Also, the core has an extensive API for versions > 1.1, 1.2, and 1.3. > > On Aug 28, 1:08 pm, geoB wrote: > > > I am trying to get started with CakePHP and am experiencing some > > frustration with the documentation. (fwiw, I am moderately well > > experienced with PHP.) For example, I was following the blog tutorial > > at the CakePHP website, only trying to adapt it to the database I > > intend to work with. I learned that the index() function was > > referring to an index of a table. So I started to look for the syntax > > of the index() function to no avail. There does not appear to be a > > function reference anywhere that I can find. > > > In general, how does one learn the syntax of a specific function? I > > hope it's not trial and error. Please point me in the right direction > > for documentation resources. > > > Thanks. > > > George Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Function documentation?
i think you need to start again from the beginning of the manual. index() is controller action. It gets records from the Model and sends them to the view. It sounds like you don't really understand the way CakePHP uses MVC. Also, the core has an extensive API for versions 1.1, 1.2, and 1.3. On Aug 28, 1:08 pm, geoB wrote: > I am trying to get started with CakePHP and am experiencing some > frustration with the documentation. (fwiw, I am moderately well > experienced with PHP.) For example, I was following the blog tutorial > at the CakePHP website, only trying to adapt it to the database I > intend to work with. I learned that the index() function was > referring to an index of a table. So I started to look for the syntax > of the index() function to no avail. There does not appear to be a > function reference anywhere that I can find. > > In general, how does one learn the syntax of a specific function? I > hope it's not trial and error. Please point me in the right direction > for documentation resources. > > Thanks. > > George Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Function documentation?
I am trying to get started with CakePHP and am experiencing some frustration with the documentation. (fwiw, I am moderately well experienced with PHP.) For example, I was following the blog tutorial at the CakePHP website, only trying to adapt it to the database I intend to work with. I learned that the index() function was referring to an index of a table. So I started to look for the syntax of the index() function to no avail. There does not appear to be a function reference anywhere that I can find. In general, how does one learn the syntax of a specific function? I hope it's not trial and error. Please point me in the right direction for documentation resources. Thanks. George Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Online Documentation
Why not just generate your own on the fly so it is always up to date? paste this link: http://groups.google.com/group/cake-php/web/faq and follow the instructions. On Aug 25, 10:39 am, Okto Silaban wrote: > You can get it here :http://www.doocu.com/pdf/view/17590 > It's not perfect, but at least you get the offline version.. > > *Doocu.com is build with CakePHP too.. :P > > On Wed, Aug 25, 2010 at 8:12 AM, Michael Gaiser wrote: > > Hey guys, I know that Cake has a great online set of documentation, but the > > only time I really have to work on my project is on the train which > > unfortunately does not have internet access. Is there a copy of the online > > docs anywhere or do you know of a program that can crawl the > > cakephp.orgsite and download a local copy of the docs? Thanks in advance Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Online Documentation
You can get it here : http://www.doocu.com/pdf/view/17590 It's not perfect, but at least you get the offline version.. *Doocu.com is build with CakePHP too.. :P On Wed, Aug 25, 2010 at 8:12 AM, Michael Gaiser wrote: > Hey guys, I know that Cake has a great online set of documentation, but the > only time I really have to work on my project is on the train which > unfortunately does not have internet access. Is there a copy of the online > docs anywhere or do you know of a program that can crawl the cakephp.orgsite > and download a local copy of the docs? Thanks in advance > > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Online Documentation
Hey guys, I know that Cake has a great online set of documentation, but the only time I really have to work on my project is on the train which unfortunately does not have internet access. Is there a copy of the online docs anywhere or do you know of a program that can crawl the cakephp.orgsite and download a local copy of the docs? Thanks in advance. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Documentation builder
I wish you a nice day, please, according to http://book.cakephp.org/ I'm lookin for ready project "Documentation builder" I wannt to ask you , is there any ready project, which was used to make Documentation on URL upper? It's nice example of what i want, project to make documentation in Tree-Like-System Like here 1 1.1 1.1.1 1.1.2 1.1.3 1.2 1.2.1 1.2.2 1.2.2.1 .. .. etc. Thanks beforehand for your reply Marek Sebera marek.seb...@gmail.com Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Offline Documentation Mirror
I have made a github repo of the files. When cloned into your web root and browsed to via localhost you will be able to see the docs. I think a chm version would be excellent. I agree that chm is much better than pdf. Im not sure if they are viewable on linux (never looked or thought about it) but im sure there is. A chm version build off what i pull would be good for those who also may not always have access to a web server to view the html files. Although any browser could see it. Any who its been a couple weeks since i created it and there have been some updates. so i will update it soon. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Offline Documentation Mirror
I'd offer to create a CHM or PDF version of the cookbook (I know it's always changing, but CHM/PDF are better formats for ebooks IMO), but the Cookbook is released under a no-derivatives CC license... On Apr 28, 6:32 pm, Graham Weldon wrote: > I think I have seen this request come up in the past. I can definitely see > how this would be useful to users that are offline frequently, and still > need to refer to documentation. > > I'll bring this up with the development and bakery teams, and see what the > best solution is to get something like this available. > Not making any promises at this stage, but a weekly automated export might > be possible. > > Cheers, > Graham Weldon (aka. Predominant) > > > > On Thu, Apr 29, 2010 at 3:11 AM, luckysmack wrote: > > While in irc at #cakephp i was talking to a few people that would like > > to have an offline version of the 1.3 documentation from > > book.cakephp.org . I was looking for the same thing as well, as I am > > frequently off line and would like to be able to refer to the docs. > > And viewing them on a phone can be done, but leaves much to be > > desired. Anywho, so last night i tested out pulling the documentation > > from the site, making sure to keep bandwidth throttled and to only > > grab documentation. Adding filters to block the download of anything > > else. > > > So currently i would use this for personal use, but I would like to > > ask permission to host this offline documentation for others to see > > and be able to download for their own offline use as well. I would > > possibly add the files to a github repo for others to get. But before > > I do so I want to make sure that is ok with the top brass as so to > > stay on your good sides. :D > > > I would only update the documentation periodically and at night when > > it is off peak hours for the site as to not bog it down. And would > > most likely only do it every few weeks or so. So If you are ok with > > this please let me know. > > > Thanks > > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others > > with their CakePHP related questions. > > > You received this message because you are subscribed to the Google Groups > > "CakePHP" group. > > To post to this group, send email to cake-php@googlegroups.com > > To unsubscribe from this group, send email to > > cake-php+unsubscr...@googlegroups.comFor > > more options, visit this group at > >http://groups.google.com/group/cake-php?hl=en > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others with > their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group > athttp://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Offline Documentation Mirror
I think I have seen this request come up in the past. I can definitely see how this would be useful to users that are offline frequently, and still need to refer to documentation. I'll bring this up with the development and bakery teams, and see what the best solution is to get something like this available. Not making any promises at this stage, but a weekly automated export might be possible. Cheers, Graham Weldon (aka. Predominant) On Thu, Apr 29, 2010 at 3:11 AM, luckysmack wrote: > While in irc at #cakephp i was talking to a few people that would like > to have an offline version of the 1.3 documentation from > book.cakephp.org . I was looking for the same thing as well, as I am > frequently off line and would like to be able to refer to the docs. > And viewing them on a phone can be done, but leaves much to be > desired. Anywho, so last night i tested out pulling the documentation > from the site, making sure to keep bandwidth throttled and to only > grab documentation. Adding filters to block the download of anything > else. > > So currently i would use this for personal use, but I would like to > ask permission to host this offline documentation for others to see > and be able to download for their own offline use as well. I would > possibly add the files to a github repo for others to get. But before > I do so I want to make sure that is ok with the top brass as so to > stay on your good sides. :D > > I would only update the documentation periodically and at night when > it is off peak hours for the site as to not bog it down. And would > most likely only do it every few weeks or so. So If you are ok with > this please let me know. > > Thanks > > Check out the new CakePHP Questions site http://cakeqs.org and help others > with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.comFor > more options, visit this group at > http://groups.google.com/group/cake-php?hl=en > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Offline Documentation Mirror
While in irc at #cakephp i was talking to a few people that would like to have an offline version of the 1.3 documentation from book.cakephp.org . I was looking for the same thing as well, as I am frequently off line and would like to be able to refer to the docs. And viewing them on a phone can be done, but leaves much to be desired. Anywho, so last night i tested out pulling the documentation from the site, making sure to keep bandwidth throttled and to only grab documentation. Adding filters to block the download of anything else. So currently i would use this for personal use, but I would like to ask permission to host this offline documentation for others to see and be able to download for their own offline use as well. I would possibly add the files to a github repo for others to get. But before I do so I want to make sure that is ok with the top brass as so to stay on your good sides. :D I would only update the documentation periodically and at night when it is off peak hours for the site as to not bog it down. And would most likely only do it every few weeks or so. So If you are ok with this please let me know. Thanks Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
