[Derek]

You can do it via CSS.

If you view the source code for the page, you'll see that each slide excerpt has a unique ID. For example, if we use the Studiopress "Agency" theme demo as an example, the excerpt for the third image has the following class: slide-excerpt slide-825

<li style="width: 950px; float: left; display: block;">
<div class="slide-excerpt slide-825">
<div class="slide-image">

So we can use a little CSS to simply and quick "hide" that excerpt:

.slide-excerpt.slide-825 {
    display: none;
}

You'll just have to figure out what the unique ID is for the excerpt you wish to remove.

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

I actually could have written that a little better. Rather than closing and opening PHP, it's probably better to use the "echo" command:

add_action( 'genesis_before_loop', 'extra_content_div_open');
function extra_content_div_open() {
echo '<div class="post-wrapper">';
}

add_action( 'genesis_after_loop', 'extra_content_div_close');
function extra_content_div_close() {
echo '</div> <!-- end .post-wrapper -->';
}

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Try this in your functions.php file:

add_action( 'genesis_before_loop', 'extra_content_div_open');
function extra_content_div_open() {
?>
<div class="post-wrapper">
<?php
}

add_action( 'genesis_after_loop', 'extra_content_div_close');
function extra_content_div_close() {
?>
</div> <!-- end .post-wrapper -->
<?php
}

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Either you've fixed it, or it is a caching issue. I also checked it in IE7, IE8 and IE9 and could not replicate the issue.

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

You've got the code right, but you need to use it in your functions.php file.

If you want to only move the titles below the images on the front page, you could use a conditional statement in your functions.php file:

/** Move image above post title on Front Page */
add_action( 'genesis_before_loop', 'move_image_front_page' );
function move_image_front_page() {
if( is_front_page()  ) :
remove_action( 'genesis_post_content', 'genesis_do_post_image' );
add_action( 'genesis_before_post_title', 'genesis_do_post_image' );
endif;
}

The only thing I'm not 100% sure on with that code is using the "genesis_before_loop" hook. It worked when I tested it, but I'm not sure it's the best hook to use in this scenario.

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Two things come immediately to mind:

1) The ability write custom Title, Description and Keywords for SEO purposes. You can also better tailor the URL (for those who don't want "category" in it)
2) The ability to add additional content before your posts (like an introduction, for example) via this method: http://my.studiopress.com/snippets/blog-page-content/

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

tyelle,

Studiopress has built a relatively simple solution into Genesis for achieving just that: http://my.studiopress.com/tutorials/category-blog-page/

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Indeed. And Yoast isn't the only one pushing for it: https://github.com/zamoose/themehookalliance

It further confirms my suspicion that, at this point, there is no "generic" method for overriding WP hooks that have already been unhooked and/or replaced/modified with a custom function.

Ultimately, I'd love to have this plugin I'm developing be available to everyone via the WordPress Plugin Directory, which is why I'm looking for a simple way to accommodate all themes/frameworks. In the meantime, I may just need to setup an admin page that requires the user to select their Framework and apply the appropriate code accordingly.

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Thanks Brad. I'll see who I can connect with via Twitter.

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Just for a little background: I've been using Studiopress themes since the beginning (even earlier, in fact, when Brian Gardner was creating themes under Revolution Themes), so needless to say I've become very familiar with the Genesis Framework and how child themes work.

About a year and a half ago I signed up for Elegant Themes, because I saw a template that I wanted to start with for my "I'm getting married" website. I'm a tinkerer, and quite honestly, I found it difficult to make changes and achieve the look and feel I was going for. To me, it felt like I had to do a lot of extra work just to make changes (which may be because I'm so used to Genesis). Also, at the time Elegant Themes was not using a framework and child themes, which meant digging through a lot of files when I did want to change something. So for me, I found Genesis (and their child themes) easier to use.

One of the things I LOVE about Genesis is the parent framework itself. Studiopress has built, in my opinion, a solid platform with which to build child themes on. Additionally, they can handle staying on top of security vulnerabilities, latest web standards, etc. by updating Genesis and pushing that update on to the end user who can update seamlessly without losing the customizations they've made to their child theme. Unfortunately, you just can't do that with a standalone theme like those available from Elegant Themes.

That being said, Elegant Themes does have some beautiful themes available. They are better looking than many of the Genesis child themes, and contain some pretty slick functionality (albeit gimmicky at times). They do have that going for them. Of course, most (if not all) of that functionality you can achieve on the Genesis platform, you just have to put in the grunt work, haha.

Ultimately, I love the Genesis framework because these days I pretty much just build themes from scratch, and being able to do that on top of a well-built, secure, powerful framework makes my job and my life easier (my normal workflow: once I get the theme design as a Photoshop file from my co-worker, I have 6 hours to code the theme and get it online, ready for content).

On a side note: I used to scour the web for "hidden gems" - great themes tucked away in some dark corner. I don't do that anymore, after a few horror stories of my own. Came across this interesting article the other day which only further assured me that sticking to trustworthy theme sources is the only way to go: http://wpmu.org/why-you-should-never-search-for-free-wordpress-themes-in-google-or-anywhere-else/

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

Without actually seeing the site, it's tough to give an exact answer, but most likely you need to tweak the CSS for either the #title-area class or the #header .widget-area class. If the width of these two classes equals more than the width of your theme #wrap (which is probably 960px), then the widget-area will kick down below the title.

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Derek]

I would second what Bill Murray has suggested and essentially re-install WordPress. There was a period of time where we were experiencing odd file changes on our server, and I spent months off-and-on trying to figure it out. Turns out there were still some infected files on the server from that timthumb exploit a couple of years back. Those infected files were affecting PHP files across our server (not just in the WP installs).

If you're able to change what directory on your host your domain points to, I would essentially "rebuild" the site in a new directory. Create a new database and import the tables from the current site into it. Setup a clean version of WP and Genesis in the new directory. Add new/clean versions of the plugins you were using into the plugins folder. If you don't have an offline copy of the child theme that you know is clean, you'll probably need to go through (or hire someone to go through) the child theme and ensure it is free of any bad code.

Just my two cents. It's where I would start!

---

Derek Rippe – CSS Artist & Genesis Fanboy @ SynaVista and MediaCairn Design Studio
Figure out your CSS problems with Firebug | Check out my Custom Comment Form Title plugin

[Author]

Posts