Use responsive ad code from AdSense to “fit” the spaces where it will live, automatically.

You have to unzip the theme only folder on your local hard drive (open it up, make sure it’s the theme!), not the large zip file of everything.

Upload the properly unzipped newspaper theme folder, via FTP, to

/yoursite/wp-content/themes/

login to WordPress and the theme will be there.

If you don’t see the theme on the appearance > themes page then you have not uploaded it correctly.

head is generally in the header.php file.

TagDiv speed booster is included in the /plugins/ folder with your purchased theme download from Themeforest.

Also note, that using child themes may not always be advisable as it’s a CSS redirect, and may slow down your site slightly.

Obviously you would have checked your site before/after with both Pagespeed Insights and perhaps GTMetrix to see the actual impact technically.

Funny — somebody else asked me about this the other day.

I think the trick — have not yet tried this —

a) generate critical CSS for post, critical CSS for home

b) combine into one CSS file

c) run CSS minifier to remove duplication

d) end up with one CSS block; adds some extra stuff to posts, but then you don’t get flash of unstyled text on home page, most notably for the slider (noticed this on one of our sites the other day … actually….).

Seems safest way to do that, but have not actually done it for Newsmag 3.1 just yet.

Pondering having two headers
a) for home/categories
b) for posts

but then that adds another if/then query to every page, which is bad for posts, where speed of posts is more critical than speed of cat/tag/archive pages.

So, combining then de-duping through minification seems logical solution.

Sorry for those of you just tuning in, probably waaaaay over your head — but hope this helps those who are already testing out critical CSS inclusion and moving style sheets to footer methods.

OH – one other issue we ran into is that with only doing the post critical CSS, it actually breaks the links on the grid images on the category indexes due to an apparent conflict with the little zoom effect on hover.

So, looks like the combining/minification is best solution. Doh. More on my to do list, darn it!!! 🙂

Just my two cents being a dinosaur around here:
(Sidebar: Matt Cutts no longer works at Google, as FYI, and has actually been on leave for couple of years.)

Actually more than one H1 tag is allowable as it’s only a semantic guideline. So inside a <header> section of markup you can have an H1 tag related to the “header” of a web document. Then within the <article> section of your content you can have an H1 tag for the page content/text.

For “SEO” Google actually “combines” your “title tag” with your H1 tag inside the <article> section(s) to determine the most appropriate “title element” for your specific page. They actually ignore the H1 on the logo as an alt/fallback in relation to the article/main content section; only used for semantic “importance” vs other brands/titles/names on the page contextually.

So, per Google your meta “title” and main H1 “title” on the page should be the same, roughly, and ideally your permalink structure should have the main words from that same page title.

Still, some folks get bee in their bonnet about semantic markup, screen readers, compliance issues, and general usability (UX) matters. If you don’t know what the <header> and <article> sections do in modern markup, you probably need to look into that.

Or, simply remove the H1 markup for the <header> for this and other themes you may use, if it really truly bothers you. It’s not going to ruin your placement in SERPS, put another way. Original content is still more important than this issue, the way Google looks at things.

It has not hurt our SERPS the past many years one wit. But we originate all our content and don’t copy/paste from other sources.

# — Chris.

One presumes that you did a search/replace in your dbase for all instances of http://yoursite to https://yoursite.

I did have this issue on one site, now that I think of it. It was due to opcache in php, actually.

In our case solution was:
A) upload newly named logo
B) paste in the new URL to new logo in the logo box
C) scroll down and click SAVE.

That worked.

As to being ‘unable to save’ — that is often a javascript problem. Or, on iOS Safari the internet cache needs to be deleted (for those nutty folk managing their websites on their phones!).

Also note for the favicons, you don’t need to actually put them in the theme panel. Simply having them in the root of your website public folder will be found by all mobile and desktop browsers. So, ideally you’d do a set of icons in correct sizes/formats and simply place in your home/root directory — browsers get them automatically, and always have.

Good to check the WordPress Codex (docs) on WordPress.org on how WordPress works.

But yes, you would put your full site home page URL followed by /feed/

🙂

Best to check the Jetpack forums and support site; it’s not made by nor supported by the theme and works with any theme out there, as Jetpack is made by the same people who make WordPress.

Some kind soul here might have some feedback. We had no success using either as they either had bugs or impacted site speed. But everybody has different needs.

Ideally – simply try one out and see how it works for your purposes.

Did you add https URL to your website to your wp-config.php file to show the full path to website explicitly? This is super important when changing your site from http to https, I’ve found.

Not theme related. You may want to check the Yoast support forum for this issue, as some people seem to have it on their server. See the YOAST SEO support page on wordpress.org and the Yoast website.

They answer queries in order received. Bumping the post actually keeps putting it at the BACK of the queue, not the front.

Just paste the full URL to the image into the box and then hit update.

Best to update via FTP.

use Feedzilla, log into website; delete old plugin folder in /wp-content/plugins/

upload new unzipped VC folder.

Seriously — only way to avoid pain and suffering !

To house clean old revisions, I use the free WP-Optimize plugin 🙂

There is an old thread I started way back; then updated by others work looking at (someplace in forum … don’t have link handy). Some stuff I cleverly started with TUTORIAL to make them easier to find, others not so much 🙂

Note the best one to use is the one from Automattic, as that is from the people who actually make WordPress and they use the plugin for top-tier sites like Time.com, etc. — so we’ve been using it here since Nov. 2015, and works quite well.

• This reply was modified 9 years by simchris.

Make sure you update Visual Composer also; delete old plugin folder for VC, upload new one.

Resave permalinks.

Clear transients with WP-optimize plugin.

Also, sometimes simply resaving your home page ‘page’ without any changes will reset it.

Google it. Any WP theme can be renamed just by changing the name in the style.css, and folder name.

Won’t change any of the styles, or sub-folders, or plugins, or other things like the font name, etc.

Envato cannot update the VC plugin.
You need to update via FTP to have it done properly.

This is what I did since I don’t use any logins with Newsmag

I opened this file

/theme/parts/header/td-login-modal.php

select all, delete, save; replace on server.

Not sure that will solve your issue, but I’m still using 3.1 and that removed the un-needed login css/code from my header on all pages, which was not needed and should have been an optional on/off item for theme.

All my sites are now https anyway, but seemed like something worth trimming on our sites.

Depending on theme version, also might need to disable the comments box if your site not running https.

• This reply was modified 9 years by simchris.

“official” AMP plugin by Automattic works very well with the TagDiv themes, and I’ve been doing so here since Nov. 2015. 🙂

Just need to either add the entry/ignore to the booster settings; or simply not use the booster plugin (which is optional).

Probably check to see if you created two accounts with different emails.
Also, contact ThemeForest tech support, perhaps share with them a copy of your receipt?

Be sure to explicitly put your https URL for website in the wp-config.php file; make sure you clear all caching; make sure you do a search/replace in your php dbase for all http links to change to https links for your domain, etc.

Those are usually the main things causing a problem.

you can’t do anything about bad actors from ad networks.

Most good hosts allow you to run BOTH 7.0x and 7.1x during the transitional period of phasing out 5.6 this year for most folk. Ideally you should run 7.0x for now until ALL the plugins and whatnot across the WP universe have been updated; 7.1 is still somewhat bleeding edge for most stuff.

To maintain compatibility with *all* WP stuff, best to stick with 7.0x for now, unless you have no other choice; however with 7.1x you *will* end up having to manually fix some php stuff in WP universe to work with it.

WP will soon “require” PHP 7x to work, and at that point “everybody” who is still active in WP dev should be running 7x and 7.1x.

Just a thought, anyway.

That plugin has never worked right for us — ever.

Best to use FTP, with something like Filezilla, as you can also make a safety backup of your site docs same time; remove old broken themes, etc.