Visual Composer 4.4.3 not working on 1.7

Hi.

I updated yesterday to 1.7 (with the second version, and also updated VC and TagDiv components). After the update the Visual Composer works when rendering, but when I want to edit the front page the Visual composer just shows the loading symbol, <*> but dont let me design anything.

Any ideas

It’s the * load sign that just rotates all the time.

4.4.3 with 1.7 is working on my site.

Just built new home page.

You might TRY deleting the old js_composer entirely
uploading new version via FTP.

Use Chrome and not I.E. (if doing so). Clear all caches first.

Try going to your page, then click “save” (update) right side.
Then try adding new item.

Seems to work okay … but VC is a very persnickety plugin, it seems!

I offcause did all that before creating a support ticket.

Tried it in three different browsers, and even restored a snapshot of my server to confirm it was not an error raised before upgrading to 1.7

Still no luck

Uncaught TypeError: undefined is not a functioncomposer-storage.js?ver=4.4.3:331 vc.Storage.fetchcomposer-storage.js?ver=4.4.3:100 vc.Storage.findAllcomposer-models.js?ver=4.4.3:142 vc.shortcodes_collection.Backbone.Collection.extend.syncload-scripts.php?c=1&load[]=jquery-ui-resizable,jquery-ui-button,jquery-ui-dialog,wpdialogs,hoverIn…:392 c.extend.fetchcomposer-view.js?ver=4.4.3:666

Here’s the debug info.

I think that is the issue with code used which does not work with ooooold versions of php on some servers.

For now roll back to older version and wait for 1.71 update of theme.

Chris. i’m running latest php version from feb. 2015 on Nginx.

/Jens

Hm. Weird. I sit corrected. I wonder if new version has some issue with Nginx …
presumably you already updated your php.ini file to increase memory, upload size and execution time from the often insufficient defaults. That was my issue with VC initially.

Probably best to roll back to prior version of VC and see if that works?

4.4.2 has the same problem with 1.7. I will consider downgrading NewsMag again.

Since I didn’t have this problem with 1.6.

So bizarre that some systems have issues, others don’t.
However I do recall going through this kind of thing with other themes over the years — where 90% of people had no trouble and for us every update broke their stupid custom “framework” which had to be updated separately. About five differnet big WP foundries just could not be consistent. Ended up just using Woo Canvas for everything for several years out of annoyance. “So far” we’ve been lucky with TagDiv as I think we are running the same kind of system they use for their demo site, testing — so, in our case we’ve not had all the wonky issues 10% of the userbase have seen. Sucks for those suffering these things. Totally been there.

Virtual hugs all around. 🙂

Is it possible to download 1.6 anywhere, so I can test if its the theme.

I’ve tried everything else.

I have downgraded PHP – Not working
I have upgraded PHP – Not working
I have downgraded VC to 4.4.2 – Not working

I have disabled every plugin except – VC and TAGDIV things – Not working

I don’t think so …
obviously if you kept the files from your last install, that’s always best.

I think they can send to you if you email contact@tagdiv.com

I have the same problem, using Visual Composer 4.3.5 with Newsmag 1.7 and I can’t edit Homepage anymore. Recent versions of VC are problematic too, they increase server CPU usage too much. Thankfully tagdiv staff sent me VC 4.3.5 and it worked very well until Newsmag 1.7.

Now even if I return to Newsmag 1.6 or 1.5, VC doesn’t show up in editing pages anymore. I have tried deleting it and reinstalling it. Visual Composer works with WP default 2015 theme but now with Newsmag anymore.

Any idea about this? It renders homepage but can’t edit anymore, same problem with the thread.

Hi,

i also have an issue with VC 4.4.3 and NewsMag 1.7. What i found is that when i switch off Social Counter pulgin then VC starts working.

Maybe there is the conflict between the VC and SC ?

NOTE TO ALL…
a couple of us folk on the forum have done a bunch of speed testing today, and upshot overall is…

ROLL BACK TO 1.6 …

v1.7 does seem to have some issues causing CPU headroom, php crunch, and slow load times compared to 1.6.

Those who know me from these forums the past 1.5 years know I’m usually the last to say “sky is falling,” but in this case I am recommending going back to 1.6 or staying there for now.

I *DO NOT* recommend using v1.7.0 of Newsmag, at least on Linux/Apache.

Thanks for that Chris.

I’m running 1.7 on nGinx with PHP 5.6.6-1+deb.sury.org~precise+1 / 64Bit OS

And I did recieve weird numbers on performance as well.

Just as an FYI,
the 1.7 version of theme was causing CPU spikes to go from our normal load of “0.9” to “1.1” up to “270.0” … (!) … considering our old server prior to Jan 2014 would have completely crashed at “60” — that’s pretty amazing in and of itself. But, server was pushing out “high load” warning emails hourly, and php status going from green to red every hour for a full day since switching on 1.7.

Going back to 1.6 immediately resolved that issue.

Normally I was skeptical of the whole “theme is crashing my server” issue, but this did in fact happen with us, and my server is about as hot-rodded and streamlined as currently possible with Linux/Apache/CentOS/Plesk-Parallels + mod_pagespeed and mod_SPDY, opcache and php optimizers; 8+ cores of XEON CPU and 32GB RAM (enterprise class server).

Still blown away server didn’t crash with “270” spikes, and email still worked, and other sites worked …. but normal server response overall also went from 0.3 seconds to 1.6 seconds and longer.

Obviously, you know there is an issue; but this is just anecdotal info for anybody else running into a WTF? moment.

Peace out 🙂

• This reply was modified 11 years by simchris.

Well we tried all the suggestions, but in the end VC and Newsmag combination is broken in our system no matter which combination we try. I have already invested too much time to trying these theme-plugin version combinations and disabling other plugins, trying with different themes.

Also in these changes our ad serving got problematic with theme changes deleting ad zone codes and I had to replace them all. Calculate lost impressions and delivery time of campaigns.

In the end CPU spike was too much pain so we have rolled back to Newsmag 1.6, uninstalled Visual Composer and changed homepage into blogroll.

Theme is great, VC is great but they don’t scale well with lots of traffic. But I still like it, it’s foundations are strong, support staff is working. I hope these problems will be solved in a month, next update etc. and we will be able to use a different homepage design and also keep it fast and bug free.

Thank you again, I’ll be waiting for an update.

• This reply was modified 11 years by aleister.