If you have an issue with permissions or your WordPress built-in installer times out for some reason, the best way is to use FTP; this allows you to
a) make backup of your site files
b) delete old theme folder
c) upload new clean copy of theme folder

Seriously, best way to always update WordPress themes to not run into this issue of partial/broken installs. Very common with some hosting setups or if your process time settings is too short for PHP, file size uploads too small, etc.

• This reply was modified 9 years by simchris.

Not theme related; see the WordPress Codex for help on using more than one site with a single database.

https://codex.wordpress.org/Installing_Multiple_Blogs

You may need to hire a developer if the above page makes no sense to you.

Database is part of WordPress and MySQL, not managed by the Newsmag “theme.”

(( I don’t work here. ))

Might be good to put the sticky posts on color backing like the one for TD Composer, otherwise i think a lot of peeps miss that it’s not just another post unrelated to them.

And — hey ! — I need a [IV] badge ! 😉

Nope.

https://forum.tagdiv.com/topic/how-to-update-visual-composer/

Meaning — just because there is an “update available” for the plugin, does *not* mean you NEED to update. You never NEED to update a plugin when one becomes available unless there is major security issue. You need to always check for bugs in plugins prior to update such as major bugs in Yoast 3.6.

Upshot – you can ignore the “plugin update available” notice for VC until the next theme update, and then update from the download for theme on TF.

Hope that helps and lowers panic level 🙂

VC doesn’t “require” updating except when theme updated.

You would need to find the custom field used by prior ‘hit counter’ and then modify the

/theme/includes/wp-booster/td_page_views.php file

change this line and element to match your pre-existing data field for views:

so, for example if your old custom field was “views”

then you’d change this line at top of the above file from

static $post_view_counter_key = 'post_views_count';

to

static $post_view_counter_key = 'views';

This should actually be in the theme docs under the “post views” information, as it’s common fix. I have to do this for our sites, also.

Hope that helps!

You need to update VC each time you update the theme, as new features added may require the new version and/or the new version of VC may fix bugs from prior version. Viewing the changelog for the theme also super useful.

Site is not penalized for <h3> tags …. <h2> tags only useful for persistent content, like a sub-headline, or a section head. All other “presentational” headlines, index links to articles, etc., can be <h3>. Google does not penalize you for using h3 tags. h1 tags are used for SEO, h2 is generally only used once on a page also, and h3 is used for all supplemental sub-heads, section heads, relational heads, etc.

Content is more important than h2 vs h3.

But you might provide an example of where on your page, post, index, etc., you feel this isn’t being done properly in your particular usage ?

( I don’t work here, but started web dev in 1994, and SEO in 1995 (!) … so ….. know something about it … )

Yeah. Agree. Note it is the top “sticky” subject seen first in the forum. 😉

A lot of people miss that.

(( I don’t work here. ))

https://forum.tagdiv.com/topic/how-to-update-visual-composer/

You need to also update the VC plugin with the theme update. 🙂

Lots of factors; speed of test connection, number of images, site optimization, mix of CDN, or custom server (10mb, 100mb or 1GB connection), https with or without http/2 support, mod_pagespeed, etc.

Speed of “theme” not relevant in context of “speed of optimized site using theme.”

Just a comment, I don’t work here 🙂

Sadly, I’m not using Newspaper anymore except on one blog thing of mine …. and have moved over fully to Newsmag 3.1, so any suggestions for the “mobile theme” here would be more anecdotal than specific, unfortunately.

Note that even if in footer, doesn’t help that issue with CSS, as page still cannot load “above the fold” without that CSS — hence why you need to use critical css generator to load the main CSS inline in the header.php — this way, mobile browser does not need to WAIT for the bottom of page CSS to load to render anything. Upshot, without the inline CSS, doesn’t matter WHERE the main css files are on page — entire page is “held up” by waiting for that to load, hence the error.

So
step 1 – generate critical css for page; step 2, have that code added to header.php before the closing </head> tag; step 3 have main css loaded in footer.

this way the ‘above the fold’ content loads without waiting for css file(s). :_)

Have you setup a video XML sitemap?

Use an ad manager plugin.

You may find my optimization thread useful, and I’ll update this again soon.

Note the ONLY way to fully remove above the fold render blocking on mobile is to move style.css to footer, and then use a “Critical CSS Generator” to load ALL “above the fold” CSS content in the header file inline. Period.

Second, Google also has bee in their bonnet about “tap targets” — so stuff like tag or category links need padding between them for “tapping without touching other item” concept. Really annoying with stuff like footer text. But easily fixed with minor CSS tweaks.

Nope. You should only have *one* h1 tag on your home page, which would normally be something for SEO that is static like a block of info about your publication. H3 is most often used for headlines on news pages as they are not sticky, meaning if you have 20 items on home page, then 20 new items post, then the other 20 drop off home page and are no longer there, so have zero “long tail” value for SEO for exact phrase matching.

h1 and h2 tags most commonly used for static content in relation to the actual article/news item or page, not the other content linking to it. So, h1 for a title, h2 for a sub-head; h3 for supplemental headlines which are more indicative of a section head, than simple bolded text items.

Welcome to SEO 🙂

Google does not necessarily provide more “juice” to something with h2 or h3 tag on your home page. Almost everytihng other than h1 is pretty much presentational.

So you can use h3 tags on your mid-story sub-titles on an article while h2 might be used for main story sub-title. H1 for main title.

Only you can optimize your site for SEO; theme can’t do it for you. So, yes, adding h1 and h2 tags to your home page with static information is useful. Not so much with transitory items. You can of course make any heads for sections as h2 using blocks in the composer (e.g., “Book Reviews” as h2 sub head above a block of book review items…). Totally up to you.

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

Tip for folks:
disable the built-in sharing buttons.

Get a plugin if you need more buttons or something different.

Or roll your own with CSS/HTML — really very simple with CSS and use Font Awesome icons.

No theme can have every share button in existence for every user/publisher nor is this one likely to have every possible sharing button, so making your own solution may serve you better than being on a “forever” waiting list for the latest flavor of sharing button.

If you use JetPack, many additional options are there; but I hate that thing myself.

Google all the tutorials on making your own sharing buttons with CSS .. not very hard.

Try deleting via FTP.

Clear all caching if used by site/plugin/CDN.

Clear your web browser cache/history.

Resave permalinks.

Clear transients with wp-optimize.

It’s the common error in webmaster tools when changing/updating any theme, where temporarily google tries to read old pages and hits the theme folder and generates a 500 error.

Probably good to add note to this since it comes up so often.

It can be marked “fixed” and ignored in Google Search Console.

Without using plugin to load FA, one could also likely simply add this to footer.php at bottom:

<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.3/css/font-awesome.min.css">

Best to install via ftp if your wordpress install unable to unzip and create folders

Useful to read the docs for wordpress to learn how it works.
You add sidebar widgets under appearance > widgets

You have numerous errors, apparently introduced by Cloudflare. Test one of your posts with F12/console view in Chrome.

E.g.,

2www.exposingthenewage.com/:11 A Parser-blocking, cross-origin script, http://ajax.cloudflare.com/cdn-cgi/nexp/dok3v=0489c402f5/cloudflare.min.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
/wp-includes/js/jquery/jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 1.4.1
/wp-content/plugins/q2w3-fixed-widget/js/q2w3-fixed-widget.min.js:1 q2w3_sidebar_options not found!
ping:1 Application Error: There was a problem getting data for the application you requested. The application may not be valid, or there may be a temporary glitch. Please try again later.
jquery.js:2 Uncaught Error: Syntax error, unrecognized expression: unsupported pseudo: hover