Tip:
you can actually just put your set of favicons for various devices in the root of your public website and browsers look for them there automatically. So, if you make a classic .ico, .png, and set for Apple format, just put them in your public root, and you never have to worry about it.

It’s not yet officially released to work with current version of TD Composer and Newsmag.

I think they will include that option with next release.

Prior version of TD Composer *does* work with Newsmag 3.1x as we use it on *all* our sites with zero issues.

Use F12/inspector in Chrome to find the style classes using the selector tool. 🙂

Usually you also need to first change to different theme from WP admin panel; then change theme name in style.css, change folder name; log back in, then change theme to the new theme name from WP panel.

You can’t just edit things randomly via WP editor, as it appears you might have.

Worst case, just delete the theme folder for newspaper from the /wp-content/themes/ folder, and reinstall; then use correct procedure for changing theme name.

Good luck!

You need to change the name of the theme in the style.css, using a text editor.

Best to edit these things on your PC, then upload via FTP; then if you break your site, you can just undo the change you did.

Probably best bet right now, is to reupload the original file(s) you tried to edit via FTP.

Not the fault of the theme or theme company if you break your site in the way you have.

(( I don’t work here. ))

Just search/replace fonts in style.css – which is what I do. 🙂

Not really part of the theme … you might check the Apple help support on this, as iOS does this for all content which has proper modern article tags on pages and tries to do this for ALL article content based on the number of words and content mix — this helps comply with visual impairment (section 508) laws, etc.

You likely need to go explore the Apple Developer info, and the related topics on Google from the past few years. This has nothing to do with the theme.

Ref:
https://developer.apple.com/library/content/documentation/Tools/Conceptual/SafariExtensionGuide/WorkingWiththeReader/WorkingWiththeReader.html

https://www.google.com/search?q=wordpress+stop+safari+reader+mode&oq=wordpress+stop+safari+reader+mode

(( I don’t work here. ))

Yes. Most of us basically take the mods, add them to our own WP plugin to avoid any issues with theme updates. For some stuff we edit the core files, and keep track of that and then make same changes after next update.

There is a theme hook I think to “insert code at end of the post” — but if not, plenty of plugins that do that. By default WP supports inserting stuff “after the post” which is how most plugins are able to do that.

If you figure out the function, you could make your own plugin, also if not wanting to edit the theme files.

Still, good to learn how to edit core files, and track that, for stuff like minification, removing hooks to things not used, moving to web-safe fonts, or whatever.

Anyway – food for thought 🙂

Yoast is not the de facto expert about SEO, only one purveyor, and NOT always right. We’ve been doing it since 1995, long before the Yoast crew ever saw a web browser; we were the #1 result on Yahoo for a decade under “keyword optimization.” But whatEVAH. I give advice, not everybody gets it. It does *not* hurt your SEO either way, as the CONTENT, and the title, description first 185 characters, sub heads, outbound organic links, inbound organic links, referential content, and ORIGINAL CONTENT are what help SEO.

Again, search engines KNOW the difference between modern DOM markup for sections of pages, and KNOW what h1 does where. A logo h1 in header container is not treated as superior to h1 tag for content in article container.

SEO = “search engine optimization” — not “website optimization” — so, Google, Bing, Yandex, etc., all know how to read modern HTML5/DOM/markup.

Just FYI anybody reading this thread later.

Matt Cutts addressed this in video in 2009, although he is no longer with Google.

Google webmaster central help forum has addressed this multiple times, including this answer on this same topic from Dec. 2016:

We don't treat HTML5 differently & having multiple H1 tags on a page is fine. Be reasonable when using them, use them where they make sense. There's definitely no penalty for using H1s.

Don’t assume the sky is falling just because some ancient article tells you some bad info about pre-HTML5 era code and modern DOM usage. Modern code is very very different from 20th century webdev. Modern code has markup and sections to define a header from a footer, from an article section, etc. (for instance, Apple uses the article section on iOS to make an ‘easy to read’ version of page available and for SIRI to read).

Feel free to change stuff if you feel strongly about it, but don’t presume that Google, Bing, Yandex etc. care one way or another. Usage on the logo is correct in this context as it’s unrelated to the content SEO for the actual page content.

Hope that helps somebody as this comes up on every theme forum these days.

Kind of like the people who still freak about about the srcset attribute

Use F12/inspector in Chrome to run audit of what is loading.

Often it’s something from an ad network, or Google having issues if loading ads, or Google fonts; or if trying to pull “likes” from Facebook, or loading dynamic elements for weather box, etc. — anything loaded from ELSEWHERE can slow down or cause “perpetual loading” since it’s not in fact, loading, but only running a fetch request.

Some tweets cannot be embedded.

Generally you have to embed the URL for tweet into the visual editor mode for creating post (*not* visual composer; the visual editor mode when making a new post), not text editor on the post box when creating a post. You cannot embed them using a text box, such as in sidebar, or using the text edit mode of the editor on the post page.

• This reply was modified 9 years by simchris.

Not really theme related. You probably need to contact your hosting provider, as those settings are based on your server, and local site and nothing to do with WordPress or the TagDiv theme. Ideally, they should be able to tell you the correct settings.

Also note you cannot control time to live for browser caching of images hosted elsewhere, such as loaded off FB, ad networks, content loaded from another site, etc. Cache control headers will only help with locally hosted content on your server alone.

(( I don’t work here. ))

• This reply was modified 9 years by simchris.

1) couple of ways:
a) add a filter in WP to add text at end of the post meta for every article; would need to google that; as you’d add a bit of code to your functions.php

b) use ACF – advanced custom fields; create a field, with default text, which you could customize per post; then insert shortcode for the custom field in your theme template(s) at bottom of the post loop

(( I don’t work here; just couple of ideas. ))

Are you using paragraph <p></p> tags?

Also note with modern HTML and document markup, you can have more than one H1 tag in different areas of the page, such as the explicit header area and expicit article area. With modern code mark-up, HTML5, etc. all modern search engines understand the difference and there is no SEO penalty. Meaning, the H1 in the header area identifies that the logo is the primary header element related to the site vs any of the navigation links, and is primary link, such as back to home page. In the article area, the H1 must match the title for the page/post as close as possible, and should be the only H1 within the article section for best placement.

Some people freak out about this without actually exploring how modern markup works. So, in case you see this in forum search – chill, baby, chill ! 😉

First, useful to look at actual ‘page source’ for a created post. If the page being loaded has a background in the HTML, then it’s there for everybody, not just one browser or another. If you write the word “puppy” on a page, it’s there for every browser. The only reason and image doesn’t load from one browser to another would be caching; meaning if one browser loaded the old photo yesterday, you change it, and still loading old image today in ONE place, it’s not the website or the theme, but caching someplace.

I don’t work here, but that has been my experience. Generally best to test site with Chrome, vs Firefox, as FF sometimes has major compatibility bugs with the rest of the known universe which you can only address by doing an update to FF to see if the bugs fixed.

I find it useful to
a) go through the tutorials here
b) go through EVERY admin panel to see what’s there

Sorry if that didn’t help. Just some input 🙂

We’ve all been there. so hang in there!

LOL … I just went to a company website to get their contact info for a follow up, kept scrolling down, would see the footer links for second, then more stuff would load, scroll down, scroll down… more stuff — had to get five sets of reloads of full length page just to see the footers. Ugh. Man I hate that!!

I am not arguing one way or another on the idea; just saying my personal vote would be No. (or, Hella no!) 😉

I think from the theme panel under post settings …

So, your Google search console account shows no errors for your current sitemap?, and you have no F12/console errors for the skipped page?.

Theme doesn’t control sitemap; so if your Yoast sitemap is working (did you test it via search console and in browser?).

Then should work. So, can’t be of much help without more info.

Good luck!

(I don’t work here; but I’m out on this one. Sorry no help.)

• This reply was modified 9 years by simchris.

I vote ‘no’ as I hate ‘infinite load’ sites as they often crash mobile devices, and lock up desktop version waiting on ads to reload again. I personally stop going to such sites (try Automobilemag.com on an iPad to see what I mean!).

If it matters so much, simply build a script that triggers ajax load of “next post ID” when the scroll bar hits a certain target. Or, try one of the many canned solutions already out there …

e.g., https://wordpress.org/plugins/ajax-load-more/

(etc.)

my vote = NO

Good start is reading the tutorials in the theme docs section here for tips on ‘speeding up your website’ — and obviously increasing the RAM for WP is cruicial, the php max execution times and max input vars (on your server, check the php settings panel for your domain!); you change the default RAM for WP in the PHP settings **AND** in the wp-config.php file.

Often issue with a bad advert loading which has invalid HTML breaking the whole div/include.

Also, good to test site for console errors and fix those first:

JQMIGRATE: Migrate is installed, version 1.4.1
(index):1 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700
williamsonsource.com/:1119 school=
williamsonsource.com/:1120 tag=nashville-armory
williamsonsource.com/:1121 section=news
(index):1 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700
content-init.js:2 Uncaught ReferenceError: zait is not defined
at content-init.js:2
(index):1 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700
service.js:8 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700
commitMount @ service.js:8
osd.js:22 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700
nc @ osd.js:22
service.js:21 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700
o @ service.js:21
service.js:16 Failed to decode downloaded font: http://fonts.gstatic.com/stats/Roboto/normal/700

We used to use it with Newsmag, but then early 2016 we had a lot of problems with it. Not sure if those got resolved. But, it does work just fine with Newsmag. You might have to remove the original comment # element from the author template, but otherwise when it worked it worked great.

We have since joined many sites in removing comment options as mostly spam, in our case.

Also, try re-submitting your sitemap to Google via search console, recommended after major theme change. Check for errors, or pages not able to be indexed.

Check your not-indexed post with F12 in Chrome/console for errors.

Obviously make sure you disable all extra plugins, caching, clear caching; only use Visual Composer -or- TD Composer *not both* with new theme. Any ‘hacks’ you made to core files in 7x might have to be redone/changed for v8, etc.