Forum Replies Created
-
Posts
-
Fixed it. The answer makes total sense now that I step back and look at it again.
I was defining the recipes_post_image() function inside the seasoning2014_archive_query() function. The problem is that the seasoning2014_archive_query() gets called each pre_get_posts action.
The second time that happens I was defining the recipes_post_image() function for a second time, causing the error.
I know, that's what's crazy about it. If I remove those lines of code I don't get that error, but then I dont' get the image I want either. Those lines are only meant to swap out the featured image size. Maybe if there's another way of doing that, I can circumvent the problem.
I've created a gist, thank you for taking a look:
TCD functions.phpThanks Brad! I attempted using that but couldn't get the crumb to display even still. Likely, I'm not adding the new argument to the array correctly.
Hi Susan, thanks for checking in. I actually just posted this is a help for others who may be wanting to create conditional style sheets. I thought I had marked it as "Not a Support Question", but apparently the system doesn't really account for that very well, or maybe I misunderstood the purpose of that option. We can always mark it as "Resolved" if that's the proper protocol.
... Except that it's not resolved. It's still an issue. I'm hoping someone can offer some additional insight.
It's a theme I've built for myself. I've narrowed it down to being an issue with the background. Mobile devices seem to want to scroll the background image on the
.home-aboutsection instead of scrolling the actual website.HI Anitac,
Thanks for checking in. I'm using both an iPad and iPhone, and I"ve had reports from others saying that mobile chrome on android isn't scrolling either...
I finally figured it out. In the normalize CSS code I've been using (git.io/normalize), the following portion of the html declaration breaks IE8:
html{font-family:sans-serif;...So I just removed the
font-family:sans-serif;and it's good now.Finally figured it out. In the normalize CSS code I've been using (git.io/normalize), the following portion of the html declaration breaks IE8:
html{font-family:sans-serif;...So I just removed the
font-family:sans-serif;and it's good now.OMG, I finally found the issue after hours of searching... the culprit? An
overflow: hidden;declaration. I will now celebrate by crying tears of joy.Ahoy there. I did post in their forum as well. The thing is, I'm not exactly sure that the issue is caused by their plugin, or rather my own code. I've developed other themes that are not conflicting with the plugin, so I tend to think that it's something on my end (though their code isn't exactly the most error-free either).
When I run diagnostics, I get some script errors being thrown from their plugin.
I figured out what was going on. I had added a function on my home page that was telling it to replace the body styles with ones that I had created. I just kept missing (and had forgotten about) that when I was going over my code. Things are working great now. Thanks for the help.
Thanks for the advice nutsandbolts. I've figured out the cause of the issue, now I'm just not sure how to fix it... It appears that
.header-imageclass is not being added to the body section on the homepage...I would typically just use the following code, but the way I have my homepage set up doesn't allow for their use...
<?php get_header(); ?> <?php genesis_home(); ?>I'm going to mess around with it for a bit and see what I figure out.
Thanks for the suggestion; I failed to mention that I'm using a MultiSite install where some sites will be using an image header and some will not, so I can't do a universal text-indent.
The Quick Answer:
Make sure a Genesis-compatible child-theme is activated (and not broken) on your site(s); for MultiSite, this has to be on all of your sites.The Long Answer:
After doing some more testing after giving it a rest, I discovered this same thing can happen on regular WordPress installs as well. The issue is caused when you don't have a Genesis-compatible child theme activated on your site. This means on MultiSite, if one of your sites is not using a Genesis child theme (even if the framework is installed), it will not let you activate the plugin. You'll have to go through each site 1-by-1 and activate it that way. This isn't very practical for MultiSite installs, and it would be nice to have this changed.
