[brock]

Can you link to the site where you're having a problem?

[brock]

My pleasure! Glad you figured it out.

[brock]

You might even like this better:

.before-header .enews-widget input {
    border: 0;
    display: inline;
    float: left;
    margin-right: 10px; <--- this
    width: 20%;
}

If it's helpful to anyone else who might come along and try to solve this, I signed up for the form which fails and redirects me to the link that is in the form's action attribute. Then I try that form and it goes through. So, something is apparently happening with the front-end form processing although I haven't determined what.

[brock]

Oh yeah, I see it now. Sorry I was looking in the sidebar. The value of the margin is set to a 10 with no px anything to say what kind of value it is and the browser is not reading it. I changed it to 5px and that looks pretty good. Like this:

.before-header .enews-widget input {
    border: 0;
    display: inline;
    float: left;
    margin: 5px; <---try this
    width: 20%;
}

As for the form not processing the submission, i'll tinker with the form in my browser and see what happens. Maybe someone else has some thoughts?

[brock]

It looks like you've fixed it.

[brock]

Can you post your code, @adrien?

[brock]

Yes good point Victor. Sorry I forgot about that. What I did was leave it in the functions.php and wrap it in an if condition to show a sidebar only on single posts. Here it is:

add_action( 'get_header', 'bc_single_post_sidebar' );
function bc_single_post_sidebar() {
	if ( !is_single() ) {
		//* Force full-width-content layout setting
		add_filter( 'genesis_site_layout', '__genesis_return_full_width_content' );
	}
}

This way, your archive pages won't have a sidebar - only your posts pages. Of course, if you want archives to have a sidebar as well then do as Victor suggested and move the force full-width code into the front-page.php file.

Note: this only gives you the basic default sidebars that come with genesis (which you will need to style with CSS). It won't have the slide-out or read-next functionality which you may be looking for.

[brock]

Try either deleting or commenting out this line:

//* Force full-width-content layout setting
add_filter( 'genesis_site_layout', '__genesis_return_full_width_content' );

The widgets should then show up at the bottom of your post, so you'll need to add some extra css.

[brock]

Hey dalexisp,

Are you referring the the author profile to the left of the article?

[brock]

Yes, it is.

[brock]

Cool! It's a little tricky because you have to target the last child of the list, which is the li, and only then target the a. It's tempting to try to target the a as a last child when it's actually a first child of the li!

[brock]

This is common when you first install a Genesis theme. I think the default widgets are put in the header right section by WordPress, for some reason. All you have to do is delete or move those widgets from the header right section. If you click on the individual widgets the box expands and you will see an option to remove them toward the bottom.

The Genesis themes don't come setup like the demo but there are setup instructions associated with your theme. Go to your downloads section on the StudioPress site to find them. Setting your site up like the demo falls under official support so if you have any problems along the way you can submit a ticket.

[brock]

Is this what you're going for?

.site-header .genesis-nav-menu li:last-child a {
	border-right: none;
}

[brock]

The text is wrapped in an s tag. It is a strange s tag because it looks like it is supposed to be a strong tag. It appears like this <s trong>whatever</s>. See w3schools for information about the s tag.

[brock]

Hey Renee,

You can add it just above the the .enews p, at the very top. It's just a matter of organization and, in this case, not going to change how the code behaves.

[brock]

Look for the add the subfooter section around line 86 in your functions.php file and change the 5 to a 1.

[brock]

Open your theme files and look inside of the js folder. Open the file effects.js and remove these lines from it.

$(".nav-primary .genesis-nav-menu").addClass("responsive-menu").before('<div id="responsive-menu-icon"></div>');

	$("#responsive-menu-icon").click(function(){
		$(".nav-primary .genesis-nav-menu").fadeToggle();
	});

[brock]

The Genesis theme that appears in the video isn't Daily Dish Pro and that explains the discrepancy. There is a section in the style.css file that styles the enews plugin in accordance with the look and feel of that particular theme. The code below adds a black background-color to the section element with classes of .widget and .enews-widget. This section element is the container that holds the widget. So, we can target its classes and add a background - in this case I added a black background. But before that, I have also targeted the text color and changed it to white so it will contrast with the black.

.enews-widget,
.enews-widget .widget-title {
	color: #fff;
}

.sidebar .widget.enews-widget {
	background-color: #111;
	padding: 20px;
}

I recommend to add these changes in the plugin>enews commented section of your stylesheet to keep it organized. I hope this suggestion gets you started.

You also said

Plus, when I edit
my copy, it’s not updating.

I didn't understand what you meant so I didn't address that part of your question. Good luck.

[brock]

The question is how slightly bigger are we talking about?

They are div elements with a class of home-featured-1 2,3, and 4. These divs have a width property set at 25%. That allows each div element to fit within the containing div, adding up to 100% of the space of the container. If you increase the width of the div elements to 50% then it will knock two of the elements down to a new row. It will make the images larger and you might like how this looks or you may not.

Since the widgets inside of the above mentioned divs have their own padding on the right and left sides (20 pixels of it) the images become smaller still to respect that. So if you only want to make the images slightly, slightly bigger I would recommend playing with those right and left side padding pixels. The less padding they have, the more space the images can take up in the div.

To do this you will use the .home-featured .widget class selectors and adjust the second value (which is currently set at 20px) of the padding property. Like this:

.home-featured .widget {
          padding: 0 20px;
}

Instead of 20px maybe 5px or 10px would give you the slightly larger sizes you want. Otherwise, you might want to have a look at increasing the width of the home-featured-1 divs to 50% as I mentioned at the beginning.

Good luck.

[brock]

I'm scandalized.

[Author]

Posts