[songdogtech]

Thanks for your help; this is still on a demo server, but I emailed the demo site login and password.

[songdogtech]

@braddalton, thanks, but I'm still beating my head against the keyboard with this. I converted to HTML5.

All the other post and page before_entry and entry_footer widgets work, and deleting them doesn't help with this one.

I added a before_entry hhdata widget, but both of these render above the content. Tried changing the 3rd parameter in many different ways and with the other widgets with no luck.

/** Register Above hhdata Widget Area */

genesis_register_sidebar( array(
	'id'          => 'above-hhdata',
	'name'        => __( 'Above hhdata Widget', '$text_domain' ),
	'description' => __( 'This is the Above hhdata section', '$text_domain' ),
) );
 
add_action( 'genesis_before_entry', 'above_hhdata_widget'); 

function above_hhdata_widget() {

if( 'hhdata' == get_post_type() && is_single() ) {
 
    genesis_widget_area( 'above-hhdata', array(
		'before' => '<div class="above-hhdata widget-area">',
		'after'  => '</div>',
    ) );
 
	}  
}

/** Register Below hhdata Widget Area */

genesis_register_sidebar( array(
	'id'          => 'below-hhdata',
	'name'        => __( 'Below hhdata Widget', '$text_domain' ),
	'description' => __( 'This is the Below hhdata section', '$text_domain' ),
) );
 
add_action( 'genesis_entry_footer', 'below_hhdata_widget', 11 ); 

function below_hhdata_widget() {

if( 'hhdata' == get_post_type() && is_single() ) {
 
    genesis_widget_area( 'below-hhdata', array(
		'before' => '<div class="below-hhdata widget-area">',
		'after'  => '</div>',
    ) );
 
	}  
}

The page template:

function hhdata_loop() {
global $post;

$args = array(
		'post_type' => 'hhdata',
		'posts_per_page' => 1,
		'post_status' => 'publish',
	);
 
$wp_query = new WP_Query( $args );

if ( have_posts() ) : while ( have_posts() ) : the_post(); 

//echoing custom field data

endwhile;

endif;
 
	wp_reset_query();
}

add_action( 'genesis_loop', 'hhdata_loop' );
 
genesis();

[songdogtech]

This is Focus XHTML.

[songdogtech]

Thanks, but still no luck with this:

/** Register After Single Post Widget Area */

genesis_register_sidebar( array(
	'id'				=> 'after-post',
	'name'			=> __( 'After Single Post Widget', '$text_domain' ),
	'description'	=> __( 'This is the After Post Widget section.', '$text_domain' ),
) );

add_action( 'genesis_after_post_content', 'focus_after_post', 15 );

function focus_after_post() {
	if ( ! is_singular( 'post' ) )
	return;
	
genesis_widget_area( 'after-post', array(
		'before' => '<div class="after-post widget-area">',
		'after'  => '</div>',
   ) );
}

/** Register Below HHData Post Widget Area */

genesis_register_sidebar( array(
	'id'          => 'below-hhdata',
	'name'        => __( 'Below HHdata Widget', '$text_domain' ),
	'description' => __( 'This is the Below HHdata section', '$text_domain' ),
) );
 
add_action( 'genesis_after_post_content', 'below_hhdata_widget', 11 ); 

function below_hhdata_widget() {

if( 'horoscope' == get_post_type() ) {
 
    genesis_widget_area( 'below-hhdata', array(
		'before' => '<div class="below-hhdata widget-area">',
		'after'  => '</div>',
    ) );
 
	}  
}

Page template called single-hhdata.php

function hhdata_loop() {
	global $post;
$args = array(
		'post_type' => 'hh-data',
		'posts_per_page' => 1,
		'post_status' => 'publish',
	);
 
$wp_query = new WP_Query( $args );

if ( have_posts() ) : while ( have_posts() ) : the_post(); 

//echoing a lot of custom field data

endwhile; endif;
 
wp_reset_query();
}

add_action( 'genesis_loop', 'hhdata_loop' );
 
genesis();

[songdogtech]

Hopefully you have a backup of your child theme and any customizations you made to it, because you need to upload fresh copies of all files. Your home page in Enterprise is a template file; download a new copy of it from your account at Studiopress.

Basically, work your way through these resources and follow all instructions to completely clean your site or you may be hacked again. See FAQ: My site was hacked « WordPress Codex and How to completely clean your hacked wordpress installation and How to find a backdoor in a hacked WordPress and Hardening WordPress « WordPress Codex.

Change all hosting and site access passwords. Scan your own PC. Use http://sitecheck.sucuri.net/ before and after. Tell your web host you got hacked, and consider changing to a more secure host: Recommended WordPress Web Hosting

[songdogtech]

Googling "themes.googleusercontent.com" shows that it's a CDN for webfonts that the theme is using. That means Google is slow for some reason.

Disable W3TC and the CDN you're using see if that makes a difference. W3TC may be trying to cache it or your own CDN may be conflicting.

Use developer tools in your browser to see exactly what is loading and what is timing out, after you disable the cache and CDN.

Use Firebug with Firefox, or use the developer tools in Chrome or Safari or IE.

[songdogtech]

That's really a Google issue and not Genesis or WordPress. Even with correct structured data, many people have seen their G+ image disappear from SERPs. Ask in the Google product forums.

See http://productforums.google.com/forum/#!topic/webmasters/ii64XqK2G0o

Google uses a variety of quality guidelines to determine when to show rich snippets, having properly marked up data doesn't guarantee that they will always appear in search. Also, recently Matt Cutts shared that Google was going to be cutting back on the amount of rich snippets returning in search. He also shared they were going to be tightening up the qualifications. If all elements of authorship are in place e.g acceptable profile image, profile visible in search etc and data is marked up correctly there's not much more an author can do but to keep writing, good quality content and ensure they're following Google Quality Guidelines.

[songdogtech]

That's really a Google issue and not Genesis or WordPress; many people have seen their G+ image disappear from SERPs even with correct structured data markup re: http://www.google.com/webmasters/tools/richsnippets# . Ask in the Google product forums; it's an issue or service change on their end.

See http://productforums.google.com/forum/#!topic/webmasters/ii64XqK2G0o

Google uses a variety of quality guidelines to determine when to show rich snippets, having properly marked up data doesn't guarantee that they will always appear in search. Also, recently Matt Cutts shared that Google was going to be cutting back on the amount of rich snippets returning in search. He also shared they were going to be tightening up the qualifications. If all elements of authorship are in place e.g acceptable profile image, profile visible in search etc and data is marked up correctly there's not much more an author can do but to keep writing, good quality content and ensure they're following Google Quality Guidelines.

[songdogtech]

Thanks, I did have the conditional wrong, and I didn't know there was a parameter for positioning, but no luck with either of those changes.

This is Focus XHTML, but once I get everything done, I'm converting it to Focus Pro HTML5 re: http://wpsites.net/wordpress-themes/how-to-convert-your-studiopress-child-theme-from-xhtml-to-html-5/

And this is on my dev server, so it's not accessible.

The full focus_after_post function is below, which I forgot to include earlier; is there a conflict here?

add_action( 'genesis_after_post_content', 'focus_after_post' );
function focus_after_post() {
	if ( ! is_singular( 'post' ) )
	return;
	
genesis_widget_area( 'after-post', array(
		'before' => '<div class="after-post widget-area">',
   ) );
}

genesis_register_sidebar( array(
	'id'				=> 'after-post',
	'name'			=> __( 'After Single Post Widget', '$text_domain' ),
	'description'	=> __( 'This is the After Post Widget section.', '$text_domain' ),
) );

And this is the source, which shows the widget is dumping the text below entry-content:

<div id="inner">
<div class="wrap">
<div id="content-sidebar-wrap">
<div id="content" class="hfeed">
<div class="post-9999 type-hh-data  hentry entry">
<div class="entry-content"></div>
<div class="below-hhdata widget-area">
<div id="text-12" class="widget widget_text">
<div class="widget-wrap"><div class="textwidget">
Below HHdata text in widget
</div>
</div>
</div>

[songdogtech]

Could be a font size rem/pixel bug in Chrome, re this sticky post:

Font Sizing bug in Chrome

[songdogtech]

Well, that was easy. I didn't even see that in functions.php. That works, Thanks.

[Author]

Posts