Search Results for 'composer'

Well as of now I’m using the latest theme and jetpack, also the following plugins

Add Meta Tags, Akismet, Contact Form 7, Limit Login Attempts, Post in Page, Remove Category URL, Revolution Slider, tagDiv Social Counter, tagDiv Speed Booster, WP-GeSHi-Highlight, Visual Composer and WP QuickLaTeX.

In Jetpack I’ve activated Custom CSS, Custom Content Types, Gravatar Hovercards, JSON API, Jetpack Comments, Manage, Publicize, Shortcode, WP.me shortlinks and WordPress stats.

So far there is no problem.

Welllll…..
here’s the thing …. if you don’t have robust hosting, I’d likely consider NOT using ANY theme running Visual Composer. All during 2014 with the Newspaper theme we’ve seen zero problems with CPU stuff, but during 2015 it seems they are using bleeding edge stuff to give power users all the stuff they have been demanding … unfortunately a lot of people want their site to do stuff that takes 500 processes and their hosting account can only do 150, and kaboom.

I’m still running the Nov. 2014 version of Newspaper for one of my blogs. Zero hassles. But I didn’t update every time a new version comes out since I didn’t need the extra 50 things added.

So, it’s kind of a tricky thing … I think VC needs to have a “developer mode” and a “deployment mode” where you have all the bells and whistles for design, then “export” your settings for a “lean” setup for actual deployment. But, it isn’t quite that clean yet.

TagDiv chose to use VC 2 years back as it was the coolest thing since sliced bread, and still is. There is another open source very very simple pagebuilder, and couple of page builders which cost $99/year (and stop working unless you keep paying!). So, for a complex layout builder like this… VC is really kind of the “standard” right this second.

Then again depends on well optimized server. I’m running multiple installs of Newsmag and Newspaper, and server not overloaded in the slightest.

Yes. Visual Composer is a memory hog.

Also if your site gets overloaded with requests. I just posted note on the Newsmag forum about our site getting slammed by the YANDEX bot and our server processes when from normal of about “1” up to “49” … which is 50x normal (!)… it’s actually worse than that. We blocked Yandex and it’s coming down to normal.

Hey Chris,

Yes I use very minimal stuff like that,

I did read someone said something like it could be the Visual Composer?

Could this be the reason?

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.

Mine’s working perfectly, after reinstalling the Social Counter and Visual Composer plugins. These plugins are conveniently included in your Newsmag-tf (v 1.7) folder download from ThemeForest.

I really appreciate the hard work you guys do! Newsmag (and Newspaper) have to be amongst the top WP themes ever produced.

Mine’s working perfectly, after reinstalling the Social Counter and Visual Composer plugins. These plugins are conveniently included in your Newsmag-tf (v 1.7) folder download from ThemeForest.

I really appreciate the hard work you guys do! Newsmag (and Newspaper) have to be amongst the top WP themes ever produced.

I apologize for the inconvenience – have discovered the filter available using Visual Composer and Widgets. So this solution has already been found.

Sincerely,

Philip

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.

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 went from 1.4 to 1.6 with zero problems last week.

Last night I upgraded site from 1.4 to 1.7.

Only issue I had was NORMAL issues of some of the sidebars getting reset (meaning some of the widgets didn’t save); and had to “resave” the homepage just to reset it. All settings normally carry over due to the built in “transient” settings of WordPress. Everything else was exactly as I’d left it.

You should also be regularly doing backups of your site, theme settings, etc.

If you made custom changes to the core files (e.g., style.css etc.) you would, of course, need to apply those changes to the new files.

1.7 works fine with couple of minor issues, depending on if your hosting co is running old php tech which is really somewhat deprecated.

So far only bugs I’ve had are one spacing issue in a stock WP recent posts widget, and the modules in Visual Composer won’t let me filter by any author except myself.

Everything ELSE is working fine for me in 1.7, but SOME people are having some weird issues which are common with all WordPress site changes/updates like this. Main issue is the use of some code in the theme which is not playing well with OLDER versions of php (we are running PHP Version 5.4.22).

So, check the version of PHP you have … if 5.4.22 or newer, should be ‘mostly’ fine.
OR: wait for a dot revision of 1.7.1 next week, I’m guessing.

Don’t know if that helped or just re-peated the other posts, but my two cents anyway. 🙂

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

Hi, typically you need to
a) setup a page, create layout with visual composer, preview
b) go to WP settings > reading > first section
change to using the page name you created for home page
front page displays
[x] static page
>> page name

Hope that helped 🙂

Often what I do is just do a simple 2 column layout with something like

[ 2 col ] [ 1 col ]

in left column use block 11 for latest
in right column use widget area, temp use the default sidebar

make that live so home page works

then I create second page to mess with layouts until I like it, then swap the static page used for home page and delete the first page.

Hope that helped 🙂

My update went perfectly.

@carelpedre
try to delete visual composer, tag div plugins folders, theme folder, and install the new versions from scratch; don’t use child theme; try using my upgrade guide.

It does work!