2Wordpress LogoRich snippets code for Mystique 3.x

I’ve pre­vi­ously writ­ten about rich snip­pets code for Mys­tique 2.  There are also gen­er­ic instruc­tions and code for the themes twenty elev­enme gusta and thes­is.  Below is updated code for Mys­tique 3

1. The first prob­lem was with the author inform­a­tion / hrecipe sec­tion

The solu­tion:

You need a google pro­file. Your google pro­file must be linked from some­where on the page, with rel=“me”, AND the main domain of your web­site must be lis­ted on your google pro­file links.

I achieved this with the Mys­tique theme with a series of modi­fic­a­tions.

Firstly, I added the code from yoast (as shown below) to functions.php

Second, I went to my word­press pro­file page and filled in the google pro­file field with a link to my google pro­file

Third, I edited a line to author.php, again, based on inform­a­tion from yoast, but changed for the Mys­tique theme

And add the fol­low­ing

Then I edited AtomObjectAuthor.php and changed line 213 by adding rel=“author” so it reads as fol­lows

When this is cor­rectly imple­men­ted you should get a suc­cess mes­sage in the snip­pets test­ing tool which reads Veri­fied: Author­ship markup is cor­rect for this page

2. The second problem(s) were with the hfeed / hentry sec­tion and included the fol­low­ing:

Miss­ing required hCard “author”.
Warn­ing: At least one field must be set for Hcard.
Warn­ing: At least one field must be set for Hat­o­mEntry.
Warn­ing: Miss­ing required field “entry-title”.
Warn­ing: Miss­ing required field “updated”.
Warn­ing: Miss­ing required hCard “author”.

The solution(s):

Use the word­press edit­or to edit single.php

Find the code

replace this with…

A final note — Don’t just copy and paste the code from this page, as for some reas­on (I’m guess­ing char­ac­ter encod­ing) it wont work. Copy it from here and paste into win­dows note­pad. Then re-copy it from win­dows note­pad (or any oth­er basic plain-text-only edit­or) and paste into the word­press edit­or. Going via note­pad loses any hid­den encod­ing or oth­er data which causes a prob­lem so the code is treated as the plain-text it is sup­posed to be!

Got some thoughts of your own? Indulge yourself below by commenting! If you would like to subscribe please use the subscribe link on the menu at the top right. You can also share this with your friends by using the social links below. Cheers.

Leave a Reply

2 Comments

gravatarRob

Is there an update for this since the code is so much dif­fer­ent now using the atom engine?
I have tried to pos­sibly add the code with the atom calls but I am just a little unsure of how to get this to work prop­erly.

Reply
gravatarJon Scaife

Not yet as this code still works. How­ever, I will be doing an update of it all in the near future — once the issues asso­ci­ated with the migra­tion of the site have been resolved 🙂 Check back in 3–4 weeks 🙂

Reply