[rfmeier]

Hello,

You have a border-top within your style.css on the title that is causing a huge margin.

/* style.css line 775 */
.featured-content .entry-title,
.featuredpost h2 {
	border-top: 34px solid #fff; 
	font-size: 14px;
	font-size: 1.4rem;
	line-height: 1.2;
	margin: 0;
        font-weight: bold;
	text-align: center;
}

Remove the border-top: 34px solid #fff; line and that should solve your issue.

---

Ryan Meier – Twitter

[rfmeier]

SB,

In short; Display a custom post excerpt depending it's category? Is the excerpt set per post? Per category?

I would recommend doing this in a plugin. If you change themes, it won't be disrupted.

---

Ryan Meier – Twitter

[rfmeier]

babress,

This was changed in a WordPress update. Genesis has no control over this.

---

Ryan Meier – Twitter

[rfmeier]

Sam,

At line 1677 within you style.css file, change width: 650px; to width: 100%;, then add the code I pasted below that css block.

.genesis-nav-menu,
.site-header .widget-area,
.site-title {
	text-align: center;
}

---

Ryan Meier – Twitter

[rfmeier]

Also, if you just want it at the very top, you can edit you style.css file as follows;

https://gist.github.com/rfmeier/0e586532461e1ca35242

---

Ryan Meier – Twitter

[rfmeier]

Adam,

To make the navigation bar stick on mobile as it does desktop, you will need to edit your style.css file;

or, if you want it at the very top, change you style.css like below;

https://gist.github.com/rfmeier/0e586532461e1ca35242

---

Ryan Meier – Twitter

[rfmeier]

Jess,

This is due to displaying your posts through a widget on a page. If you look at the code, it will only display the comment bubbles if you are not on a page. I updated to script to remove the clause and always display the comment bubbles.

https://gist.github.com/rfmeier/aeb327a23dc22d3f4aad

---

Ryan Meier – Twitter

[rfmeier]

Great! Glad I could help.

---

Ryan Meier – Twitter

[rfmeier]

Man alive. Posting code never works here.

---

Ryan Meier – Twitter

[rfmeier]

Jeff,

You have the same issue with the clickable area;

Around line ~771 within your style.css file change

.home .listing-wrap:hover span,
.home .listing-wrap:hover a.more-link {
	opacity: 0;
}

to

.home .listing-wrap:hover span,
.home .listing-wrap:hover a.more-link {
	display: none;
}

As for the missing bottom margins... it looks like some elements aren't respecting their height. The issue is probably deeper, but I was able a get a fix in as follows;

Around line ~1238 within your style.css file, change the min-height to 200px like so;

.home-featured-1,
.home-featured-2,
.home-featured-3,
.home-listings .featured-listings .entry {
	float: left;
	margin-bottom: 0;
	margin-right: 60px;
	min-height: 200px;
	text-align: center;
	width: 340px;
}

---

Ryan Meier – Twitter

[rfmeier]

Jeff,

Who is your comment targeted at? kduffey or myself?

---

Ryan Meier – Twitter

[rfmeier]

G,

I would also love if you could help me reduce the size of the menu. It is just too broad i would like to reduce it to a better width i.e reduce the size.

To adjust the width of the menu, you can do two things;

1. Adjust the padding on the anchor elements

/* style.css line ~1018 */
.genesis-nav-menu a {
    border: none;
    color: #222;
    display: block;
    padding: 25px 20px; /* adjust the second value for left and right padding */
    position: relative
}

2. Reduce the font size of the anchor elements;

/* style.css line ~1018 */
.genesis-nav-menu a {
    border: none;
    color: #222;
    display: block;
    padding: 25px 20px;
    font-size: 14px; /* adjust the font size */
    position: relative
}

And also when you visit my site you’ll find that the left and the right side are blank can you suggest me any idea to put it into better use? Can i add like a fixed menu bar even in that white space and in the right white space add some social icons with some ads? Any suggestions and how to do it?

I will leave that up to a designer. I am the last person who should be giving out design advice. You may want to make a new thread in the Design Tips section

Good luck.

---

Ryan Meier – Twitter

[rfmeier]

jspada,

The first is still a big one. The shortcode is still not showing its query results on the the search results page. You can see that here, Memoriam test search results, its the first result on the page. This is the major issue. If you click the link and go to the actual page Im using the short code on you can see that it does work there on the individual page.

Shortcodes are only executed on pages where the shortcode exists. A search is not a post or a page, but you can still modify the initial query to affect the search results. The search page can actually take in extra parameters from the query string to alter the results. Adding post_type=memoriam will return a search of only the 'memoriam' posts. Search memoriam post types. There are two ways (probably more) to accomplish this.

1. Create your own search form and add a <input type="hidden" name="post_type" value="memoriam" /> within the search form, so the post type gets passed along with the search.

2. Hook into the pre_get_posts action for a search and append the post_type. This would cause all default searches to search the custom post type. Logic could also be used to allow the default search too.

Second, if you scroll down the search results page a bit you will notice that other results, ones that are not of type memoriam, have the ‘FILED UNDER: CATEGORY’ printed twice. I can fix that by removing ‘genesis_post_meta();’ from the jspt_memoriam_post_meta function. However, in addition to that, the posts of type memoriam, still have ‘FILED UNDER:’ in the footer although just without the actual category. The jspt_memoriam_post_meta function you created just seems to remove the metadata and not the entire entry footer area.

This ended up being a bug in my code. I was assuming get_post_type() was grabbing the current post object, but it wasn't. This was breaking the logic within the actions and filters I added. I fixed this code and updated the gist. I didn't notice this before because I wasn't able to test the code.

I also want to remove the entry content for memoriam post types. So can I rewrite the jspt_memoriam_post_meta function like this?

The action should be added to the functions.php file like the other action and filter I added. I updated the code to include this within the gist.

https://gist.github.com/31897a3519df07c75829.git

---

Ryan Meier – Twitter

[rfmeier]

jspada,

The first is still a big one. The shortcode is still not showing its query results on the the search results page. You can see that here, Memoriam test search results, its the first result on the page. This is the major issue. If you click the link and go to the actual page Im using the short code on you can see that it does work there on the individual page.

Shortcodes are only executed on pages where the shortcode exists. A search is not a post or a page, but you can still modify the initial query to affect the search results. The search page can actually take in extra parameters from the query string to alter the results. Adding post_type=memoriam will return a search of only the 'memoriam' posts. Search memoriam post types. There are two ways (probably more) to accomplish this logic.

1. Create your own search form and add a <input type="hidden" name="post_type" value="memoriam" /> within the search form, so the post type gets passed along with the search.

2. Hook into the pre_get_posts action for a search and append the post_type. This would cause all default searches to search the custom post type. Logic could also be used to allow the default search too.

Second, if you scroll down the search results page a bit you will notice that other results, ones that are not of type memoriam, have the ‘FILED UNDER: CATEGORY’ printed twice. I can fix that by removing ‘genesis_post_meta();’ from the jspt_memoriam_post_meta function. However, in addition to that, the posts of type memoriam, still have ‘FILED UNDER:’ in the footer although just without the actual category. The jspt_memoriam_post_meta function you created just seems to remove the metadata and not the entire entry footer area.

This ended up being a bug in my code. I was assuming get_post_type() was grabbing the current post object, but it wasn't. This was breaking the logic within the actions and filters I added. I fixed this code and updated the gist. I didn't notice this before because I wasn't able to test the code.

I also want to remove the entry content for memoriam post types. So can I rewrite the jspt_memoriam_post_meta function like this?

The action should be added to the functions.php file like the other action and filter I added. I updated the code to include this within the gist.

https://gist.github.com/31897a3519df07c75829.git

---

Ryan Meier – Twitter

[rfmeier]

jspada,

Send me an email at [email protected]

The forum will not display my response.

---

Ryan Meier – Twitter

[rfmeier]

Hello,

I have done this once in the past for a custom post type by adding some logic to the functions.php file to trick WordPress into thinking the home page is an archive page. Since I have never used to Minimum Pro theme, I am not 100% sure on the files included, but I am sure we will be able to get this to work.

1. Within the Minimum Pro theme folder, create an archive.php file if one does not exist already.

2. Copy the code from the Archive Portfolio template into the archive.php file. (I am not 100% sure the code will work as I don't have this theme. If I saw the code, I would have a better understanding)

3. Add the following code to your functions.php file. This will trick WordPress into thinking the home should use the archive.php file.

4. See what results you get. The css may be a little off due to some body classes that may or may not change.

Let me know how this turns out. I am pretty sure we can get this to work.

---

Ryan Meier – Twitter

[rfmeier]

Glad I could help. Good luck.

---

Ryan Meier – Twitter

[rfmeier]

Are you able to edit the css within the browser? Kinda hard to diagnose from a far.

---

Ryan Meier – Twitter

[rfmeier]

I finally had a change to sit down and look at the code. I broke it into three parts, but you can paste them all in the same functions.php file. I made an explanation for each part.

You will only need to create a 'genesis_post_info' filter once and let the logic do the work. When the entry header goes to display the entry meta, if the post type is 'memoriam', it will display the custom content. If not, it will display the default content. This allows you to insert your custom output and leave the default functionality in place.

Similar logic is used to not display the entry footer content for the 'memoriam' post type. When the current post object is not 'memoriam', the default post content will be displayed.

For the short code, you were correct the first time in using the genesis_custom_loop(). The filter and action delegation is no longer needed within the shortcode callback.

I hope this works helps you out.

Edit: I had to put all code in one gist as the forum was removing all posts.

Edit #2: This is obnoxious. Links will not display. You can contact me through my contact form and I can send you the code. http://www.rfmeier.net/contact/

---

Ryan Meier – Twitter

[rfmeier]

It should be within the <head> element. Outside of head would definitely be ignored and probably cause even more rendering issues in IE.

Here is code to inject the meta element early.

You could probably use Genesis Simple Hooks instead of adding code. I am not sure if it will let you adjust action priority.

---

Ryan Meier – Twitter

[Author]

Posts