Your cart is currently empty!
And where have all those helpful Epik tutorials you wrote gone to?
I found what I wanted here in the end ~ http://wpsites.net/web-design/how-to-create-a-custom-landing-page-template-for-genesis/
Well, I waited for version 2.0, no change, then for version 2.01 to come out, but it doesn’t make any difference.
If I have “epik-darkblue” set up as my default color scheme, for example, and then I select for a specific page a custom body class of “epik-black”, in the raw page HTML I can see the line ~
<body class="page page-id-1172 page-template-default logged-in mp6 custom-header header-image full-width-content epik-darkblue epik-black" itemscope="itemscope" itemtype="http://schema.org/WebPage">
Both are color schemes are called but only the “epik-darkblue” shows.
However, if I leave the default set at “epik-darkblue” and then change the same page’s custom body class to “epik-pink”, the page then becomes pink.
So the custom body class “epik-black” doesn’t work in combination with “epik-darkblue” in the standard CSS setup, but the combination with the custom body class “epik-pink” works, for some reason.
This is with the standard CSS supplied as the HTML5 version of Epik.
Any ideas? I have been trying for ages to get my terms and conditions pages to be in black.
Thanks Scooby but I know how to use Google. What I don’t know is how to make a landing page which is full width.
Removing left alignment from featured images in Genesis.
And then I found this post by one of the contributing developers of Genesis [http://www.billerickson.net/genesis-featured-image-alignment/] so I thought I’d (he’d) cracked it.
But apparently not. The body copy still keeps creeping up the side of the image.
https://appfinite.com/topic/blog-content-in-the-image-area/#post-6951
The clue is in the title… 8^)
@GDU ~ got the same issue here, and then I discovered that, as of bbPress 2.2, bbPress will auto-detect the CSS file if it exists in the right location.
Directions to use custom CSS file without a plugin
Copy:
wp-content/plugins/bbpress/templates/default/css/bbpress.css
to:
wp-content/themes/[YOUR-THEME]/css/bbpress.css
That’s all it takes.
Oh, and maybe a little editing of the bbpress.css file, of course.
Hope that helps.
Terence.
@BossLady ~ I just looked at the website with my iPhone and I think I now see what you mean. Almost half the slider image, in fact half of the screen was obscured by the header.
But try as I may, I am still not understanding how to correct this.
Damn, you’re good!
[clear]
by itself wouldn’t do it. I scratched my head for days.
@BossLady ~ with nothing more clever than rearranging the menu items a little the header should now appear to you to be no more than 60px high? Yes?
You don’t use the standard WordPress menu locations in this design you use a menu widget.
Once you have created your menu you access it via a custom menu widget in the “header right” sidebar under Appearance > Widgets.
Hope that helps.
Terence.
@BossLady ~ thank you so much for trying to help me with this.
I tried what you suggested but I couldn’t see that it made any obvious difference.
I don’t doubt what you are saying is correct, but I am wondering if the problem you are seeing is not the one I am trying to fix.
You see the header 100px deep because you are not logged in and this changes “Log In” to “Log Out” and adds “Register” to the menu, which cause it to wrap inside the header. I think that’s why for you it the menu covers the slider. Also the logo has slipped out of position since adding this sticky header and is no longer on top of the home anchor.
Either way, first I have to fix that problem then I can come back to the media queries.
Any ideas on fixing the logo position?
Yes, that would do it if the #wrap ID was high enough on the home page.
At the moment I have an ID in the Genesis header script meta box, and its still not high enough.
Hmm, very strange. Are you sure its my site doing it Eric? I just looked at it ~ not logged in, with cache and cookies cleared ~ with Firefox’s code inspector, and I had no problem at all.
I have no idea what might be preventing you from seeing the underlying CSS. As far as I am aware, there isn’t anything running with anything remotely like that capability. The only thing I can think it could be is CloudFlare have maybe updated their firewall capability and, whether I like it or not, there’s some code obfuscation going on?
I think your guess is a good one but I have to admit I am struggling with how to maintain the header at 100% AND define a width. Could you give me an example of how that is done?
Yes, I think it was something like return_to_top, but that sounds like a possibility. At the moment I have it returning to an ID which is a div in the Genesis header meta box, but it doesn’t return high enough. I’ll take a look at the wrap and see if that does it better.
Thanks Eric.
@touchofsummer ~ you were absolutely right and its fixed now.
All it required was to change two fixed dimension “header-width: ###px” statements to “header-width: 100%” in the media query section, and the job’s done.
Awesome! Thank you so much.
I always wanted to be an expurd, and now I are one… 8^)
@atouchofsummer ~ I play everywhere. When you get to my age, you start to realize just how much of a game life is and how much of life is just a game.
Thanks for the guidance. I am looking at Media Queries section in the Genesis 2.0.1 sample child theme right now and I do see some differences. Surely it can’t be that simple?
I’ll go and see if I can make it work.
Taa muchly!
@Jason ~ no, but close. Actually its from Brad Dalton. I saw it here [ http://wpsites.net/web-design/how-to-make-your-nav-menu-sticky/ ] and thought it looked like a really simple solution. Which it was, since he left out the whole media queries bit, which is unusual for Brad as his stuff is usually pretty spot-on.
Fortunately, he’s take pity on me and he’s taking a look, so I should have an answer pretty soon now.
Thanks for trying Eric.
The author simply says its a “media query issue” and if I would like to pay him to do some custom coding he’ll think about it, or failing that I should “take a course”.
So I guess that’s me on my own again, looking for the paddle… 8^)
Apparently Wes has gone awol, so I asked Brad Dalton, the guy who coded the original version of this method of creating a sticky menu, and what he told me was this…
It needs responsive design.
You will need to customize the responsive design using the CSS media queries as an guide in your child themes style.css file.
Hope you understand that responsive design varies depending on the individuals preferences and the design of the theme you’re using.
It’s not the same for every theme.
So now, arguably, I am wiser, but I still don’t know what to do to resolve this issue.
With this additional input, can someone (Eric?) steer me in the right direction?
Why thanks Eric. Thanks for thinking it and thanks for taking the time to say so.
It’s still at a very early stage, as you can see, and there’s more ideas I have but most of those are for behind the scenes.
I really like how the sticky menu and the single-page/homepage feature work together, but at the moment I only have two menu items working in single-page mode “Plans” and “Features”. In the end they will drive the whole homepage up and down, as needed, while the “blog” ~ or “latest news” link {haven’t decided yet} ~ will take visitors off the homepage and deeper inside the site.
When that happens, the menu’s “Home” link and a completely new set of links appears in the menu, which keep people on the inner pages until they click the “Home” link again.
Now if I could only figure what’s happening to the header in view-ports 768 and 1024 I would be a happy man.
I did add !important to the margin code in line 722 and it did fix it for my content.
Perfect… thanks Eric.
@onlinesimple ~ hi, you’re right, now I come to check it on that link it doesn’t have the spots, but when I look at it in page preview it does.
Don’t know whether that’s a an Epik, a Genesis 2.01 or WP 3.6 issue, but the’re not the same.
OK, thanks, that’s problem solved for me. Somebody else’s problem now.
Maybe Wes will take a moment and have a look.. do you think?
No need to explain at all ~ but what do you mean I am not the center of your Universe?
Now I am heart-broken as well as a non-comic.
My missus always says most people don’t get my sense of humor. {That’s because she doesn’t have one ~ but don’t tell here I said that}
For instance, I asked her the other day, “…what’s the difference between man’s best friend, and his wife?”
Answer ~ if you locked your dog in the trunk of the car, he would still love you when you let him out! 8^)
Anyway, no, I didn’t fix it, its still the same. I guess you didn’t get time to check it as I suggested, but as you can see here ~ http://www.studiopress.com/responsive/?http://qloudpress.com ~ even when you use 100%, it doesn’t work that way for all viewports, 768 and 1024 for example.
Keep up the great work. And remember, I have ADS and a weird sense of humor… 8^)
@scooby @onlinesimple ~ thanks for coming back to me.
I published the test page I was working on at http://qloudpress.com/test/ so you can see what’s happening.
I’ve added !important as you suggested Allegra, but its not working.
Is my CSS so goddamn awful you don’t want to talk to me any more?
I’m guessing you’re on your holidays, so I won’t take offence.
I’m struggling here guys… throw me a crumb!
@Eric & @David ~ thanks guys. I think you’re right Eric, there might have been a caching problem. I’m sure we’re just a gnat’s away, but what do I know, right… 8^)
This is all I now have in my Site Header section…
/*
Site Header
---------------------------------------------------------------------------------------------------- */
.head-wrap {
background: #303236;
margin: 0 0 40px;
}
.site-header {
margin: 0 auto;
max-width: 100%;
}
.site-header .wrap {
padding: 16px 0;
padding: 1rem 0;
}
/*
My Site Header
---------------------------------------------------------------------------------------------------- */
/* This is where the magic happens. You need
* to assign a fixed position in order for
* everything else to work correctly.
--------------------------------------------- */
.site-header {
position: fixed;
top: 0;
width: 100%;
z-index: 2000;
}
/* This will ensure your site looks correct
* when the admin bar is displaying.
--------------------------------------------- */
body.admin-bar .site-header {
top: 32px /* Make this 32px if MP6 is installed */
}
/*
Body Element
---------------------------------------------------------------------------------------------------- */
/* This Should Be Equal to the Height of your
* fixed header bar.
--------------------------------------------- */
body {
padding-top: 60px;
padding-top: 4.28571429rem; /* Only Add this in Genesis 2.0 */
}
.head-wrap .site-header {
background-color: #293f5e !important;
}
Originally max-width was set to 1140px in this section…
.site-header {
margin: 0 auto;
max-width: 100%;
}
but if I change the max-width back to 1140px instead of 100% the header doesn’t expand right the way across at full size. But as you can see here ~ http://www.studiopress.com/responsive/?http://qloudpress.com ~ even when I use 100%, it doesn’t work that way for all viewports, 768 and 1024 for example.
What am I doing wrong?
Thanks Eric, I tried your suggestion but adding that override makes no difference.
I also moved all the code to the header location around #1872, but nothing changed.
I then tried NickTheGreek’s plugin “Genesis Responsive Header” ~ which I used to have to use with 1.2, but don’t seem to need with 1.3 ~ because it normally allows you to set the header background color. But this time, with HTML5 and Genesis 2.0 it made no difference at all.
I then tried background-color: #293f5e !important;
in various locations but for the moment I seem to be stumped as it remains stubbornly transparent.
This is a real shame because I particularly liked this method since, to my eyes at least, its very elegant and requires only minimal CSS additions.
Something within HTML5 seems to be controlling the header in a way I don’t understand.
Yet.
I simply have this code at the bottom of my style.css file, by the way. I don’t know if it should be more strategically located and if this is part of the problem.
@scooby ~ No, I think he is right. For the first-time user it *IS* confusing, because the answers you need in order to get started are spread all over the place, and its not easy to find them all until you you really dig in. Which is off-putting and not a good way to start the relationship.
And this constant referral I read in this forum, not only by you, about conforming to “generally accepted Genesis theme principles” or similar, while it may be true, is not an answer that satisfies anyone who is not already a CSS/PHP proficient coder, which means its way above the head of many users.
Wes could do all his future customers a big favor, and lighten the burden on the forums too, simply by A) putting all the specific code snippets he has published as examples (of which there are a quite a few), and samples pages and tutorials into the readme.txt (rather than whats in there now which tells you a whole bunch of stuff, but not what you need to know), and/or B) including them in a basic manual, and perhaps the simplest of them all C) exporting his demo site as an XML import file (including the standard Genesis sample content), which is literally the work of a very few moments both to do and to publicize.
This is really basic ‘premium theme publishing 101’ stuff were talking here guys. It ought to be there, but so far its not.
Terence.
I found that…
.site-footer a {
color: #fff;
}
without the !important wouldn’t work for me, but…
.site-footer a {
color: rgb(255, 255, 255) !important;
}
works just fine.
You can’t see epik-darkblue links on a black background. But that’s the standard 1.3 now has.
Yes, thanks, that may fix the footer, but the problem is that this is now the default behavior for all links and its very different from 1.2
I guess I got used to the way it was and feel it worked better. The links in 1.2 were bolder, the correct color (white) when in the footer, and altogether more obvious to the user.
The code above will maybe partially resolve the issue with the footer, but what about all the other links in the body copy and plugins etc?
I guess I was just looking for it to be the same as it was in 1.2. No problem. I can live with that.
Ooops! It was late at night and I meant to ask “will Wes be reversing these fixes back into 1.4…?”
Terence.
Actually, it seems to me that all the link and hover colors are not the same any more and some make no sense at all.
For example, the current Custom Body Class (epik-darkblue) is being used as the link color, with no hover color, on a black background for the creds in the footer.
This makes no sense at all, of course. How do I put the contrasts back in?
Actually, I am not too concerned about this since I can just use <small>...</small>
instead.
I just thought Wes might like to know.
OK, thanks Eric, that defines the problem but not the solution.
So Google is my friend, and I have just learned that REM is the fallback with Sass or LESS, is relative to the font-size of the parent element on which it is defined and that this means, if one of the parents in the DOM-tree changes its font-size, the font-size of the child element changes too. Also that in contrast the REM unit is relative to the root element of the page (this means the html element), and thus it is possible to define a font-size once on the root and make all other sizes depending on this size.
So then I realized, I have to learn how to convert one into the other in order to deal with this situation, so I found the converter here ~ http://foliovision.com/2013/03/responsive-design-calculator ~ and worked out/confirmed that 40px is actually 2.85714286rem, and then I really started to get confused.
But in the end, I went with the following, and it seems to work quite nicely…
.header-image .site-header .widget-area {
padding: 10px 0;
padding: 0.72rem 0;
}
Thanks Eric, my education continues… 8^)
I just posted the first one ~ had to leave you something to get your teeth into… 8^)
I am off to bed now ZZzzzz…. 😉
Hi Eric.
Its 02:45 in the morning here and I am sitting here trying to get the site back to where it was before I updated. I think I’m going to write this and then hit the sack as I have to be up early in the morning.
So much for Brian’s “Don’t be afraid to update to Genesis 2.0”. To be fair though, Genesis may well have been part of the problem but it didn’t become apparent until I updated Epik to 1.3.
Yes I understand that Wes rewrote it although I am not really sure why/if that was entirely necessary. Well, whether it was or it wasn’t, we are where we are. No good crying about it.
I take your point about not mixing the issues together so that others might find the solution to their problems a bit easier. I will put each in a separate thread so that we can tick them off as we go.
I think some/most of my original issues with ‘wonkiness’ were more to do with not being able to clear my cache properly than problems within the original PHP/CSS. Apparently the version of Chrome I was using had a problem, so I have now re-installed it.
Open-Sans is running generally but the way it has been used, and not used, in places, which is the first problem I saw. Being trained as a typographer I am sensitive to type styles, line spacing, font weight and color being changed and there are a number of those that have crept in, either deliberately, or accidentally in the rewrite; so I will start a new series of threads and work my way through the ones I can see already.
Thanks for being there and the offer of your help. I really do appreciate it.
Terence.
D) The link text in the footer is now the default “epik-xxx” color instead of white as it used to be.
E) The font used in the footer, the weight and line spacing, and elsewhere, have all changed very subtly, but not for the better unfortunately.
Download it and open the archive. You will soon know by the dates on the files inside.
And I am going to start a new thread and apologies for hijacking yours.
I added @import url(http://fonts.googleapis.com/css?family=Open+Sans:400italic,400,600,800,700); to my CSS but the old familiar Open Sans face has not returned. I’m looking at it and I can’t put my finger on it but something has changed.
I have it running at http://qloudpress.com in HTML5 mode and I can see a few things I may need some help with. The over-large header has returned, and although this used to work for me, it now doesn’t.`/* header height logo width etc */
.header-image #title,
.header-image #title a,
.header-image #title-area {
min-height: 40px;
width: 278px;`
Also some of the widgets have gone wonky, and Open Sans has disappeared in favour of Helvetica for some reason.
Think I’ll go and make a nice cup of tea. I might be here for a while.
8^)
Wes, how will we know if its the new version loaded in our “My Account” section, since it only shows a link for “Epik”?
I tried Eric’s converter the other day and ran out of time and patience, when it didn’t go right for me. Not his fault ~ mine.
To avoid update problems I use two plugins and totally avoid the hassle no matter how many ‘improvements’ I make ~ Improved Simpler CSS, a custom CSS and LESS editor which provides an easy way to modify the css globally on your site, and you are able to edit the css from the front end, plus Code Snippets which is a very easy, clean and simple way to add code snippets to your site. No need to edit to your theme’s functions.php file ever again!
That’s it Eric! Perfect. Thanks.
I got the website restarted but not the footer creds to center.