Changeset 760410

Timestamp:

08/21/2013 10:07:10 PM (12 years ago)

Author:

Faison

Message:

Bug Fix: saving null for a Nav Menu Field doesn't save "null" anymore

Location:

advanced-custom-fields-nav-menu-field

Files:

• tags/1.1.2 (added)
• tags/1.1.2/fz-acf-nav-menu.php (added)
• tags/1.1.2/nav-menu-v4.php (added)
• tags/1.1.2/readme.txt (added)
• trunk/nav-menu-v4.php (modified) (2 diffs)
• trunk/readme.txt (modified) (2 diffs)

advanced-custom-fields-nav-menu-field/trunk/nav-menu-v4.php

@@ -104 +104 @@
             'name'      =>  'fields['.$key.'][container]',
             'value'     =>  $field['container'],
-            'layout'    =>  'horizontal',
             'choices'   =>  $choices
         ));
@@ -160 +159 @@
         if( $field['allow_null'] )
         {
-            echo '<option value="null"> - Select - </option>';
+            echo '<option value=""> - Select - </option>';
         }
 

advanced-custom-fields-nav-menu-field/trunk/readme.txt

@@ -6 +6 @@
 Requires at least: 3.4
 Tested up to: 3.5.1
-Stable tag: 1.1.1
+Stable tag: 1.1.2
 License: GPL2 or later
 License URI: http://www.gnu.org/licenses/gpl-2.0.html
@@ -79 +79 @@
 == Changelog ==
 
+= 1.1.2 =
+* Fixed a silly mistake related to allowing Null for a Nav Menu Field. Basically, it was storing the string "null" when you don't select a menu, that's taken care of now.
+
 = 1.1.1 =
 * I forgot to add a default value for the Menu Container field, so I added 'div' as the default value. If you upgraded from 1.0.0 to 1.1.0 and had WP_DEBUG enabled, you would receive a warning about an unknown index. Since I like debug mode to run without warnings, I fixed this.