[nickthegeek]

correct, if someone is doing something in violation of the forum rules please submit a ticket to us. Thanks.

[nickthegeek]

pst, bbPress, not BuddyPress.

[nickthegeek]

Please do submit a ticket about this. We imported all accounts, but there are some things that resulted in some themes from being active. Short list includes:

• The purchase may have been under a different account
• The purchase may have been prior to the systems that we had records for
• The ProPlus account may have been comped and so was not part of the purchase systems that were imported
• Something just plain may have gone wrong during the import for this specific purchase

Regardless of the reason, if you submit a ticket we can help get it fixed. Unfortunately there isn't much that can be done in the forum about this, just the help desk. Thanks.

[nickthegeek]

Susan,

Just a note, Brad's code is pretty good, but it can be modified to show the link on all posts but only showing the previous/next link for posts in the same category. You can see the arguments in the codex
http://codex.wordpress.org/Function_Reference/previous_post_link

So you would end up with something like this

add_action( 'genesis_after_post_content', 'my_post_nav', 5 );
function my_post_nav() {
    if( ! is_single() )
        return;

    previous_post_link('<span class="single-post-nav previous-post-link">%link</span>', 'Previous in category', TRUE);
    next_post_link('<span class="single-post-nav next-post-link">%link</span>', 'Next in category', TRUE);
}

You can do a lot more with it than just that too. You can also do some cool stuff with images and add the post title and other HTML markup so that your links can have all kinds of cool styling.

I've even done something custom with it on my blog to pull in a custom image size and use tags instead of categories. This took some pretty hackish custom code and it doesn't play nice if you aren't using categories the way I do to create series, but it works really well for my site.

[nickthegeek]

These are only available to ProPlus members or if the retired theme is an ancestor of the child theme you purchased. If you only purchased Genesis then there will be no retired themes. If you purchased Minimum (for example) you would have access to Minimum 1.0.

The retired themes may not be kept indefinitely, this is just how it works right now.

[nickthegeek]

The difficulty is there is currently no official breadcrumb schema.
http://schema.org/docs/search_results.html#q=breadcrumb

There has been a good bit of discussion and feedback from developers on this issue. It will be done in the way which is ultimately best for moving forward instead of slapping on something just to get it out the door then having to fix it later.

I know it would be nice if I could give a hard answer, but that is the answer as it stands.

[nickthegeek]

"Modern News" is a WordPress.com theme. News 2.1 is the equivalent for WordPress.org.

You can see some examples of what folks have done with it in the showcase
http://www.studiopress.com/theme/news-2

[nickthegeek]

Thank you for your feedback. We always are willing to listen to our customers as we are continually working to improve overall customer experience. If you would like to provide feedback please log into your account here http://my.studiopress.com/ and fill out the Get Help form.

The Community forum is a place for community members to share ideas and solutions. It is also a place for users to request help with customization of StudioPress themes. This is made possible because of the generosity of our many volunteer developers and moderators.

Per our Forum Guidelines here: http://www.studiopress.community/policies-and-guidelines/ this thread will be closed to further comment. Thank you!

[nickthegeek]

Yep, as I explained in the link you found, typically it is best to edit the child themes directly with the exception of true core functionality, things which should exist regardless of the theme being used. That really should be put into a plugin. CSS especially should be done in the child theme directly because it really only applies to a given child theme. Well, it would require some modifications to use in other themes at least.

I do often put my CSS into groups that allow me to find code I will be adapting to new themes I add to my site.

[nickthegeek]

child themes aren't really intended to be updated. For example, lets say you made a custom Minimum 1.0 theme and saw Minimum 2.0 then wanted to update. If you do this your customizations will be lost. Even if you use a core functionality plugin the CSS and some of the functions won't be relevant. This is because the home page markup is pretty dramatically different and the way the CSS works in Minimum 1.0 is dramatically different from 2.0.

It is best to think of them as two different child themes. You can apply your customizations manually but not automatically.

That said, a core functions plugin is a great idea. I like to ask myself which code should be available in all themes then put that into a plugin. Code for custom fields, posts types, and stuff like that belongs in a core functions plugin. Template files, widget areas, and things like that are usually theme specific. There are times when there are templates and widget areas associated with those that will apply to any Genesis child theme, I pull those into a second plugin that loads on a genesis_init hook so if the client switches to a non Genesis theme the site doesn't break.

[nickthegeek]

You can enable that functionality with custom code in the child theme, but it isn't done on purpose because updates are intended to come through Genesis. Child themes should be edited directly and making for an auto update would break the child theme customizations of many users. While some developers may wish to tie into an update script is isn't something that will be adopted by default for all child themes. You can see how the update scripts look in Prose 1.5+

[nickthegeek]

oh, and bumping your post is actually a good way to make sure it isn't seen by the folks helping out.

[nickthegeek]

Please don't paste your entire CSS file. That makes for REALLY long posts with a ton of code that just isn't needed. That makes most volunteers walk away because it really creates a bit of an unmanageable thing. A much better solution is to fill in the URL field with the URL of your site. This creates a link automatically that opens in a new tab and is set to nofollow which is ideal for sharing your site for support. Seeing the site makes it possible to see the HTML markup and also the CSS if needed.

As for your issue, the HTML5 output for the genesis_widget_area() function requires that you declare the "after" argument because "before" may not be a

genesis_widget_area( 'home-top', array(
            'before' => '<div class="home-top widget-area">',
            'after' => '</div>',
        ) );

You need to do that for any genesis_widget_area() function.

[nickthegeek]

Static front pages will not paginate. You need to use the latest posts on the front page and edit the code that forced the layout of the home page in the home.php file if you want pagination on the front page.

[nickthegeek]

Anthony,

sorry for the trouble you are having. This is a bug in the theme and we are fixing it for the download. On issues like this feel free to contact support via my.studiopress.com. We work very hard to have a quick turn around on support issues. Right now our average first response is about 5 hours.

I see that you have it working correctly on the site you linked to. For anyone else having this issue, please add this code to the style.css file. Exact placement isn't important, just make sure it is not inside the responsive section or inside another CSS rule set.

.header-image #title a {
	background: none !important;
	padding: 0;
}

Again, very sorry for the frustration this has caused. If you need anything else remember you can drop us a note in help desk. The theme price includes the theme, support, and this amazing forum we maintain.

[nickthegeek]

Here are a couple of screen shots showing how to get to that setting in Safari
https://dl.dropboxusercontent.com/u/3496010/Screen%20Shot%202013-05-22%20at%202.05.39%20PM.png
https://dl.dropboxusercontent.com/u/3496010/Screen%20Shot%202013-05-22%20at%202.05.53%20PM.png

[nickthegeek]

Unfortunately there isn't anything we can do to force something like that to be taken down. The only way to do that is through legal channels.

[nickthegeek]

In chrome please make sure you have the developer tools active when you load the widgets page and check the console tab to see if there are any script conflicts.

[nickthegeek]

which browser are you using?

[nickthegeek]

Could you try enabling Genesis as the active theme and only GFWA active and see if it works. What version of WordPress are you using?

[Author]

Posts