Likely you should ask for how to disable the “divider line” in the visual editor on post/pages; that way it will work just like the WordPress default methodology.

Google follows all links on your pages, even if set to rel=”nofollow” … internal links on your site to your own pages do help your “link juice,” but not to external sites if on “all pages” as that is spammy. This is not theme related; all sites often have used footer links to make navigation throughout a site easier when somebody hits bottom of page (so not needing to scroll to top to see top menu again, or side menu).

There is nothing in the theme that prevents Google from following the links on your pages, or the footer, or the header, or the sidebar, etc.

You may have custom settings in Yoast WordPress SEO – or similar – which can control which elements are not followed (such as nofollow internal links), or which hide pages from your XML sitemap.

The thing is, Google now looks at your XML sitemap, if available to determine what content to index, its “priority” and to build the custom results in search, where for your site it would show things like your “about us” page and “editorial staff” as primary information pages; this is also where the footer links can help.

Footer links to external sites should be rel=nofollow.

I’ve had no issues with this on our site(s); and I thoroughly test our site on desktop (Mac/PC), iPad Air, and iPhone 6, with no issues with layout when “live” on the web, and no issues with preview.

The line first threw me when I saw it too, but I mostly work in text mode except when pasting in articles from couple of writers who work in MS Word and I have to paste into the visual editor. It’s actually kind of nice once I figured out what it was for, to have a better idea of how wide the “real” column is on the site while working in the editor.

I don’t recall seeing an explanation of that in the theme docs, but I might have missed that also.

UPSHOT: on one production site and one test site, it has not caused any issues whatsoever (links available if curious).

You’ll need to contact your hosting provider to fix the maximum filesize directive.

You need to activate the theme with your license code in order to verify you purchased a license.

The theme does not phone home every day or anything like that (“check in”). The registration cannot “crash” widgets or plug-ins. Since it doesn’t have any code being loaded to interact with plugins or widgets, how would it crash the same? Since the code is already there, why would it suddenly damage your system by activating it? Seems more logical it would stop working by NOT activating your license (!).

Never seen that in 10 years of using themes; so it must have been some pretty “funky” themes with that requirement.

One presumes you’re talking about the THEME license, and not the Visual Composer license, which does not apply to the theme. Same with stupid Envato plugin, which is not recommended for anything.

• This reply was modified 11 years by simchris.

Nope. You can only update the version included with the theme, when the theme is updated.
See the theme docs, right side of page for more info.

Or, the “sticky topic” top of the forum:
https://forum.tagdiv.com/topic/how-to-update-visual-composer-2/

• This reply was modified 11 years by simchris.

using basic CSS for responsive design also may help:

eg

style="width:100%;max-width:700;height:auto"

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

Switch to HTML editor and make sure the HTML shows class=”alignleft”

If you’re running WordPress 4.1, make sure you have Visual Composer 4.3.5 installed, and if not you will need to get the latest version of the theme via your themeforest account and update your site. WordPress 4.1 “broke” the visual editor, hence the theme update.

Some plugins conflict – so nothing for the TagDiv folk to “fix” on your end; try turning off all plugins except Visual Composer, then turn each one on until you find the “bad” plugin. You would then need to either not use that plugin, which might not have been updated to work with WP 4.1, or get a fix from that plugin developer.

The VC works perfectly on tens of thousands of websites, and so the “fix” is to determine which plugin is causing the problem 🙂

Right, some themes have both a responsive and non-responsive layout; this theme is built as a responsive theme as with the “new Google” your site may be hidden in SERPS if not responsive, so nobody is really building “fixed layout” themes anymore, except as special cases like internal sites/forums, which would only be used on desktop — which will be increasingly rare.

So, you can try to edit out the @media queries in the style.css file; but that’s about it.

It’s a “responsive” theme, so you can’t really disable the responsive features – that is how it’s designed. It’s not an on/off proposition.

You could try to edit the @media queries in the style.css file, but you could have very mixed results with that. (e.g., remove all the sizes for phone and see what happens?)

You can also disable ads on the phones from the ad manager in the theme, so you might try that first.

For example on this page:
http://www.miseeharris.com/deflategate-nfl-investigating-patriots-footballs/

you have a whole bunch of errors, one seems related to ads, one with JQUERY, as if a plugin is trying to load something; a bunch of “access denied” errors; and looks like some error related to a social media element, and a slideshow element.

If using a plugin for any of that kind of thing, it might be the fault!

@misee

try disabling all your site plugins, except for Visual Composer.

If you are using a caching system, or you see a big [clear cache] button in your admin (as with GoDaddy), you need to clear that.

With only the theme active and Visual Composer active. Hit refresh [F5] on one of your post pages; the “view counter” should increment by 1 when you do so. Did that work?

If so, then turn on your other plugins one by one and re-test until you find the plugin which is breaking the theme.

Only you can do this, as you need to learn to manage your own website.

If you are using a caching system/plug-in you need to use an advanced setting in the theme to enable “ajax counter” capability; where the theme attempts to use javascript (JS) to increment the counter, since the caching would normally preclude or block that from working (e.g., the idea of caching is to serve up a page which does not change; so how can the counter change on the page if it’s cached and not actually being served as new page – logical, right?).

This is the best way to “debug” why your particular instance does not work.

Then post an update here with a sample page link to one of your posts, if you can’t get it working. 🙂

Also, not a good idea as the site would not then pass Google’s new mobile ready label program for phone users.

REF:

Wondering if your site will qualify for Google’s new mobile-friendly labels or be ready for a potential mobile-friendly ranking boost? Google has a new tool to help.

The new tool is at https://www.google.com/webmasters/tools/mobile-friendly and it basically gives you a pass or fail grade. Either it tells you that you are mobile friendly or you are not mobile friendly.

Yes, as stated:

Actually, the theme folks *do* put in code to stop the “nag screen” from showing up, but the people at VC keep changing their product, and so that keeps coming back when it really shouldn’t.

I have one website where I have 3 nag items right now; but all 3 have bugs and so can’t be updated until fixed; so I just ignore them. I concentrate on the content, SEO, growing readership and get on with my life. Highly recommended. You’ll go nuts worrying about the pesky updates.

I agree. Kind of annoying, though. But not strictly a “theme issue” — but a plugin issue, and Tagdiv does their best to work around that.

Whew! I’ll shut up about this now! 🙂

Ha! yeah… one of my clients uses GoDaddy, and the fact they have a major caching plugin running which has to be cleared TWICE for any updates is a pain in the keister. 🙂

Awesome!!!!

Thanks again! 🙂

Thanks, Marius
will give it a try.

I did try the usual debug tricks like removing any review bullets from sidebar, etc. and still had the problem, hence the “cry for help!” 😉

Chris

The theme developers don’t do mods, unfortunately; but perhaps another kind soul here might help out.

You need to use the version of visual composer included with the theme.

Try using Chrome; since IE on Windows sucks with Ajax stuff. If using Mac, make sure Safari is updated to current version.

It does work; being used by tens of thousands of websites.

Try using with just Visual Composer running v 4.3.5 and WP 4.1, and no other plugins.

see:
https://forum.tagdiv.com/topic/how-to-custom-time-stamps-on-posts-etc/

Yup:

from the theme docs:

How to Update Visual Composer plugin (WPBakery)

•The theme includes a license for this plugin so you don’t have to buy it.
•You don’t have to activate the plugin license, it’s already activated.
•You can’t update the plugin directly from the it’s producer.
•You don’t have to worry about the plugin update warnings.

from the theme docs:

How to Update Visual Composer plugin (WPBakery)

•The theme includes a license for this plugin so you don’t have to buy it.
•You don’t have to activate the plugin license, it’s already activated.
•You can’t update the plugin directly from the it’s producer.
•You don’t have to worry about the plugin update warnings.

from the theme docs:

How to Update Visual Composer plugin (WPBakery)

•The theme includes a license for this plugin so you don’t have to buy it.
•You don’t have to activate the plugin license, it’s already activated.
•You can’t update the plugin directly from the it’s producer.
•You don’t have to worry about the plugin update warnings.