Richard D'Angelo

NOTE: There are no additional headers, and I’ve changed the “From” feild setting to an email address on my domain to get rid of that configuration error. It still doesn’t work: says sent succesfully but I never get the email. Not even in spam. Understand this just randomly started happening out of nowhere. Not after an update or any changes. Any ideas?

• This reply was modified 7 years, 10 months ago by Richard D'Angelo. Reason: Changed Mail Settings to no Avail

Oh ok is that the one? Yes that snippet is in my child functions.php but after the update I needed to change “TC” to”CZR”. Turns out I actually prefer the metas on the top so I think I’ll just remove that snippet. I’m assuming that will reverse the problem.

Update 3.4.33 completely resolved the issue for my site and all modifications in my child functions.php work just fine. Thanks for the helpful input everyone, and big thanks to @nikeo and the Customizr team for so diligently fixing all bug reports. Much appreciated.

I’m marking this as resolved.

– RJD

• This reply was modified 8 years, 1 month ago by Richard D'Angelo.

Nikeo et al. are working on a bug-fix release and said it will be available later today (“a few hours”, per Nikeo a few minutes ago in another theme update bug report support thread). They always fix these things quickly and comprehensively. If anyone has new bug fixes to bring to their attention now is the time. <b>Looking forward to the update, thanks Customizr Team.</b>
– RJD

AWESOME! This is what I’ve been waiting for. I’m great with schema microdata – not so much with PHP. Can’t wait to see the Cookbook grow!

As usual, George, your support for this plugin is as good as or better than any other plugin author I’ve seen. Well done!

– Richard, Owner
CraftPro Contracting Home Improvements

Excellent work, per usual. Thanks George!

articleSection isn’t an accepted itemprop of the ‘WebPage” itemtype in schema.org structured data. You would need to replace it with something else that makes sense. “About” maybe? Check out schema.org/WebPage for the accepted itemprops. Then you’d have to change articleSection to one of those.

No problem, George – this is definitely a 5-star plugin. Thanks for being so proactive about the support. I’m very, very much looking forward to the customization code snippets wiki! Keep us posted. That would be phenomenal.

The new update is excellent George. Your support of this plugin is fantastic. Congrats – it’s an excellent plugin and I couldn’t be happier.

I’ve tested two instances of the same itemtype in a validator and it “passes” but I still highly doubt it’s a best practice. I’ve been able to accomplish what I need with the code I pasted in my 2nd post in this thread: it eliminates the Article itemtype on pages, which is what I was looking for. And my pages are already marked up with the WebPage itemtype via my theme, which I suspect is the case for most themes (either WebPage or BlogPost, from my experience).

If you can figure out a lightweight solution to make the itemtype customizable (for example, I use ContactPage for my business’ “Contact Us” page) and to make the Schema itemprops customizable that would sure be cool.

But really I think as it stands right now with a few PHP hacks (maybe you could start a collection/wiki like you suggested? Many people would contribute I’m sure) it works well. I mean even Porch.com uses your plugin and they were started by two former Google guys so AMT does what it needs to do. The ability to customize would be nice but I understand you want to keep it simple and lightweight so, of course, it’s your call.

Sounds great George thank you! Quick question: I use the Customizr theme (www.presscustomizr.com) and it already marks up every post and page with the WebPage itemtype in the body tag (in order to markup breadcrumbs – as far as I can see that’s the only reason). I wonder if 2 instances of WebPage would be a problem? I don’t think it would be. Thoughts?

It is in my plans to create a webpage/wiki that contains a collection of snippets that customize the plugin’s functionality in various ways. Users will be able to use them as is or as a starting point for their own customization.

That would be incredibly useful! Looking forward to seeing something like that. I’m surprised no one has published any such snippets already, because there is a lot of customization possible if one has the PHP coding ability.

About your suggestion, you are absolutely right. The main object type should be customizable and also automatically setting posts to Article and pages to WebPage makes a lot of sense.

However, this modification would possibly require the replacement of the ‘articleBody’ attribute with the ‘text’ attribute which is common to all CreativeWork derivatives.

Ahh ok. I didn’t know itemprop=”articleBody” was hard-coded (for lack of a better word) and yeah that isn’t an attribute of WebPage. The “text” itemprop would work just fine. Sounds like you’re really on top of it. Thank you for taking the time to respond!

If you have any resources/links for me re: customizing the Schema placement I’m all ears. If not, feel free to mark as resolved and thanks again for your speedy reply.

EXAMPLE #2 on the plugin description page is an example of what I’m looking for. Currently am using that filter to apply the metadata to an array ‘post’ and ‘jetpack-portfolio’:

function limit_metadata_to_post_types( $post_types ) {
    return array( 'post', 'jetpack-portfolio');
}
add_filter( 'amt_supported_post_types', 'limit_metadata_to_post_types');

Still I’d like to have more control of the Schema and any help in the form of filters would be appreciated. If I were more fluent in PHP I could write them myself but, alas, I’m only a home improvement contractor who dabbles in web design.

I had the same problem:
“Warning: preg_match_all() expects parameter 2 to be string, array given in /home/content/72/9209272/html/blog/wp-content/plugins/jetpack/class.photon.php on line 91” at the top of the page.

QUICK FIX
Go to Jetpack settings and disable Photon until Yoast fixes the problem with a new update release. The warning goes away.

Found the code in the PHP file – deleted it, and fixed it. Sorry for the bother.