OK, I see this in your FormHelper.php version #L44
use Cake\View\Helper\FormHelper as CakeFormHelper;
class FormHelper extends CakeFormHelper
So to answer my last question, it would appear that your FormHelper adds
the ability to inspect
the "novalidate" option.
Now I have to determine how to i
OK Mark !
I am into the Configuration documentation and looking at bootstrap.php
now. I will attempt to get this loaded by myself.
Can you answer two questions though ? ( guess that is really three :-) )
Should I focus on your #L44 version ?
If I get this working, does your FormHelper.php c
Never mind my solution then. It would need a little bit more knowledge of
how CakePHP works.
Even though it would exactly do what you want to.
Try to read the wiki documentation and study the plugin code more, that
might clarify it a bit.
But note that this is an extended FormHelper, not the cor
Hello Mark !
Thanks for this. At first glance I do not see any difference between the
#L16 and the #L44 version.
I have loaded the #L44 version as /src/View/Helper/FornHelper.php.
I do not know where to place
Configure::write('FormConfig.novalidate', 'true');
I'm a cakePHP novice. Can you giv
Lorne
you can actually set a config on the user side when using sth similar I did
in my plugin (since 2.x).
You can either use my Tools plugin directly, or copy and paste the relevant
part:
https://github.com/dereuromark/cakephp-tools/blob/cake3/src/View/Helper/FormHelper.php#L16
https://github.
Hello José
Thanks for the reference. If I interpret the manual properly, I think it
wants me to store the custom widget under the
/vendor/cakephp/cakephp/src/View/Widget/ directory structure ?
If this is correct then would the custom widget be wiped out every time I
did a "composer update"
Hi,
When I am sending mail from Cakephp to rediffmail. Then in body section
mailformat is also defined.
I have used Cakephp Email html format.
I have done following code:
$email = new CakeEmail('smtp');
$email->viewVars($vars);
$email->to($to);
$email->subject($subject);
$email->from(array('s
Ah, here we go sorry for the spam, it seems I was correct. under
Authentication it does state "By default the hash type set in Security
class will be used." Sorry if this caused any confusion, I was doubting
myself:
http://book.cakephp.org/2.0/en/core-libraries/components/authentication.html#hashin
In hindsight I may be wrong on that last comment, I think the salt is
actually for Security::hash rather than the Auth component, something I've
never thought about before, apologies.
On 9 January 2015 at 11:07, Stephen S wrote:
> Hey
>
> If you check out the comments above these configuration
Hey
If you check out the comments above these configuration values it should
explain what they are for.
When you use CakePHP's "Auth" component in your application, by default it
will use the Security.salt value when it is hashing passwords and the like,
it's a bad idea to keep this at the defaul
In cake 3 you can override the ButtonWidget and make that a default
property of your
buttons:
http://book.cakephp.org/3.0/en/views/helpers/form.html#adding-custom-widgets
You can just extend the one in the core (Cake\View\Widget\ButtonWidget) and
append your custom options.
On Friday, January
11 matches
Mail list logo
