title: CakePHP 2.3.1 deactivate form validation in certain views
body: <p>The Cookbook introduces for version 2.3 the possibility to deactivate the forced valiadation for forms. Or at least I understood it like that:
  Quote: from <a href="http://book.cakephp.org/2.0/en/core-libraries/helpers/form.html" rel="noreferrer">http://book.cakephp.org/2.0/en/core-libraries/helpers/form.html</a></p>
  
  <blockquote>
    <p>" New in version 2.3.</p>
    
    <p>Since 2.3 the HTML5 required attribute will also be added to the input
    based on validation rules. You can explicitly set required key in
    options array to override it for a field. To skip browser validation
    triggering for the whole form you can set option 'formnovalidate' =>
    true for the input button you generate using FormHelper::submit() or
    set 'novalidate' => true in options for FormHelper::create()."</p>
  </blockquote>
  
  <p>In my case I have a search from for this model and of course the user does not need to fill in all mandatory fields like for adding a dataset. So I want to deactivate the validation for my search form.</p>
  
  <p>I tried all three variations and see no results: Still the mandatory fields for create are mandatory in my search form.</p>
  
  <p>Those attempts I made:</p>
  
  <p>first try:</p>
  
  <pre><code>echo $this-&gt;Form-&gt;create('Partner', array('action' =&gt; 'search', 'novalidate' =&gt; true));
  </code></pre>
  
  <p>second try:</p>
  
  <pre><code>echo $this-&gt;Form-&gt;input('name', 
  array('required' =&gt; false, 'value' =&gt; $this-&gt;Session-&gt;read('Searchparameter.name'))
  );
  </code></pre>
  
  <p>third try:   </p>
  
  <pre><code> $this-&gt;Form-&gt;submit('Submit', array('formnovalidate' =&gt; true));
      echo $this-&gt;Form-&gt;end();
  </code></pre>
  
  <p>variation:</p>
  
  <pre><code>echo $this-&gt;Form-&gt;end(__('Submit'), array('formnovalidate' =&gt; true));
  </code></pre>
  
  <p>What did I understand wrong? btw: I did deactivate caching, so that should not be the problem.</p>
  
  <p>Of course I could still use the old workaround for this validation, but when 2.3 is offering this option, I would gladly use it.</p>
  
  <p>Calamity Jane</p>