Support Forum - Topic: Error on Mega Menu

Support Forum - Topic: Error on Mega Menu http://www.kriesi.at/support/topic/error-on-mega-menu Support Forum - Topic: Error on Mega Menu en-US Sat, 25 May 2013 13:01:51 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://www.kriesi.at/support/search.php Kriesi on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-105960 Wed, 17 Apr 2013 15:21:41 +0000 Kriesi 105960@http://www.kriesi.at/support/ <p>Hey! </p> <p> both fixes will be in the next updates, thanks for your help :) </p> <p> Regards,<br /> Kriesi </p> Devin on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-101512 Fri, 15 Mar 2013 17:31:38 +0000 Devin 101512@http://www.kriesi.at/support/ <p>Hi Tom,</p> <p>Yes, go ahead and make the same change if you'd like and of course turning off the error log for now. There are a number of bug fixes coming in the next update so this will be one of those.</p> <p>Regards,</p> <p>Devin </p> gsTom on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-101319 Thu, 14 Mar 2013 16:15:51 +0000 gsTom 101319@http://www.kriesi.at/support/ <p>Hi Dude,</p> <p>I suggest, the two solutions, one for me and one for seanjohnson are for the same issue.</p> <p>commenting //error_log... does of course avoid crowding my error-log-file.<br /> in debug the originating error still comes up, however, I will not go productive with debug mode on, just want to be sure, that I can go live with it as is, or should I also do the second change in helper-responsive-megamenu.php before?</p> <p>Thanks<br /> Tom</p> <p>PS: so far, my WP351, replete 131, woo 203 seems to be quite ok now - I only experience poor backend performance since upgrades for now! </p> Dude on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-101269 Thu, 14 Mar 2013 11:33:26 +0000 Dude 101269@http://www.kriesi.at/support/ <p>@seanjohnson please deactivate the debug mode (you need to edit wp-config.php: <a href="http://codex.wordpress.org/Editing_wp-config.php#Debug" rel="nofollow">http://codex.wordpress.org/Editing_wp-config.php#Debug</a> ). We'll fix the php warning/notice with the next theme update however it's not a good idea to turn on the debug mode on production systems.</p> <p>If you want to fix the error yourself please open up wp-content\themes\replete\includes\helper-responsive-megamenu.php and replace:</p> <pre><code>$output = str_replace("{current_row_".$row."}", "avia_mega_menu_columns_".$columns." ".$this->grid_array[1].$last, $output);</code></pre> <p>with:</p> <pre><code>$output = str_replace("{current_row_".$row."}", "avia_mega_menu_columns_".$columns." ".$this->grid_array[1], $output);</code></pre> Dude on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-101268 Thu, 14 Mar 2013 11:30:34 +0000 Dude 101268@http://www.kriesi.at/support/ <p>Try following - open up wp-content\themes\replete\includes\admin\register-dynamic-styles.php and replace following code:</p> <pre><code>error_log(print_r($avia_config['backend_colors'], true));</code></pre> <p>with:</p> <pre><code>//error_log(print_r($avia_config['backend_colors'], true));</code></pre> gsTom on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-101105 Wed, 13 Mar 2013 14:09:45 +0000 gsTom 101105@http://www.kriesi.at/support/ <p>No, no impact on functionality and no error displayed with debug off.<br /> Was just wondering about that.<br /> However, I configured to write an phperrorlog and I find huge numbers of this one there, which looks like coming from replete, but there are no further hints why it is in error log:</p> <p>[13-Mar-2013 13:57:52 UTC] Array<br /> (<br /> [color_set] => Array<br /> (<br /> [header_color] => Array<br /> (<br /> [bg] => #ffffff<br /> [bg2] => #f8f8f8<br /> [primary] => #333333<br /> [secondary] => #444444<br /> [color] => #333333<br /> [border] => #e1e1e1<br /> [heading] => #000000<br /> [meta] => #808080<br /> )</p> <p> [slideshow_color] => Array<br /> (<br /> [bg] => #041424<br /> [bg2] => #0c1d2e<br /> [primary] => #2d5c88<br /> [secondary] => #3d71a1<br /> [color] => #ffffff<br /> [border] => #ebebeb<br /> [heading] => #ffffff<br /> [meta] => #828A92<br /> )</p> <p> [main_color] => Array<br /> (<br /> [bg] => #f8f8f8<br /> [bg2] => #ffffff<br /> [primary] => #2d5c88<br /> [secondary] => #3d71a1<br /> [color] => #666666<br /> [border] => #e1e1e1<br /> [heading] => #222222<br /> [meta] => #8D8D8D<br /> )</p> <p> [alternate_color] => Array<br /> (<br /> [bg] => #ffffff<br /> [bg2] => #f8f8f8<br /> [primary] => #2d5c88<br /> [secondary] => #3d71a1<br /> [color] => #666666<br /> [border] => #e1e1e1<br /> [heading] => #222222<br /> [meta] => #919191<br /> )</p> <p> [footer_color] => Array<br /> (<br /> [bg] => #041424<br /> [bg2] => #222222<br /> [primary] => #2d5c88<br /> [secondary] => #e4e7eb<br /> [color] => #e4e7eb<br /> [border] => #0a2138<br /> [heading] => #f8fbff<br /> [meta] => #7E8892<br /> )</p> <p> [socket_color] => Array<br /> (<br /> [bg] => #02080f<br /> [bg2] => #000000<br /> [primary] => #ffffff<br /> [secondary] => #eeeeee<br /> [color] => #eeeeee<br /> [border] => #0a2138<br /> [heading] => #ffffff<br /> [meta] => #818487<br /> )</p> <p> )</p> <p> [style] => Array<br /> (<br /> [body_style] => stretched<br /> [body_color] => #041424<br /> [body_fontcolor] => #ffffff<br /> [body_img] =><br /> [body_customimage] =><br /> [body_pos] => top center<br /> [body_repeat] => repeat<br /> [body_attach] => scroll<br /> [body_background] => #041424 top center repeat scroll<br /> )</p> <p>)</p> <p>any idea?<br /> I'm running on all new versions WP351, replete 131, woo 203</p> <p>Danke<br /> Tom </p> Devin on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-100680 Mon, 11 Mar 2013 18:56:32 +0000 Devin 100680@http://www.kriesi.at/support/ <p>Hi gsTom,</p> <p>Are you getting the error when not debugging? Is the actual functionality impaired at all?</p> <p>Regards,</p> <p>Devin </p> gsTom on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-100561 Mon, 11 Mar 2013 11:00:02 +0000 gsTom 100561@http://www.kriesi.at/support/ <p>Hi,</p> <p>I got the same when in wp_debug<br /> replete 1.3.1<br /> woo 2.0.2<br /> wp 3.5.1 </p> Devin on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-93931 Tue, 29 Jan 2013 15:16:37 +0000 Devin 93931@http://www.kriesi.at/support/ <p>Hey seanjohnson,</p> <p>First try disabling any active plugins you have running (except for WooCommerce). See if that removes the error from happening.</p> <p>Also, can you tell us the version of Replete, Wordpress and WooCommerce you are using ?</p> <p>Regards,</p> <p>Devin </p> seanjohnson on "Error on Mega Menu" http://www.kriesi.at/support/topic/error-on-mega-menu#post-93711 Mon, 28 Jan 2013 13:41:02 +0000 seanjohnson 93711@http://www.kriesi.at/support/ <p>Menu work ok, but when I add items as sub-menu items for a mega menu it displays this error on the front end, right before the menu:</p> <p>Notice: Undefined variable: last in /var/www/ <my path> /wp-content/themes/replete/includes/helper-responsive-megamenu.php on line 109</p> <p>Line 109 is:</p> <p><code>$output = str_replace("{current_row_".$row."}", "avia_mega_menu_columns_".$columns." ".$this->grid_array[1].$last, $output);</code> </p>