Only way I’ve gotten that to work is the post by email settings:
https://codex.wordpress.org/Settings_Writing_Screen

Theme documentation is great place to start in learning to use the theme; link right side of page >>>

e.g.,
https://forum.tagdiv.com/installing-the-demo-data/

I think he covered that in that post …

I’m not having this issue, which is odd. But normally you can have pagination for archives, and simply add the meta settings in Yoast to deal with that — it does work.

For home page, you should *not* have pagination from front page unless you’re using old style blog layout; and even then not ideal since it’s just duplication of all your category content.

Sorry of I’m no help on this 🙂

Sounds stupid, but you might try deactivating then reactivating the Yoast plugin; resave your permalinks, clear all your cache on server/CDN, etc.

Regardless, the theme doesn’t impact how the plugin writes to your header files with Yoast. Do you have console errors on your page? Conflict with another plugin?

Link to a page for example might help?

There is a “beta” SHIM workaround that Radu came up with; not sure if it works with Newspaper 6 yet.
Idea is that you can build your home page with VC, then use the “shim” and turn VC OFF… downside is that you lose some of the more fancy features of VC; but your site will work with high traffic. VC is a bit of a memory hog so you have to both ensure your server setup properly for memory usage; including increasing default memory in your wp-config.php file (MANDATORY!), and limit queries on your post pages (e.g., have a “most recent” items block on sidebar, not 4 categories of news modules in sidebar; don’t use mega-menu, etc.).

That is controlled by Yoast, so you may want to check the docs for that.
Perhaps try checking the “force write” option. Check to make sure those are not being added to your sitemap also, from the sitemap options.

Yeah.. there used to be a sticky post I did about moving from Newspaper 4 to Newsmag, which kind of outlined all that … but I think they “unstuck” that since they have their own upgrade guide now.

Stupid CDN caching! 😉

Ah so! Been there. Both require changing around some stuff. Kind of comes down to which look/feel you prefer. On the plus side it’s easier to upgrade and modify stuff for Newsmag from v4 and then perhaps later move to NP6 due to similarities in some of the codebase. Meaning, you’re going to have to redo your homepage either way, and reset sidebars, etc., redo some optimizations, font sizes/weights, etc.

I’d likely do Newsmag from NP4 as I did; then go from there. 🙂

Take a Sunday, put on some coffee/tea/red bull (whatever) and some nice music, and have at it. NM Much easier to use than NP4, in my lil’ ol’ opinion.

• This reply was modified 11 years by simchris.

My thoughts are only my own, I don’t work here nor speak for TagDiv, just — as you likely know — been using WP for 10 years, and TagDiv stuff since 2013, and webdev since March 1995; graphic design since (ahem) the 70s.

My thoughts on this stuff are usually just based on what I deal with on our own news portals, and may not apply to your use case at all.

I think they do have a github page where you can make suggestions and report bugs, but I honestly forget where that is for the direct link.

(In other words anything I say here is not a yes/no/maybe for theme … just commenting for the average joe/jane who might not understand what YOU are asking for and freak out they need to change all their photos. 🙂 )

Yeah. Throws me off anytime I upgrade and have to redo the widgets … and I go … um? What? 🙂

So now I have a cheat sheet of author social media links, site social links for the single sites, network links for the “entire” network, so I can keep track of the pesky who/what/where on which social link goes where.

Generally “best” to fit your images to the layout and then allow FB to bring in and optimize and reformat to fit their ever-changing systems for both desktop and mobile; e.g., 470×246 is the size FB most often actually uses for timeline on desktop; with 140×100 for smaller thumbs and 158×158 for square images taken from smaller items.

This only refers to sharing “articles” or posts with featured images, and not “sharing” photo gallery items as single posts themselves.

For our article sites we standardized on 640xXX and for our daily news sites we just to 500×375 and those sizes both work awesomely with Pinterest pins, Twitter cards, and Facebook.

Just some food for thought, not trying to step on your suggestion on any way/shape/form. 🙂

HI
it’s a “sticky” post at top of the forum(s); so you should be able to find it there as long as you’re on “page one” of each forum. It works fine with this version of theme as most of it’s related to WP optimization and not the “theme” itself, aside from hiding the visual composer code on posts, which I guess would be related to theme. One bit of the code for functions.php is to hide Yoast bar; another is for putting up a “quit it!” message for folks trying to guess your password (great to use with my suggested plugin ‘limit login attempts’); and of course the compression setting for WP from 90 to 50 should be mandatory (some folks like 60, but if you still get warnings about your images could be more compressed, try something like 45).

The htaccess optimzations are mostly intended for apache based servers (most common); and so that stuff is also included in the speed up guide from TagDiv in the docs, as that also applies to all WP installs – you need to have caching/TTL settings.

Anyway – hope that helped 🙂

<LOL>
I can honestly say I’ve been there!

One of my early tickets in this forum end of 2013 was why the review section was “missing” on my post page; totally forgot about the “make visible” button top right of post pages. Doh.

Happens to all of us, really! 🙂

I use the wp-optimize plugin to clean spam from akismet, get rid of extra drafts, optimize tables, etc. — really really helps. And bulletproof. (Of course make periodic backups and all that.)

WordPress issue, not theme issue.

If you already emptied your trash (ahem = hint!), then:

Try optimizing your database (I use wp-optimize plugin), deleting any tags created with page if unique to that page.

You may need to do additional house cleaning on your dbase if above doesn’t work.

Try going back to backup copy of dbase (good practice to backup dbase before activating new plugins!) if available.

Recommended:
https://wordpress.org/plugins/wp-optimize/

@Fudoki
thanks, totally forgot about that one … been so wrapped up in my business site, have not been fully optimizing my WordPress stuff — YES!!


remove_action('wp_head','print_emoji_detection_script',7);
remove_action('wp_print_styles','print_emoji_styles');


Check your hosting account for error log is likely best place to start if your website is totally offline. If your site is live, but you cannot login, that is whole separate issue unrelated to theme.

If your site is “overloaded” and crashing you likely will need to do couple of things
a) increase memory allocated via php.ini if not already done
b) edit wp-config.php to increase WP default memory from 40MB to 128MB (or 256MB if you are allowed on your system).

Social tab in the theme panel is for top of the page.
Social widget can be different based on page, post, homepage, etc. – more flexible.

Some folks want some stuff top of page, different things/accounts in sidebar.
Sidebar code uses hooks for counting; items for top of menu bar just for click-through.

Many of us don’t want “one for all” but location/placement specific usage.

ah… in the block setting (duh).

I think they have that set to filter out HTML since a class is being applied to that already you might end up with broken HTML by simply using HTML.

oh….
there are no gitignore files for theme, except by mistake 😉
any for the theme should actually be removed.

Anecdotal: We had it happen across three websites using Newsmag where the [category] bugs were above headline and Google News would grab those as part of headline when “scraping” the page, even though the sites have proper news sitemaps and meta data. ON some of our 10 year old sites (part of original GN beta launch!), it seems they still sometimes ‘scrape’ vs ‘pull’ which is dumb, but it’s their little ecosystem.

So you can see here, I just “moved” them down with the ‘tags’ (old skool placement!)
http://enewschannels.com/2015/06/19/scott-durfee-and-george-medeiros-of-spathose-featured-at-cory-allen-contemporary-arts-the-showroom-enc45775_123016.php/

Nothing wrong with theme – it’s just Google News sometimes doesn’t use the XML sitemaps that Webmaster tools shows having properly captured content with no errors.

Broad strokes:
1) install v4 of theme
2) restore your dbase from backup to former version.

You can’t have html in the WP titles for a post.

You can edit WP to change behavior in the templates, where what “prints on page” pull from dbase and post meta has style applied.

You can also write HTML in the text editor for posts.

You can also setup custom field, such as with Advanced Custom Fields, with a custom field for a title; then change your template to “print” that field, and NOT the main title field; then rest of site would pull the default title.

Hope that at least pointed you in some direction.

Most often issue with Cloudflare — you can find lots of comments about such issues in the forum. You should have all caching OFF and cleared before doing any updates, upgrades, migrations, etc. — otherwise you have weird mix of old/new and hence crashing of doom.

I forgot to turn off mod_pagespeed one time doing upgrade and it was a “dog’s breakfast” as my dad used to say!

You would likely need to come with custom query, then you would need to modify each module file youre using with custom query. That is just the broad strokes.

Always delete/clear cache before updates.

Always delete old theme folder and child theme folder for new theme; upload new folders to completely replace old ones. Delete old plugins completely, install new folders. NEVER OVER-WRITE UPDATES.

Always clear cache after making changes to core files when they are working; otherwise you are loading mix of old/new from server and things break.

If you’re unable to do anything — try switching to default theme, try disabling all plugins entirely; try resetting the plugins folder (see my “how to move to new theme” for a best practice way to update/upgrade and recover from fail).

Only put stuff at end of your functions.php in MAIN folder, NOT child theme. Only add things you know what they are — most being self-evident. If site crashes when loading edited functions.php, then roll back to your backup. If site won’t recover from that, then it’s 100% a caching problem.

Often for testing via FTP, I do

a) all caching and mod_pagespeed disabled
b) rename functions.php to xfunctions.php
c) drag over new functions.php
d) test site
e) if site won’t load; via ftp with window still open, just rename xfunctions.php to functions.php and it replaces the bad functions.php — total time 20-30 seconds.

Not sure any of that helps, but maybe some pointers in some direction.