UPDATE:
1) the issue of the ?rel=author in footer is no longer an issue, and Google does now prefer to just use the meta tag in the HTML head:

<link rel="author" href="https://plus.google.com/+ChristopherSimmons/posts"/>
<link rel="publisher" href="https://plus.google.com/+NeotropeNet/posts"/>

* technically you should only be adding that element at bottom if an SEO plugin not running; however we can easily comment it out in the theme functions.php file

2) I have put in a bug track on github (Issue #372) for the Yoast SEO plugin to perhaps create an additional field, perhaps Yoast Twitter ID to be able to properly embed @USERID in head, but retain full twitter URL for use on page for author box, etc.

IDEALLY: we should be able to somehow for the moment turn off the option in author box to pull the @USERID twitter ID as it’s more critical to include the correctly parsed @USERID for the twitter card for the article author, than have link in author box for twitter. Unfortunately, if left alone, we end up with a bad link of:
/site/story-permalink/@USERID … in the author boxes, which will end up generating bad not found errors for Google, which is also really bad.

*POSSIBLE SOLUTIONS* right now
(1) turn off the twitter field link for the author box in theme (I cannot locate this in the snippets)
(2) turn off *all* links at bottom of twitter box temporarily as stop gap fix; better than nothing
(3) add/register new user account data field to functions called “Twitter URL” to add to user data meta for the full twitter.com account URL – and then call this in the theme vs “twitter” field? — for the moment we’d prefer this option, if you folks have your usual nifty arrow-screens on how to do that. This way your theme will work with the huge installed base of YOAST SEO (and possibly others who follow same method of putting @USERID in the twitter field, vs the full URL).

Option #3 would be awesome, in my opinion.

For those interested in what I sent to the Joost and the Yoast team via Github bug track:
REF: http://wordpress.org/support/topic/conflict-with-user-account-twitter-data-in-themes

HI, Joost and co…

ran into one issue with Yoast and several theme devs lately.

Specifically, under each user account setup, the field for Twitter is now common to Yoast and many themes, and themes use the field to put twitter link in things like an author box.

Problem is that Yoast SEO looks for simply @NAME from the user > twitter field to print in the META.

So, this ends up doing this:

<meta name=”twitter:creator” content=”@https://twitter.com/USER”/>

however, if we put just @USER in the twitter field, we would see this in themes under things like author box

Follow on twitter:

LIKELY BEST FIX would be to come up with a new field the user account setup, like Yoast Twitter ID vs simply Twitter.

That way we could have:

Yoast Twitter ID = @USER
Twitter = https://twitter.com/USER

Since the field “twitter” is now a standard in most themes, if not WP, then it seems more logical for Yoast to either filter out the URL when it’s there to just print the @USER .. or setup alternate field for the non URL version of code.

http://wordpress.org/plugins/wordpress-seo/

Hi, as quick follow up.

Seems Yoast adds data field for Twitter and Google+ and expects to see

(user setup, per user/author)
Twitter account: @name
Google+: linktogoogle/accountname?rel=author

When the theme uses these same fields for placing in author box, it expects to see:
Twitter account: https://linktotwitter/name
Google+: linktogoogle/accountname

So….. seems either theme or Yoast will break.

Fix options:
1) use @name in user setup for proper author placement in yoast og/twitter card META; and then add new user data record for Newspaper Twitter Account (full URL)
2) or, get Yoast to update to use full twitter account – but with tens of thousands of sites using Yoast, seems more applicable to modify theme behavior at this point

1) Option to remove the Google author data from footer generated by theme, which is redundant with yoast/etc.
2) remove rel=”author” and conform with yoast and others using the full url with ?rel=author already added; but still have option to remove since redundant even without the additional rel=author added.

Right now we either have broken meta data for sharing to author’s @account in twitter/tweets, or broken link under author box — choice of two evils. And for Google author have broken link in footer for rel=author?rel=author

CONFIRMING: Newspaper theme works just fine on our install of WP 3.7.1 out today.

🙂

(sorry… having a bad day over here ….. )

HI … just to clarify I’m not misunderstanding:

the functions.php in child theme should over-ride core WP functions as normal – correct? But may not over-ride “theme specific” functions.

I think I can live with that (whew) 🙂

We also need the functions in child theme to work.
This is mandatory to enable custom over-rides for the site, turn off functions in things like Yoast for the menubar, specify custom optimizations, etc.

Child theme functions.php must be enabled for this theme to propagate both professionally and for the WordPress community to support it – period.

This includes over-rides for removing “versions” on javascript and CSS and font calls, removing RSS enclosures, removing error messages at login hack attempts, changing the WP post revisions interval and numbers, etc., etc.

This is one of the core functions (pun intended) for having a child theme.

This may mean looking for another theme provider, after all, if this core function support is removed. I’m already having to do couple of hacks on every version for things still not fixed, and which are *still* not yet defaults (like author byline on post … why should this be optional by a hack?).

C’mon folks. Time to clean up some of the BASE LINE functions of the theme before getting too tricky with some of the other stuff with galleries, or sliders, or whatnot.

in fact …. 3.7.1 just came out …..and so far the world hasn’t exploded …

Also, since our author URLs already include the rel=author, your code ends up doing this:

https://plus.google.com/102627062589158403110?rel=author?rel=author

in the footer

• This reply was modified 12 years by simchris.

Hi, usernick/Claus (Santa!!)
don’t know if this helps (I am backing up my server, and killing time here tonight)

you can turn off comments under the wordpress control panel once logged in, left side menu:
> settings > discussion

once you turn off the option for people to leave comments you should no longer see a comment box at bottom of each post (all WordPress setups work this way, it’s not related to the theme).

Basically uncheck the boxes under Default article settings

[ ] Allow people to post comments on new articles

Then it should be gone on your post pages. 🙂

(I usually also uncheck the other 2 items; basically all 3 “default” items on sites where comments are not wanted.)

Hope that helped.

Chris 🙂

• This reply was modified 12 years by simchris.

@arneg ..

not sure if this will help you:

It’s included in the /theme/includes/plugins/revslider.zip
this is one of the items the theme asks you to install when you first set it up.

So, if the auto-install doesn’t work, you could unzip that and then upload manually via FTP, presumably to the /wp-content/plugins/

Chris

Hi,
I updated one of our two sites using this theme to 3.7 today and works 100%.

Still waiting on the bug fixes:
1) title links on posts/ indexes should *not* be linked (they are now; bug)
2) featured image top of post 700×409 not linked (should not, makes Google news skip image)
3) WP saying “1 update available” even though all plugs/theme up to date (gremlin!)

Otherwise works perfectly.

We’re using child theme for functions and css over-rides on dedicated server for our sites.

• This reply was modified 12 years by simchris.

Hi,

I am starting to get annoyed by “dohuytoan” trolling for clients here ?

The person keeps posting “offer to fix error” when many of the posts are not error related, but queries about how to implement something.

I am adding a “vote” here to tag those as “spam.”

Chris

HI, Radu
fyi, this same “bug” makes the site pages, AND archive pages (e.g., category, tag, archive) clickable also, which should NOT be the case, not just the post page.

I can confirm this causes Google News to skip the featured image, which is not the behavior we want. The “featured” or main image should be the primary, and must be unlinked.

How can I unlink the featured image for the post page ? The setting in the config panel is set as “no link” vs lightbox, but I don’t think that applies to the post image on the post page.

We need to fix this one ASAP.

w3C cache does implement many of the tricks for optimizing your site. Note you can also do some of that yourself using your htaccess file and make sure you optimize the heck out of your featured images (mine are about 16-24kb max for 700×406). There are quite a few great articles out there on implementing some of the W3C stuff without using the plugin, if you only want to test bits of that. Also setting up an Amazon CDN (S3+cloudfront) and hosting your JS/CSS and fonts there will also speed up your site. You can’t entirely rely on the “theme” to manage your site optimization, as a bunch of that is related to hosting, optimization of images, and minimizing using plugins and fancy jetpack stuff (basically anything that calls out to another site slows yours …). Putting more than two ads on the page from AdSense really slows it down, using anything connected to facebook or twitter “on the page” slows it down. Etc.

This may also account for the error when clicking on the Pinterest share button not transferring the featured image, as I believe they “scrape” that and also look for “unlinked” images !

sorry…. using v 1.6 for everything, in case that matters.

🙂

Actually, Marius from tagDiv *did* put the instructions in his reply to the original query. So far everybody at tagDiv has been doing pretty well in replying and responding to fixes for a work in progress. They are doing a tremendous job; and I particularly admire them for doing a very hard thing with modern responsive design — I know, we tried to build our own similar to this recently and literally lost some hair over it. Even for a static B2B site we’re redoing (our main site that pays the bills), dealing with responsive + HTML5 + PageSpeed + CSS/js optimization is a nightmare to “do it right.” I’ve suffered a LOT of poor coding, bloated frameworks on top of WordPress that get abandoned or won’t update, custom panels that break, and hideous custom hooks that modify WP dbases with additional fields that are not needed, and won’t go away when changing themes, etc. — So far these folk are doing a GREAT job, in my opinion, so be sure to show them the love whenever possible. Just sayin’.

I would also recommend adding a folder called /mods/ in your root for the theme, and put backups of your mod files there (meaning the files you make mods to – put the MODIFIED versions in there). This is a handy reminder when you go to do a manual update via FTP, to go “oh. duh. I need to over-write the new files with my mod files…”

Obviously, child theme support for these elements via functions.php would be preferable, but I haven’t gotten that far.

• This reply was modified 12 years by simchris.

look in

/theme/includes/app/modules/

open td_module_1.php

uncomment: $buffy .= $this->get_author();

=============

it just occurred to me this morning that one could uncomment the same element on other modules.

Presumably with the hook in there, they could add this as an “option” toggle as they do with the get_commentsAndViews …

HI, iOSPortalSK
you need to comment out the line in the module as noted in Marius’ prior reply, at least for now. Note this mod only works on adding byline to the post page, not any of the “modules” for the indexes.

See his prior image, above in this thread

–snip–

Just de-comment this line. In Module 1 is for post. http://screencast.com/t/kB49r8NgH

-/snip–

I went ahead and modified the module 1 file and it works. Thanks.

To clarify:
for us, we MUST HAVE the byline on the actual posts … regardless of any functionality on categories, tags, homepage, or other blocks.

ALL articles should have byline at top as the author box traditionally is intended to be an “also ran” for a mini-bio about the author, and not to identify who authorized the story. With a 3,200 word article, the byline needs to be at top to clearly identify the AUTHOR of an article.

Willing to pay to get this done!

Chris

HI, all
this really should at least be a standard “on” option for the posts page, if nothing else, since ALL newspapers post a byline for a story, and this is the main point of this theme!

I realize you have lots of other stuff on the to do list, but I’d move this one up a little higher as any “real” magazine or newspaper site that isn’t being setup for content spam MUST have bylines for each article.

Thanks! 🙂

Hi, Radu
awesome. I think a “knowledgebase” area with the answers to most common tricks/tips, and “hacks” (“mods”) would be welcome. I know when I was going to post something about the byline there was no way to “search” for any prior fix, and some things like the fix you gave me for using a pre-existing data field for the “reads” counter would be great to have in such a knowledgebase … and it saves you from answering some of the same questions over and over 😉

You are way ahead of the crowd, however, in answering most replies timely and accurately, and using screen shots with arrows — really great work on all of that.

Chris