Forum Replies Created
-
Posts
-
Try adding your page slug as a pagename parameter to the query args. Replace sample-page with your page slug:
'pagename' => 'sample-page',So this:
$args = array( 'thumb' => true, 'post_type' => 'post', 'author' => '16', 'paged' => $paged, 'posts_per_page' => 8 );Becomes this:
$args = array( 'thumb' => true, 'post_type' => 'post', 'author' => '16', 'pagename' => 'sample-page', 'paged' => $paged, 'posts_per_page' => 8 );Looks like you just need to clear the floats for it to display after all the floated elements. Try adding this bit of CSS:
p.more-from-category {clear: both;}It sounds like Disqus requires the default WP comments to be displayed in order to display Disqus, and as they mention, it will show default WP comments while the page loads then it will be replaced with Disqus.
You can probably hide the default comments section with CSS to prevent it from showing in the browser while the page loads:
.entry-comments {display: none;}Looking at your site and all I'm seeing is Disqus. Not seeing what is in your screenshot or any remnants of the default WP comments.
Try adding this to your functions.php file to remove the genesis_get_comments_template action:
remove_action( 'genesis_after_entry', 'genesis_get_comments_template' );You have this block of CSS in the .footer-widgets section which adds extra padding to the 1 and 2 widgets but none to the 3 and 4 widgets:
.footer-widgets-1, .footer-widgets-2 { margin-right: 40px; margin-right: 4rem; }Remove that bit of CSS or add .footer-widgets-3 and .footer-widgets-4 to that declaration so they all have the same padding.
No worries. I enjoy trying to figure out strange issues like this that seem to have no rhyme or reason. It's always just a process of elimination.
We can tell what is active and being loaded by looking at the source code. We can't know what is not active. Your source code is clean right now (except for the stray quote I mentioned earlier) but as @anitac mentioned, there could always be something loaded in the backend through PHP (a hack or other bad code) and we can't determine that without getting into your account.
Very odd. I see no plugins are active now, but doing an Inspect Element on your page still shows two <body> tags. Again, strangely, only one <body> tag is in the actual source code.
I noticed that your div.footer-widgets and footer.site-footer are outside of the div.site-container when they should be inside. Don't know if this is causing the issue (it shouldn't), but it is incorrect.
Did a W3C validation and noticed a stray quote in your "Track with me" text widget code, on the Google+ link, in the img element after the closing slash. Remove that quote at the end and see if it has any effect:
<a rel="author" href="https://plus.google.com/u/0/+RandallRRussell/about"><img src="http://randallrussell.com/wp-content/uploads/2014/03/randall-russell-google-48x48.png" border="0" alt="" /"></a>Both sites are still showing active plugins. Also, both sites (only on PC) show two body tags when doing an inspect element, but not in the actual source code, meaning the browser is adding that, usually due to invalid HTML, or javascript after page load.
Each of the sites have an invalid body tag of:
<body style>
Followed by a<body>tag with no classes.Your main site has the
<body style>tag in the middle of the<head>which is then closed by the browser. That is followed by code that is supposed to be in the<head>, but isn't, after the<body style>tag.Your other site has the
<body style> tag followed immediately by the<body>tag.The common plugin I see on both is the a10-imaio plugin. I know you've said you deactivated it, but it's still showing active, so be sure to deactivate that plugin and clear any caches.
Has to be the <div> in the <head>. You can't do that. The browser, some at least, will think that is the beginning of the <body>. Looking at the source on a PC, you'll see there are no body classes are being added because of that.
Found the issue...
Different browsers on different OS's can sometimes ignore bad HTML.
The problem is with your Facebook code. Viewing the source, you have a
<div>within the<head>section. This is creating two body classes when it's rendered by the browser and Genesis relies on adding body classes for colors and layout. While mobile browsers, and apparently on Mac browsers, overlook this error, it breaks on PC browsers.The offending code is this:
<div id="fb-root"></div>It's probably in the Genesis > Theme Settings > Header Scripts section. Remove that <div> and the <head> won't end prematurely and should render properly.
Edit: If it's not a script added to the theme settings, it's probably a Facebook plugin of some kind. If so, deactivate any FB plugin you have.
