Version 8 is a new version, not an update, so this is always possible with any major update to anything, whether it’s WP, WooCommerce, or themes. You don’t have to update theme if you don’t want to; it’s not mandatory.

The new theme has option of continuing use of Visual Composer page builder for custom home page or pages; or use new light-weight version the TD Composer. If using the TDC, yes, you will need to test and adjust any page using VC, as some modules are carried over but not all – so you would need to change the pages which have any VC element which TDC does not have.

Options
a) don’t upgrade if you have no compelling reason to do so
b) upgrade and use Visual Composer vs TDC — but yes, any custom code added to any core files always has to be moved to new version as new page templates over-ride old ones; this is common with any customization done to any theme
c) setup test area, with clone of site (such as sub-domain, or folder on existing site); switch to TDC, then adjust pages which have broken elements to alternative option from the TDC builder; then once done – copy the clone dbase into the original dbase and replace old theme with the dev theme. Anybody who knows what they are doing as webdev would know how to do all of that.

Hope that helped!

(I don’t work here; but accept tips of cookies and pies!)

Perhaps the other site you’re loading image from doesn’t allow that image loaded on mobile?

If the URL is in the post, check the URL to image works on a mobile device.

In my case I think I took out some stuff related to woocommerce and BBPress — don’t recall. Sadly most theme devs don’t “ship” commercial themes with everything minified by default for various reasons.

a) see the theme docs on how to install, right side of page
b) presumably you have the zip files downloaded from themeforest? FTP is best way as you can make full backup of your files first; and you should be making a download of your WP dbase through
1) WP panel > export
2) phpmyAdmin/hosting panel > save/export Php dbase used for your site
3) make copies of any special settings for things like sidebar widgets, or custom code boxes used in prior theme — save out to text file
c) you will want to install the Newspaper.zip, not the ‘all files’ zip
d) the child theme is a child of Newspaper, not child of any other theme; meaning, generally you don’t need to use child theme unless you have specific reason to do so

(( I don’t work here; just some basic advice. ))

Again —
if you compress the non-minified version, you will have working version.

The included minified version is for special cases, and might not work with your setup. At least that is what I understand.

Again — if you take 5 minutes and compress the .js using Google’s tool, it works 🙂 I’ve been doing it for long time now with zero issues.

But I don’t work here — just trying to help 🙂

If you setup home page same way with same meta data and structure, why would your SEO change?

You can create virtually identical home page with TDC vs VC and much smaller data payload for TDC vs VC, so pages *will* run faster for most people on modern servers.

Most of the ‘custom’ modules for the THEME were created by TD, not by VC, so easy for them to port into leaner meaner builder. Also “most” people don’t use the builder for “posts” and only use for “pages” such as home page, services page, etc., and all of that can be built/tested with draft pages — without harming live pages, per normal WP dev practice for revamps.

It’s a win-win for everyone, not a mistake or fool’s errand. VC has a huge footprint, and on some systems it kills the box, and after several years of growing bloat many of us with news portals refuse to use it on anything except a simple corporate site.

TD Newspaper plus the TDC builder will be an awesome option for folks who are starting from scratch, migrating to leaner build structure vs VC, and for those who want to optimize system resources and drop all the bloat in VC that they never have or will use for anything.

Just an opinion for anybody dropping into the thread in a ‘panic.’ (TIP: don’t panic!)

Our site works properly based in California, server in Texas, Windows 10, Chrome, with TD Composer. Those elements have nothing to do with whether the plugin works.

Usually it’s due to a javascript conflict from another plugin, weird settings from using CDN or optimizer/compression plugin/service/host, a bad plugin added to Chrome (extension), corrupt cache, having more than one page builder active at same time (you can only use VC or TDC not both), etc.

Usually because if people need to modify the code in developing a website, it’s not readable once compressed.

However, what we do over here for our sites is use the Google recommend .js compression tool to minify the main .js file — remember you need to disable your caching, clear it, before swapping file otherwise you’re still loading old file even with new one in place.

correct way to compress your js file:
http://closure-compiler.appspot.com/home

ref:
https://developers.google.com/speed/articles/compressing-javascript

( I don’t work here … just resident smarty pants mcduff…. )

Try
a) not using jetpack
b) test site with *no* ads running
c) remove all demo content
d) don’t use “number of likes” from FB/Twitter on your posts/pages or sidebar

(etc)

Everything you pile onto a page that goes to another site to grab stuff adds bloat.

Once you optimize a “lean” site, then start adding bells/whistles to the point it doesn’t die on speed. 🙂

(At least that’s what I do … )

(( I don’t work here… just a smarty pants who butts his nose into other people’s business… 🙂 )

@henrib

answered it twice now.
I’m out!

(that should have said ‘newbies’ not ‘newsbies’ …)

Heh. My company started doing SEO in 1995. We pioneered many of the things most people today take as common sense, before most people here were even online or perhaps had a PC; before Google launched, in fact.

However, your point was a good one, in a certain respect: people need to learn to use WordPress and what things do, RTFM on WordPress.org (codex), etc. to better understand what’s going on.

So, perhaps TD needs to mention couple of scenarios for “newsbies” on the tutorial, on instances such as my two examples for those who don’t yet know any better, simply from lack of experience.

In your case, providing helpful examples on how to improve the situation vs simply complaining ‘the suck’ does not help anybody.

Perhaps create a better tutorial and post it? That would be way more useful here. 🙂

(( I don’t work here; sometimes I help, sometimes people hate me. Sorry about either. ))

• This reply was modified 9 years by simchris.

Dunno. I never used VC for posts, as for just such an issue as this.

I think there is a ‘conversion’ tutorial, someplace where one could do search/replace in the post meta via phpMyAdmin (just like if moving from http to https where one needs to replace image URLs — same idea).

Presumably if you have a
[VCshortcodexxx] my neato content [/VCshortcodexxx]

you could search/replace with
[TDCshortcodexxx] my neato content [/TDCshortcodexxx]

* in theory… *

On the plus side — it’s simpler to move to TDC than say, oh, SiteOrigin, or similar, where *nothing* would be compatible.

No reason to not use VC if you like it — it was just major resource hog on my dedicated server, so Radu made a ‘shim’ for us originally; which of course has evolved into the TD Composer — basically it’s the custom blocks CSS they came up with to fit their site design, along with some additional stuff like slider, so one could build a home page layout, without the bloat of VC.

However, it doesn’t have the hundred plugin/hooks/expansions of VC – obviously.

For now, I believe TD is providing it as an option … if you want it, but not required to if you don’t. For some people it’s a major “woo hoo” and for others “meh.”

Hope that helped a little.

🙂

“I lurk for free ginger bread cookies in my tip jar… still waiting …. “

AGAIN: you cannot use BOTH plugins same time. Period.

If choosing to use TD Composer, you will need to
a) NOT activate VC under plugins panel !
b) adjust any/all existing pages built with VC, as TDC not 1:1 replacement.
c) then, all FUTURE new pages would be built with TDC

Put another way, imagine Visual Composer went out of business and TD made their own version to maintain compatibility with WP moving forward, but not direct replacement as some elements are ‘owned’ by VC as it’s their commercial code.

Or, put another way – say you like some of what VC did in making cool home page layouts, but VC crashes your server, especially if you’re still on PHP 5.4 — this would be suitable replacement for much lighter weight, less resource heavy, version to do “mostly” the same thing. And, it’s also got less code complexity and “bloat” and therefore far less likely to have the security flaws which have popped up once in a while with VC.

(I don’t work here.)

What a blunder you made for this post!

You are able to make new ‘pages’ as drafts to build a new home page which only you can see and is not public and has no impact on SEO as it’s not visible on the web.

You then delete old page, then make the new one live at same time.

If you keep the same ‘slug’ as the original then there is no lost link juice, or SEO value.

Or — if you don’t know how to maintain same slug; you build new page as draft, then copy all the new code to the old page.

Perhaps you will want to learn more about SEO and how WordPress works before such posts in the future? You don’t need to have two live pages with same name or numerical addition.

If you have

/mysite/services-pricing/

draft page can be

/mysite/services-pricing-draft/

then when old page deleted, change the draft page slug to remove word ‘draft’

For home page, where you choose a ‘static’ page from the WP settings panel (not theme panel); you simply make any number of draft versions to test, then simply update the settings for static home page to the new one. Duh.

What a blunder you made with this post!

Have fun out there!

(I don’t work here. Just a veteran of WP and webdev — aka ‘a dinosaur’)

• This reply was modified 9 years by simchris.

Yes, you want to use one or the other NOT both.

TD Composer is new option to use in place of VC; but not 1:1 replacement. So, you may need to adjust any pages/home page built with VC if switching to TDC.

Same answer already provided.

If not infected site or PC; might be a bad plugin you’re using.

• This reply was modified 9 years by simchris.

Hi,
I think there is a tutorial guide in the theme docs (see link right side of page). It’s under the other DIY tutorials…

https://forum.tagdiv.com/cache-plugin-install-and-configure/

(I don’t work here )

You should use one *or* the other, not both.

Tagdiv Composer is a lighter weight version page builder which is more secure than VC, doesn’t need activation from WPBakery for support, and is much faster with smaller footprint. But not a 1:1 replacement either.

it’s there as option for those who don’t like VC, or where there are resource problems with hosting account, or who don’t need all the bells and wistles VC has which many peeps never use.

I think they have a comparison for it someplace …

With most modern web hosting services, you can also change this in your php settings from your hosting account panel.

Actually, this is PHP and WordPress issue – not theme related. Comments should not be used in any data field, ever.

Welcome to WordPress !

Make sure not to use TagDiv Composer and VisualComposer at same time — won’t work!

Jumping from v4 to v8 you’re much better off doing clean install via FTP, after doing backups, and such; as so much has changed, it’s quite a lot. Went through that with Newsmag going from 1x to 3x.
(I don’t work here – just opinion.)

clear caching, resave permalinks, clear transients with wp-optimize plugin, etc.

Use unarchiver for mac if unable to install 7zip on your mac for some odd reason.