Search Results for 'github'

Hi,

By calling it a class I believe I am not expressing myself properly.

What I need to do is when someone clicks n a certain element in a page for it to scroll nicely to a certain element on the page.

Something like this
http://css-tricks.com/snippets/jquery/smooth-scrolling/

or

http://balupton.github.io/jquery-scrollto/

Actually wanted to know if I can use existing code in the theme to do it, or if I had to add code to the theme, and how

Thank you

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/