HTML bug in Customize > Navigation - Support | Kriesi.at

Viewing 8 posts - 1 through 8 (of 8 total)

Author

Posts
June 8, 2014 at 8:40 am #276165

amazeingart
Participant

Hey one bug it looks like I found… tried to find a bug report thread but couldn’t, so here it is.

Under Appearance > Customize > Navigation some HTML tags are coming through in the theme’s own interface, where they shouldn’t be. At least in a child theme. Probably some other tag wasn’t closed properly. It reads like this, with the select element after each indicated by [selector]. All the select elements worked.

Here is how it reads:

Your theme supports 3 menus. Select which menu appears in each location. You can edit your menu content on the Menus screen in the Appearance section.
Enfold Child Main Menu
[selector]
Enfold Child Secondary Menu (Will be displayed if you selected a header layout that supports a submenu here)
[selector]
Enfold Child Footer Menu (no dropdowns)
[selector]

June 8, 2014 at 1:27 pm #276181

Ismael
Moderator

Hey Chris!

Thank you for your visiting the support forum!

It doesn’t seem to be happening on our end when I check one of our installation with a child theme. Do you have the latest version of Enfold?

Best regards,
Ismael

June 8, 2014 at 8:05 pm #276266

amazeingart
Participant

I just downloaded and installed it yesterday, looks like the latest version, it is:
2014 May 28th – Version 2.8.1

The HTML tags bleeding through in the interface occurs in the parent theme interface too, I just switched the site over to enfold parent and checked. The problem occurs in all browsers. If you like I can include a screenshot, I’d have to upload it to one of my websites for you I think, to link it here in the forum.

Just in case it matters, the child theme was created by following the directions in the video you guys have for Enfold Child Theme.

Both were uploaded via FTP to the themes directory, and they both seem to work in all other respects. The dummy data gets imported, the template site exists and works for visitors in both child and parent. Just this WP interface bug makes me nervous to begin the week+ of customization work I have for the child theme. What if something else (that actually matters) is mixed up in the theme installation too?

Should I maybe delete and reinstall everything?

June 8, 2014 at 8:25 pm #276267

amazeingart
Participant

Here is the screenshot. I’m on Bluehost too if that matters. I think I will delete and reinstall both parent and child, then just install parent and see if it happens again. Hopefully its just a corrupted glitch.

June 8, 2014 at 8:59 pm #276272

amazeingart
Participant

Hmm yes the problem still happens in the Enfold parent theme interface, with a new install of the theme. All the data for the site is just the dummy data, except for one new page I created (an under construction frontpage).

Maybe the WP database got corrupted? That shouldn’t affect the admin interface though right? Should I delete my SQL database for the site, or remove and reinstall the entire WP install for this hosting account (Bluehost managed WP).

Thanks for any thoughts you might have (and the actual real support you guys give on this forum, its great).

Chris

June 9, 2014 at 12:01 am #276298
amazeingart
Participant
Well, the interface problem (in both parent and child theme) still occurs after completely wiping my entire WP install and database, and then re-installing everything and uploading a fresh Enfold theme.

There may be something off about the following code, likely in the  part that the theme interface is delivering… this code seems to be causing the issue in all my browsers.
```
<li id="customize-control-nav_menu_locations-avia2" class="customize-control customize-control-select">
 <label>
 Enfold Child: Amazeing Art Secondary Menu (Will be displayed if you selected a
 header layout that supports a submenu <a target="_blank" href="http://198.1.78.233/wp-admin
 /?page=avia#goto_header_layout">here</a>)
 
 <select data-customize-setting-link="nav_menu_locations[avia2]">
 <option value="0">— Select —</option>
 <option value="27">Main Menu</option>
 </select>
 </label>
</li>
```
June 9, 2014 at 12:07 pm #276413
Dude
Participant
Hi!

Thank you for the bug report. We’ll fix it with the next update. If you need a quick fix open up enfold/functions.php and replace:
```
/*
 * Activate native wordpress navigation menu and register a menu location
 */
if(!function_exists('avia_nav_menus'))
{
	function avia_nav_menus()
	{
		global $avia_config;

		add_theme_support('nav_menus');
		foreach($avia_config['nav_menus'] as $key => $value){ register_nav_menu($key, THEMENAME.' '.$value); }
	}

	$avia_config['nav_menus'] = array(	'avia' => 'Main Menu' ,
										'avia2' => 'Secondary Menu (Will be displayed if you selected a header layout that supports a submenu <a target="_blank" href="'.admin_url('?page=avia#goto_header_layout').'">here</a>)',
										'avia3' => 'Footer Menu (no dropdowns)'
									);
	avia_nav_menus(); //call the function immediatly to activate
}
```
with
```
/*
 * Activate native wordpress navigation menu and register a menu location
 */
if(!function_exists('avia_nav_menus'))
{
	function avia_nav_menus()
	{
		global $avia_config, $wp_customize;

		add_theme_support('nav_menus');
		
		foreach($avia_config['nav_menus'] as $key => $value)
		{
			//wp-admin\customize.php does not support html code in the menu description - thus we need to strip it
			$name = (!empty($value['plain']) && !empty($wp_customize)) ? $value['plain'] : $value['html'];
			register_nav_menu($key, THEMENAME.' '.$name);
		}
	}

	$avia_config['nav_menus'] = array(	'avia' => array('html' => __('Main Menu', 'avia_framework')),
										'avia2' => array(
													'html' => __('Secondary Menu (Will be displayed if you selected a header layout that supports a submenu <a target="_blank" href="'.admin_url('?page=avia#goto_header_layout').'">here</a>)', 'avia_framework'),
													'plain' => __('Secondary Menu - will be displayed if you selected a header layout that supports a submenu', 'avia_framework')),
										'avia3' => array(
													'html' => __('Footer Menu (no dropdowns)', 'avia_framework'),
													'plain' => __('Secondary Menu (no dropdowns)', 'avia_framework'))
									);

	avia_nav_menus(); //call the function immediatly to activate
}
```
Cheers!
Peter
June 9, 2014 at 7:58 pm #276579

amazeingart
Participant

Excellent, thanks to you both. Great support here! So glad I went with a Kriesi theme again.
Chris
Author

Posts

Viewing 8 posts - 1 through 8 (of 8 total)

The topic ‘HTML bug in Customize > Navigation’ is closed to new replies.