Forum Replies Created
-
Posts
-
Hi,
You want to reduce the height of that black bar on top? There’s tons of padding on the header nav. Appearance… Edit, and look for the code like this. I changed the padding setting. This looks pretty good to me..header-image .site-header .widget-area { padding: 1.9rem 0; }Dave
Wes,
I converted my own homepage to Epik 1.3 with Genesis 2.0 yesterday. It was the easiest time I’ve ever had changing the theme there. My own homepage is largely a landing page now, not too complex. But with so many fancy widgets available, I was expecting to do some careful organizing/thinking. Instead, things just fell into place. I did a few moves of items to different widgets. My responsive Portfolio Slider looked good right away. I added 2, count ’em 2 lines of CSS, and I was good to go! I played with all the color options, and I liked several, but went back to the default for now, which I think really looks great.I’m extremely pleased!! I look forward to using this theme elsewhere too, on more complex sites. davidchu.net
Thanks!! Dave
Hi Eric and Wes,
Just FYI, not urgent – I converted to official 1.3, and it’s looking great! Re: the PrettyPhoto slider, 1.3 created a new issue, and I tracked it down (apart from my fix for the thumbnails above)…3.1 has CSS that gives a blanket treatment to images, for responsiveness, no doubt:
img { height: auto; width: auto; /* IE8 */ }This made PrettyPhoto mini-thumbs look awful and work funny, so I added this CSS which fixed it:
.pp_gallery ul a img { width: 50px; }Then again, I may end up abandoning PrettyPhoto anyway, as it’s not responsive. I added some CSS hacks to force it to be a bit responsive, but it just isn’t quite right anyway. Maybe this will help someone. Plenty of nice responsive sliders out there now. 🙂
PS: I noticed 1.3 got rid of the admin bar error – nice job!!!! Wish I could be a fly on the wall and see what changes Gary J made. 😉
Dave
Hi,
I agree that Eric’s code should work, as long as it’s in the Epik style.css.I see interference from a bunch of inline styles, I don’t know if that’s coming from Jetpack or something else, you’ll have to hunt that down. This code is in there, and the 2nd line is adding an extra dollop of background color. If that can be deleted or at least set to “background-color: inherit;”, then the bar revealed by Eric’s code will look nice, with the background color and the image.
.site-header .wrap { background-color: #293F5E !important; padding: 1rem 0; }Dave
Hi,
These super-tricked out homepages that every theme has nowadays can be somewhat confusing, even to a theme hacker like me. The most common problem I see on the Studiopress forum is that people are used to having a static page as “Home”, so they wonder why no home widgets work (95% of modern tricked-out theme home pages require that you choose “Latest Posts” for what’s on home, even if their home page layout contains no Blog posts at all! Otherwise, no Home widgets work).But I think there’s an easy answer to your question. You can just make a new page, call it Blog, and here’s the key difference: before saving the page, go down to the right, and find “Template”. In the dropdown, choose “Blog”. Save. (no content needed on the page). Then put the page into one of your menus, and you’re all set. This will work great unless you want some kind of custom changes to the blog display.
Dave
I had some downtime today, so just for giggles and practice, I did a quickie Genesis 2.0 conversion of the Epik theme. It came out very well! The Portfolio section was borked, as expected, but I just made a couple of hook changes as per my own article, and they worked. The appearance was a little funky, but I got it looking decent with a few CSS tweaks, and with a few more minutes of CSS polishing, it would look just lovely.
So I’m looking forward to seeing what the official 2.0 version will be like!
Dave
I see. And I did notice after the fact that there are separate instructions about the PrettyPhoto setup. I wouldn’t have needed to explore if the default in the template had been to use PrettyPhoto, like the demo. Maybe most people don’t want PrettyPhoto. In any case, it’s good to know that it works, and to familiarize myself with the template code.
Anyway, having a conditional for the mini-thumbnails is good if you don’t want to force the user to have a Featured Image on every item in the Portfolio. It’s very normal code for this type of context:
if ( has_post_thumbnail() ) { ... other code here .... }Dave
Hi Again!
One more thing… in the above code for displaying the PrettyPhotos, I found and fixed one more issue.As I’d mentioned, I noticed that the lightbox was working. Then I looked at its own little navigation thumbnails at the bottom. There were tiny thumbnails for the Posts with Featured Images, and also “blank” thumbnails for the “other images”. When I clicked the “other images”, a lightbox error came up saying “image not found”.
I realized what was going on, and then made the lightbox code conditional – I just used an IF statement to make sure there was an existing featured image before adding a mini-thumbnail. This way, I only got mini-thumbnails on the lightbox for “real images”. 🙂
Cheers, Dave
Hi Wes,
Yup, I’ve been following these changes closely, and the README has been pulled out for 2.0. More on that stuff here.Why this would happen is beyond me. I answer questions on the SP forum, and some questions would have been avoided altogether if people would have read that. Now that’s out. Gary’s not even a Studiopress employee, but thanks to him, some details emerge. The SP team are pretty silent about release details, changelogs, prices, etc. I don’t know if they’re understaffed or what. So I’m left to do my own code compares, or catch something on Twitter.
On a happier note, when I get some time between tasks, I will be sporting Epik on my own homepage, so I’m looking forward to that!
Dave
