You would need to either adjust your hosting settings, or ideally learn to upload via FTP, as this also allows you to make site backups same time and is the ‘best way’ to manage WP sites.

We’ve been using the Automattic AMP official WP plugin since it was in beta back end of 2015; and works perfectly. And it’s fully compatible with WP, since it’s made by same people who make WordPress. Worth a try 🙂

Hi, as noted in my posts, auto post thumbnail pro, which i think is $7 on themeforest/codecanyon.

You can test with one of our news feeds if you want ?

See the footer settings in theme panel.

A simple css mods tutorial for black version would be cool.

Feedwordpress does this. It can put stories into dbase and then put into modules or cat indexes, but links go to external sites. However, you need something like auto post thumbail to add photo to featured image.

LOL. 10,000 news sites using theme. 😉

You can add author metrics via plugins — such as google analytics with custom metrics-dimensions, PiWik, etc.

I’ve been using Feedwordpress for several years and helped donate and provide feedback to its developement, and use it with a dozen sites with TagDiv themes (we publish from our mothership, and then have local/regional portals unrelated to the main site, but which includes content from the main site).

No idea on WP RSS Aggregator. Why not try it?

RSS import plugins have nothing to do with the ‘theme,’ — they pull in content into WP posts, optionally slot that into categories automatically and/or create new tags, and/or go into a default category you select. They don’t do anything else to your theme settings, although you might be able to select some theme settings via hooks/filters.

Meaning, they don’t have to be ‘compatible’ with theme to work, they need to be compatible with WP 4.7 and higher to work.

• This reply was modified 9 years by simchris.

See the them docs on how to upgrade. v8 is entirely new version, with many many changes, so be sure to review the help/info before doing so.

How did you try to update/upgrade?

Best way is via FTP, so that you can make backup first, and then roll back if you have problems with new version.

You can keep using Visual Composer – it’s not ‘gone.’

The TDComposer is a more lightweight, faster, more secure solution for those who only use the pagebuilder for home page, business info pages, etc. and don’t use it on posts, where there is already wide variety of custom post layouts.

For our sites, it’s a perfect fit, as we don’t custom build ‘posts,’ only ‘pages’ and so it’s much faster, and less prone to all the weird system issues we’ve had with VC.

Nothing to correct in the sense of “it’s bad….” — if you have found a bug and can identify how you experienced it, where and why, and what steps taken to debug that, they will definitely address it for the next update to TDC — which is still fairly young, and still being developed.

TDC is *not* a 1:1 replacement for VC. Two totally different things.

If you like VC, keep using it. If you don’t want to switch to TDC, you don’t have to.

You have to enable comments in wp admin settings first, under discussion. Then turn on from theme panel to switch on in the templates.

Not issue with theme.
As long as you have proper open graph og meta data in your post source in head meta, its up to fb to grab. Theme has no control over that.

You can try fb debugger.

Yes. You can use feedwordpress and auto post thumbnail pro.

You can pull news from
Send2press.com/wire

As long as not selling a competitive service. News available by topic, industry, us state, tags.

Make sure you update the plugins AND the theme together; delete old folder, don’t ‘overwrite’ old ones.

Clear transients with WP-Optimize plugin

Resave permalinks

Works for me doing that.

(also: make sure you’re using PHP 5.6 or higher; as older versions will not work well with most current WP updates, plugins, code, etc. — and older versions are ‘end of life’ now, esp 5.2/5.3).

• This reply was modified 9 years by simchris.

1) make sure you properly installed the new theme and related plugins — you need to delete old folders, not simply over-write them; but make backups via FTP first — as ever
2) after update,
– run WP-Optimize plugin to clear transients
– resave permalinks to clear micro transients
3) make sure you clear/reset any caching plugins prior to update/upgrade and afterwards; if not using caching plugin, the 1 and 2 above should help.

That’s what I do anyway. 🙂

Ask your host to allow caching plugins. Or get better hosting provider.

Theme doesn’t manage your hosting company choice.

KNOWN SECURITY ISSUES:
* Newspaper 6.7.1
* Newspaper 7.0
* WordPress prior to 4.7

MAKE A SECURITY PRACTICE POLICY CHECKLIST FOR YOUR SITE(S):
Also good to setup a security policy internally — you should be checking update changelog/readmes for *all* plugins/themes you use and for WordPress core — as the TagDiv theme security notice for 6.7x was included way back in April 2016:

Version 6.7.2 – April 27th, 2016
fix: social counter facebook issue with new API keys
fix: security issue

a minor issue with 7.0 was fixed with 7.1 for those early adopters who rushed to install 7.0

Version 7.1 – May 20th, 2016
fix: panel got stuck while saving in specific cases, mostly related to categories
fix: Related articles filter was not working with the settings from the panel if you choose related by tags and the post had no tags set.
fix: contributor users cannot change the post template now, this is more in line with WordPress
fix: Security issues
fix: back to top on ie9
fix: missing woocommerce add to cart on mobiles

==============
Everything on the web requires periodic checkups; it’s not static like old websites with static shtml files or similar. WordPress, plugins, PHP, MySQL, WooCommerce, etc., all need to be *checked* when updates are done — new features, no need to upgrade unless you read the help info first; for security patches, these should *always* be done when originally notified!

I don’t work here — but our ‘security practice policy’ internally forces us to CHECK when new updates come out to see WHY they were updated, in case of security issue(s).

Recommended you consider the same, or hire a company to do it for you.

• This reply was modified 9 years by simchris.

Also good to setup a security policy internally — you should be checking update changelog/readmes for *all* plugins/themes you use and for WordPress core — as the TagDiv theme security notice for 6.7x was included way back in April 2016:

Version 6.7.2 – April 27th, 2016
fix: social counter facebook issue with new API keys
fix: security issue

a minor issue with 7.0 was fixed with 7.1 for those early adopters who rushed to install 7.0

Version 7.1 – May 20th, 2016
fix: panel got stuck while saving in specific cases, mostly related to categories
fix: Related articles filter was not working with the settings from the panel if you choose related by tags and the post had no tags set.
fix: contributor users cannot change the post template now, this is more in line with WordPress
fix: Security issues
fix: back to top on ie9
fix: missing woocommerce add to cart on mobiles

==============
Everything on the web requires periodic checkups; it’s not static like old websites with static shtml files or similar. WordPress, plugins, PHP, MySQL, WooCommerce, etc., all need to be *checked* when updates are done — new features, no need to upgrade unless you read the help info first; for security patches, these should *always* be done when originally notified!

I don’t work here — but our ‘security practice policy’ internally forces us to CHECK when new updates come out to see WHY they were updated, in case of security issue(s).

Recommended you consider the same, or higher a company to do it for you.

The old version from prior to April 2016 had a security issue which was patched in 6.7.2 — and an issue with 7.0 fixed with 7.1. Similarly WordPress prior to 4.7 is insecure.

ALWAYS check the ‘changelog’ when new versions of themes, plugins, and WordPress core released to check for security issues.

If you don’t want to upgrade to v8 which is entirely new version and will require changes to site; you can email tagdiv (link bottom of page), to get 6.7.2, or 7.x, however they no longer provide tech support for 6x, so you’d be on your own if continuing to use it.

If you didn’t keep backups of your site (good idea btw!), or the prior downloads for install from TF, you can send TagDiv and email asking for the older version. I think you just email them and include your purchase code, and they can send you older version(s) 🙂

I think the Force Regenerate thumbs plugin does that house cleaning.

They can’t fix your content.

You can keep using Visual Composer — you don’t need to stop using it. TDC is optional, and is primarily for those starting with theme first time, or who only use it for stuff like home page and custom pages — not posts.

If you use to use TDC in place of VC, you will need to redo some stuff.

Or, just keep using VC.

TagDiv doesn’t make or manage WP SuperCache — you may want to use the support site on WordPress.org for that plugin, to get faster help!

You can upgrade to the version 7.1x which is advisable if not wanting to go to 8x.

Also good to setup a security policy internally — you should be checking update changelog/readmes for *all* plugins/themes you use and for WordPress core — as the TagDiv theme security notice for 6.7x was included way back in April 2016:

Version 6.7.2 – April 27th, 2016
fix: social counter facebook issue with new API keys
fix: security issue

a minor issue with 7.0 was fixed with 7.1 for those early adopters who rushed to install 7.0

Version 7.1 – May 20th, 2016
fix: panel got stuck while saving in specific cases, mostly related to categories
fix: Related articles filter was not working with the settings from the panel if you choose related by tags and the post had no tags set.
fix: contributor users cannot change the post template now, this is more in line with WordPress
fix: Security issues
fix: back to top on ie9
fix: missing woocommerce add to cart on mobiles

==============
Everything on the web requires periodic checkups; it’s not static like old websites with static shtml files or similar. WordPress, plugins, PHP, MySQL, WooCommerce, etc., all need to be *checked* when updates are done — new features, no need to upgrade unless you read the help info first; for security patches, these should *always* be done when originally notified!

I don’t work here — but our ‘security practice policy’ internally forces us to CHECK when new updates come out to see WHY they were updated, in case of security issue(s).

Recommended you consider the same, or higher a company to do it for you.

With 8.1 you can continue to use Visual Composer if you wish; so keep using that, and do not activate TD Composer.

TDC doesn’t support posts; only pages.