Search Results for 'composer'

Hello folks.

I’m also having issues with trying to save theme settings. I’m using the latest version of both WordPress and Newsmag themes. I’ve disabled all plug-ins except for Wordfence, WPBakery Visual Composer,Ultimate Addons for Visual Composer, tagDiv Visual Composer Shim and tagDiv Speed Booster.

When in the theme settings page in the admin panel, I’m able to modify most of the settings without any issue. However, when I try to click on the Block predefined style section links to modify them, the ajax spinning icon just hangs and doesn’t pop open the menu. When I pull open the dev console in Chrome, I noticed this:

Uncaught SyntaxError: Unexpected token < admin.php:1

Things that I’ve tried:

Cleared both the server cache and the browser cache.

I’ve spoken with my host, HostGator and asked them to check the admin-ajax.php and confirm that it wasn’t being blocked, which they said it wasn’t. They also stated that the maximum memory limit is already set to 256, and cannot be changed by the end-user on a shared hosting account.

Reference: http://support.hostgator.com/articles/cpanel/php-settings-that-cannot-be-changed

memory_limit = 256M (MAXIMUM)

Per Chris’s link above, I also went into the wp-config.php file and added the following line of code:

/** Increased memory allotment to prevent Ajax Errors. https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP */
define( 'WP_MAX_MEMORY_LIMIT', '256M' );

(The official WordPress.org article Chris showed said you had to add it in prior to settings.)

Please note, this has to be put before wp-settings.php inclusion.

You can see it in-line where I included it right after the absolute path section, and before the wp-settings.php section, here:

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Increased memory allotment to prevent Ajax Errors. https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP */
define( 'WP_MAX_MEMORY_LIMIT', '256M' );

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

Perhaps this is related, but when I’m on the front end, and try to use the left and right arrows to scroll through content in the various section blocks, the ajax loading icon just spins, and the console spits out the following error:

SyntaxError: Unexpected token < madlymanly.com/:1

Any thoughts as to what is causing the syntax error message in the console? Thank you in advance for the help!

• This reply was modified 11 years by MrChill.
• This reply was modified 11 years by MrChill.

Chris, thanks for the response.

This is what the hosting company told me about the issue – please bear with me since I’m not very accustomed to such issues.

I have checked the logs of rcdronearena.com and found the following error messages:-
------
[Thu Jun 04 15:39:39 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/admin.php?page=td_theme_panel
[Thu Jun 04 15:40:01 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/admin.php?page=td_theme_panel
[Thu Jun 04 15:40:14 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/themes.php
[Thu Jun 04 15:40:43 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/admin.php?page=td_theme_panel
[Thu Jun 04 15:41:18 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/themes.php
------

Please note that, the long_query_time set for the MySQL service is 15 seconds.
Since it is a shared server, we can't alter this values for single domain. We have set this limit carefully to avoid any wastage/abuse of server resources and increasing the limit will result in degradation of server's performance.

Do you think I need an older version of Visual Composer?

Thanks once again.

Error 503 is server overload, as you likely know.
Check your server error logs to see WHAT is causing it to die.

If it’s the issue with the CPU spikes, then you might have to request the older version of Visual Composer, due to a semi-rare issue with some web servers.

See: https://forum.tagdiv.com/topic/newsmag-1-7-1-killed-our-server-again/

Make sure you disable ALL your other plugins EXCEPT for Visual Composer as starting point!

Upon closer inspection it appears to be the ‘enqueueStyle’ function starting at line 540 in class-vc-base.php in plugins/js_composer/include/classes/core.

If I comment out the line ‘wp_enqueue_style( ‘js_composer_front’ );’ the error goes away.


/**
* Enqueue base css class for VC elements and enqueue custom css if exists.
*/
public function enqueueStyle() {
$post = get_post();
if ( $post && preg_match( '/vc_row/', $post->post_content ) ) {
wp_enqueue_style( 'js_composer_front' );
}
wp_enqueue_style( 'js_composer_custom_css' );
}


Damn, meant to say, for those thinking this might be an issue with NewsMag or Newspaper, that the issues with Visual Composer being discussed in this thread are not unique to tagDiv themes. I’m also using A-Bomb by 007Theme, aka Ridwan Reedwan, which uses VC 4.4.4 and is very similar to NewsMag/Newspaper, and experiencing the same kind of load issues. Not as bad as NewsMag 1.7 was for me on the same site, but tagDiv integrates VC with a lot more features than the A-Bomb theme does, so it makes sense that it drains a bit more.

That is probably a widget … so you have to add it to a ‘widget area’ or shortcode for that plugin.

So either create a widget area first, or add to a custom sidebar for home page (like I do for the weather widget). You add widgets to sidebars in appearance > widgets.

The plugin doesn’t add a Visual Composer “element.”

https://wordpress.org/plugins/wp-polls/installation/

• This reply was modified 11 years by simchris.

Marius/Radu..
going to post this here since relevant to the SHIM users and also those who follow my thread on optimizations … somebody brought up good point I had forgotten about …. any ideas for updating this functions.php element to remove the SHIM css from the post pages … this code you provided for the VC plugin obviously doesn’t work for the SHIM; and I have hunch we might have to put something into one of the booster files also?

——–old code you created to hide VC css from post pages — does not hide SHIM css on post pages————snip:

add_action('init', 'myoverride', 100);
function myoverride() {
remove_action('wp_head', array(visual_composer(), 'addMetaData'));
}

function dequeue_visual_composer_css() {
if (is_single()) {
wp_dequeue_style('js_composer_front');
}
}
add_action('wp_enqueue_scripts', 'dequeue_visual_composer_css', 1003);

———-/snip

thank you kindly 🙂

• This reply was modified 11 years by simchris.

Absolutely true. Everything “weird” started with 4.4 and when they started adding a bunch of new things for WooCommerce and adding some things which I think were designed to roll-in things others were selling as extensions/add-ons to VC.

So, for low traffic site, VC 4.42 and Newsmag 1.71 work fine. High traffic site and VC 4.5x .. not so much.

With VC 4.3.5 we never had *any* problems. Newsmag 1.71 good to update to for the WP security fixes, and then try to either use shim, or older version of VC.

AGAIN TO ANY AND ALL: issue *not* with the theme — it’s nothing TagDiv ‘needs to fix’ with new theme version. It’s an issue with Visual Composer from WP Bakery, bundled with theme to provide dashboard and additional widgets for custom layouts. Issue doesn’t impact ALL sites/servers. Oddly it seems worse with those of use with dedicated servers, but really weird things happen. Only real solution — I think — is for VC to fully re-write their code from ground up based on current version of WP, optimize it, and possibly break some things into extensions that most people don’t use. Why have all the code bloat for WooCommerce if not using that on a magazine site?

Anyway…. just my input on this topic since I was one affected. I don’t speak for TagDiv in any way… just my opinions.

Hi Alin:

thanks, I did diable all plugins except visual composer. Now, still the icon not show on mobile phone but the canvas menu now working.

I think the menu not wokring related to W3 cache but still why the icon not showing?

Thanks

Well, they kind of already have … on various threads.

Right now the *only* solution with Newsmag if you have this CPU spiral of doom is to use the shim plugin, and use VC as little as possible beyond the development portion of your home page. Make sure you have a lot of memory allocated to WordPress (at least 256MB from the wp-config.php file in addition to php.ini setting; you must do both!).

We started to see minor spikes once 4.4.2 came out. Prior to that zero issues. Right now we can use it, but anything later not so good. I can’t imagine if WP Bakery haven’t addressed this ins the 4.5x versions, that they still don’t “get it” and are not solving it — seems to be a “if 90% of people can use, the other 10% oh well …” which isn’t great.

Right now TagDiv is focused on (based on posts I’ve seen):
a) Newspaper 5 w/ features of Newsmag + better grid + new version of API.
b) Next Shim beta for use with Newsmag *and* Newspaper.
c) Newsmag 1.8 with bug fixes and minor updates/tweaks.
d) Dev work on possible alternative to using Visual Composer.

So — at the moment if your site dies with VC 4.42 immediately, then it’s clear you might need to go back one more iteration, and/or stick with 1.6 of Newsmag vs 1.71.

I have 2 sites still working with 1.6 and 4.42 without shim, and doing okay, but they are fairly low traffic sites. I have 3 sites on 1.71 with VC442 and the shim, and 2 of these are our larger main traffic sites which were killing MySQL in batches of every 10 minutes or so going from green to yellow to red, and back. Then CPU death.

Not sure any of that helps … not much TagDiv can do beyond the shim, and possibly providing earlier versions of VC to try for your system. Since they don’t develop VC, it’s not something they can “fix” for anybody beyond the reports they have provided to the Bakery folks as a developer/licensor in hopes of solution (and yet to see one).

Some theme devs are already leaving VC in favor of in house solutions or simpler things like Siteorigin builder (free/open source), etc. (( We’re using Page Builder by SiteOrigin with a lean WP home brew Bootstrap 3 theme for a client reporting system along with Advanced Custom Fields, and works well so far for that … )).

Anyway…. I’m sure TagDiv folk will have some reply, but likely not far different from the above rantings 🙂

Of course, it’s possible that the next version of Visual Composer will be better “optimized” …. frankly, I’m amazed they are not working with an example “DOA” server setup, reading the error logs, and trying to find what bit of code is causing the death spiral, and then FIXING it. But I’m behind on stuff for my own business, so can’t really point fingers on that 😉