Forum Replies Created
-
AuthorPosts
-
emmtreParticipant
Nathan found the cause of the problem with the error message and the strange microdata markup.
<main class="content" role="main" itemprop="mainContentOfPage" itemscope="itemscope" itemtype="http://schema.org/Blog">
The Microdata Manager plugin by Brad Potter is not compatible with the new Gensis 2.2 version.
emmtreParticipantThanx Nathan! Keep up the good work!
Please add me to the GitHub repro and I can test on one site where we have a problem and conflicts now. I have the same username on GitHub as here. Or you can get my email via the ticket I filed yesterday with reference to this thread.
I tried to look at the conditionals in the code but I can't figure out what's going on. I get various markup for different sites. I thought it was because of using custom Genesis loops or custom fields and query_args with the Blog template.
(I know Bill Erickson says "Don’t use the Genesis blog template" but I sometimes do instead of using category pages...)
But that's probably not the reason since I have other sites with more or less the same set-up. But the Genesis child themes are different. If you want I can file a ticket so you can have a closer look at one site with these markup errors.
<div class="content-sidebar-wrap"> <main class="content" role="main" itemprop="mainContentOfPage" itemscope="itemscope" itemtype="http://schema.org/Blog">
Is it still ok and safe to use the Microdata Manager plugin by Brad Potter with the new Gensis version even if it hasn't been updated for over two years? The plugin is easy to use to set microdata markup like AboutPage or ContactPage.
emmtreParticipantWhen using the Genesis Blog template for blog pages I get the following error message.
Google doesn't recognize the property mainContentOfPage for an object of type Blog.
<main class="content" role="main" itemprop="mainContentOfPage" itemscope="itemscope" itemtype="http://schema.org/Blog">
Is this a known problem or something that also can be fixed?
emmtreParticipantMany thanx again Nathan for your quick reply! I'm looking forward to the fixes in 2.2.1.
Regarding breadcrumbs Google recommends more extensive markup for mobile search.
https://developers.google.com/structured-data/breadcrumbs
Here is an example.
<ol itemscope itemtype="http://schema.org/BreadcrumbList"> <li itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> <a itemprop="item" href="https://example.com/arts"> <span itemprop="name">Arts</span></a> <meta itemprop="position" content="1" /> </li> › <li itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> <a itemprop="item" href="https://example.com/arts/books"> <span itemprop="name">Books</span></a> <meta itemprop="position" content="2" /> </li> › <li itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> <a itemprop="item" href="https://example.com/arts/books/poetry"> <span itemprop="name">Poetry</span></a> <meta itemprop="position" content="3" /> </li> </ol>
emmtreParticipantAnd can we expect full http://schema.org/BreadcrumbList microdata markup?
emmtreParticipantThanx for your comments Nathan!
1. Could be but according to W3C "the itemscope attribute is a boolean attribute" and some people get errors.
http://www.w3.org/TR/microdata/#attr-itemscope
2. The problem is that http://schema.org/WebSite is added to all pages in the <head> and not only the homepage.
If you put the markup in the <html> tag there are standard hooks that can be used by plugin developers.
And since other plugins like Yoast SEO and WPSSO puts the microdata in the <html> there are now conflicts.
emmtreParticipantAnd why is itemtype="http://schema.org/WebSite" placed in the <head> tag on all pages?
Shouldn't the homepage be "Blog" and other pages/posts be "Article", "Products", etc.
emmtreParticipantAre StudioPress going to fix this? There are itemscope="itemscope" all over.
And why are there schema.org microdata markup in the <head> tag?
Shouldn't the schema.org microdata markup be placed in the <html> tag?
When using Yoast SEO and WPSSO plugins there are now conflicts.
November 20, 2014 at 12:45 pm in reply to: Remove rounded corners on search input area on IOS #132303emmtreParticipantI'm using this on some sites.
button, input, select, textarea { -webkit-appearance: none; -webkit-border-radius: 0; } input[type="button"], input[type="reset"], input[type="search"], input[type="submit"], input[type="text"], input[type="textarea"] { -webkit-appearance: none; }
emmtreParticipantThere is no documentation available yet for the Genesis Framework extension in W3 Total Cache. But StudioPress would write one and some tutorials if there is enough requests. So please chime in and send a request to StudioPress support by email.
emmtreParticipantAnyone?
emmtreParticipantI have done that several times! But I only get bad excuses as answers. So I hope someone else at StudioPress reads this. Seems like Rainmaker is getting all focus?
emmtreParticipantWell some of the themes are missing the change log info in the read me files and if they exist the info is not complete. And then there are silent upgrades of the themes without any change of the version numbers. So this is definitely something to improve for StudioPress. There are also themes that have been updated (StudioPress demo sites) but not availible for download.
emmtreParticipantAny idea what to change if you only want one page before and after current page to save space on mobile devices? Is it ok to just remove the -2 and +2 links in the code or do i have to change some other parameters and code as well?
//* Add the pages around the current page to the array if ( $paged >= 3 ) { $links[] = $paged - 1; $links[] = $paged - 2; } if ( ( $paged + 2 ) <= $max ) { $links[] = $paged + 2; $links[] = $paged + 1; }
emmtreParticipantAnd the winner is genwrock! You had to place the single quotes outside the comma separated values. Many thanx!
'category_name' => 'blog, quote, video',
emmtreParticipantThanx genwrok I have not tested with singel quotes outside the category IDs.
'cat' => '1,7,10',
emmtreParticipantYes but you should be able use comma separated values as stated in the WordPress Codex and it does work with the Genesis built-in blog template but not with the front-page template.
And you can use 'category__in' instead which accept an array of values but then you have to change all categories since this doesn't show any posts from sub-categories (children).
I was just qurious about how others have solved this issue since it will require a lot of manual work to change all categories for all posts.
And it look like genesis_custom_loop_args will accept comma separated values for' category_name' but they are stripped by some internal format and sanitize functions in WordPress.
I will find a solution with genesis_custom_loop since I need the front-page template to also be able to display widget areas with other post categories like 'news' on the front page
Thanx for the help!
emmtreParticipantSummer, yes you should definitely go testing yourself since you can't use an array with 'cat' or 'category_name'... Then you can try to add categories to 'cat' or 'category_name' just by adding them separated by commas as stated in the WordPress Codex. And I sure do know that 'cat' requires the category ID (number) and 'category_name' the slug (string). My testing environment is a freshly installed WordPress 3.9.1 and Genesis 2.1.2.
remove_action( 'genesis_loop', 'genesis_do_loop' ); add_action( 'genesis_loop', 'site_front_page' ); function site_front_page() { global $paged; global $query_args; $args = array( 'category_name' => 'blog', 'quote', 'video', 'paged' => $paged, ); genesis_custom_loop( wp_parse_args( $query_args, $args ) ); } genesis();
emmtreParticipantI have done some more testing and can only conclude that the genesis_custom_loop doesn't work with the latest versions of Genesis and WordPress.
You should be able to add categories by adding them to the end of the parameter list (separated by commas) with 'cat' and 'category_name' as stated in the WordPress Codex.
When used with the built-in Genesis blog template and custom fields it does work as expected with several categories but not with a custom front-page.php or home.php template.
The 'cat' and 'category_name' only accept the first category in a list (separated by commas) due to some problem in WordPress with the format and syntax for integers and strings as argument.
From the php error code it seems like WordPress doesn't accept integers or strings anymore in the parameter list du to some internal format and sanitize functions in WordPress.
But 'category__and' and 'category__in' does work as expected with several categories since the parameter list is in an array with all the category id's separated by commas.
Another problem I also discovered with the genesis_custom_loop was that the sticky posts didn't work in the custom front-page.php template.
http://codex.wordpress.org/Class_Reference/WP_Query#Category_Parameters
I have not used pre_get_posts to exclude categories before in a template but I will give it a try. Thanx for the suggestion and link.
emmtreParticipantThis is really strange. When I use the argument and the plus "+" operator for displaying posts that have both the 'blog' and 'quote' category all posts that have either the 'blog' or 'quote' category is displayed instead? There must be a logical error somewhere in the latest Genesis version?
remove_action( 'genesis_loop', 'genesis_do_loop' ); add_action( 'genesis_loop', 'site_front_page' ); function site_front_page() { global $paged; global $query_args; $args = array( 'category_name' => 'blog' + 'quote', 'paged' => $paged, ); genesis_custom_loop( wp_parse_args( $query_args, $args ) ); } genesis();
-
AuthorPosts