Sorry, that one doesn’t help. But I think what is causing this. I’m using a custom avia.js in my child theme for a custom breakpoint of the theme. When I switch that off, the menu toggle is displayed correctly.

However, I do like to use the custom breakpoint. Hope you can help me out with this! I did one edit in the avia.js – and placed it in my child theme folder. At the responsive menu function on line number 88 I changed the switchWidth value from 767 to 989.

This modification is based on the following support thread: https://kriesi.at/support/topic/mobile-menu-tablet-breakpoint/.

Also – as mentioned in the thread – In the functions.php I’ve added:

// WZ: For custom breakpoint mobile menu toggle
// Make these Child functions load after Parent functions
add_action( 'after_setup_theme', 'childtheme_late_functions' );
function childtheme_late_functions() {
	// Swap out Parent's js/avia.js for Child's js/avia.js
	add_action( 'wp_enqueue_scripts', 'childtheme_menu_breakpoint' );
	function childtheme_menu_breakpoint() {
		wp_dequeue_script( 'avia-default' );
		wp_enqueue_script( 'childtheme-avia-js', get_stylesheet_directory_uri() . '/js/avia.js', array( 'jquery' ), 1, true);
	}
}

Let me know if you need more information.
Thanks!

Peter,

I tried to turn on the wp debug and this is what I found from the error_log.txt. Not sure if this has anything to do with the issue of not able to add custom social icons to the nav bar.

[07-Oct-2013 10:11:45 UTC] PHP Notice: Undefined index: qq in /home/content/30/11045530/html/z/wp-content/themes/acutta/config-templatebuilder/avia-template-builder/php/font-manager.class.php on line 622
[07-Oct-2013 10:11:45 UTC] PHP Notice: Undefined index: qq in /home/content/30/11045530/html/z/wp-content/themes/acutta/config-templatebuilder/avia-template-builder/php/font-manager.class.php on line 622
[07-Oct-2013 10:11:45 UTC] PHP Notice: Undefined index: sina-weibo in /home/content/30/11045530/html/z/wp-content/themes/acutta/config-templatebuilder/avia-template-builder/php/font-manager.class.php on line 622
[07-Oct-2013 10:11:45 UTC] PHP Notice: Undefined index: sina-weibo in /home/content/30/11045530/html/z/wp-content/themes/acutta/config-templatebuilder/avia-template-builder/php/font-manager.class.php on line 622

thanks,

Hi Ismael,

It is already in the woocommerce-core-functions.php file.

”
case ‘USD’ :
$currency_symbol = ‘$’;
break;
case ‘EUR’ :
$currency_symbol = ‘€’;
break;
case ‘CNY’ :
case ‘RMB’ :
case ‘JPY’ :
$currency_symbol = ‘¥’;
break;

”
As I mentioned in the previous posts, the Yuan shows correctly in iPad, Android tablet and from linux machines. but not from win 7 at least. I tried FF, IE and Chrome from win 7, all showed Japanese Yen instead of Chinese Yuan.

This is line 17 of my page.php file located in my child theme folder <div class='devin template-page content twelve units'>

That didn’t do anything. You can check my page source for http://thepluginfactory.co/warehouse/gard-pro/ and search for the word “devin” and you won’t find it. The page.php isn’t loading, I’ve even changed other code around, and that page didn’t use it.

I looked into code of the parent theme and found that you have a special function for dynamic stylesheet URL.
It is referenced around line 302 in enfold functions.php and line 748 of functions-enfold.php.
Can you provide a patch that will correct behaviour of serving dynamic stylesheet from /uploads/dynamic-avia/ folder over https?

http://snipt.org/Ahhff0

Here you go. I didn’t make any modifications in the functions.php before creating this thread, so the above snipt should be identical to what’s in the enfold theme package. The error went away when I added a “)” in the comment on line 26 of the attached snipt code.

After adding that extra “)”, I tried adding “add_theme_support(‘avia_template_builder_custom_css’);” to where you mentioned again, and then it gave me a new error about an unexpected ‘;’, this time in the comment in line 17.

What’s going on?

• This reply was modified 12 years, 6 months ago by bunguman.

Hi

Futher to this i have manged to get some output from Safari error logs (Firefox/Firebug crash out).

After insert into post is pressed, the following is returned:
avia_media.js:141RangeError: Maximum call stack size exceeded.

It would seem that there is a clash with AVIA and the cmb_metabox framework on
https://github.com/jaredatch/Custom-Metaboxes-and-Fields-for-WordPress

as if i disable the function to init the framework, the WP functionality then works to insert a post.

Part of the init.php function is to call the following

function cmb_scripts( $hook ) {
if ( $hook == ‘post.php’ OR $hook == ‘post-new.php’ OR $hook == ‘page-new.php’ OR $hook == ‘page.php’ ) {
wp_register_script( ‘cmb-scripts’, CMB_META_BOX_URL.’jquery.cmbScripts.js’, array( ‘jquery’,’media-upload’,’thickbox’ ) );
wp_enqueue_script( ‘jquery’ );
wp_enqueue_script( ‘jquery-ui-core’ ); // Make sure and use elements form the 1.7.3 UI – not 1.8.9
wp_enqueue_script( ‘media-upload’ );
wp_enqueue_script( ‘thickbox’ );
wp_enqueue_script( ‘cmb-scripts’ );
wp_enqueue_style( ‘thickbox’ );
wp_enqueue_style( ‘jquery-custom-ui’ );
add_action( ‘admin_head’, ‘cmb_styles_inline’ );
}
}

Could this be the source of the conflict do you think?

Many thanks for any guidance.

Phil.