[Bill MurrayParticipant Post count: 463]

So…

1) I’m guessing you switched to the Generate theme after uploading some of your images? That would explain why the first image on your first post is the wrong size. WP generates image sizes based on the settings in effect when you upload the images. If those settings change, you need to regenerate the images. Visit the WP plugin repo and grab the Ajax Thumbnail Rebuild and run it. That should solve the image sizing problem.

2) Looking at the source of the first image, it appears you put the 2nd image inside H2 tags, followed by a 2nd H2. That might be more obvious in the HTML editor as opposed to the visual editor. I recommend you delete the H2 tags surrounding the image, and delete the image from the post content. That will solve the duplicate image problem on that post.

A bit of unsolicited advice: shorten those permalinks. It’s fine to have catchy titles, but the permalink should be short and keyword rich and without stop words.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

Are you sure you’re loading those fonts correctly? (Nudge, nudge )

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

@MacWebgrrl – I can only assume you are using the Generate theme, since you don’t say and your link doesn’t work.

If you are using Generate, as I said in my previous post, the home page is controlled by home.php. By default, Generate displays 2 featured posts followed by some posts in a grid loop. Generate will grab the image that is attached to the post and display that first, then it will display post content up to a more tag. One way to get rid of the 2nd image is to make sure you only include an image in the post content that is after the more tag. If you want to change the way the grid loop operates, you’ll need to edit home.php.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

Yes, you can style them there. There are classes ( .someclass ) and IDs ( #someID ). If you look at Firebug, you’ll see your form has an ID of #af-form-574040688. An ID is unique to a page.

That already has some styling from your from provider. In your child theme’s style sheet, you’d just restyle only what you want to change. If you want to change the background of the entire form and make it a little wider, you’d do this:

#af-form-574040688 { background: #ccc; width: 60%; } /* you put your color there */

Sometimes, because of the order of loading style sheets, you have to make sure that your declaration is the one that’s followed, so you put !important on a declaration you want to override:

#af-form-574040688 { background: #ccc !important; width: 60%; }

You record your CSS for each property that you want to change or add (you don’t need to repeat what’s OK), which you discover in Firebug. Also, in case you’re not aware, you experiment in FIrebug. In other words, you add your new styling in Firebug to test whether that’s what you want. When you’re satisfied with a declaration, you record that in your stylesheet.

As for an example of a styled form, I do have one. It’s your own website. Don’t get hung up on Aweber class names or ID’s. The names are irrelevant. It’s just CSS and you are no more or less restricted because it is an Aweber form. The only subtle exception to that (and you won’t know about this until you dive in) is whether Aweber has provided an ID or class name for every place you want to style uniquely. They probably have, but that may not be true of every situation where you try to style output from a third party.

Good luck.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

Want the easy way or the harder but more versatile way?

Easy: Just style what you have with CSS. It has classes and ID’s to make that possible. Firebug is your friend. Give him a hug.

Harder but more versatile: 1) Add a new widget area and 2) change your landing page template to put this widget area somewhere. Putting it at the start or end of content is easier; putting it in the middle is much harder. You can fake putting it in the middle by creating multiple widget areas, putting your signup form in the 1st, and putting a widget that would display additional content (like a text widget) in the second. That makes it look like your form is in the middle of content, when it is really at the end of what WP considers post/page content.

The second method requires you to master a few skills involving PHP, and you run the risk of breaking your site with even a minor typo.

You’ll have to choose the method best suited to the time/effort you want to devote to sorting it out.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

On screen options you should see Slug and Excerpt, which are core WP checkboxes. So if you’re not seeing those, something is odd. A standard debugging step is to deactivate all plugins to see if it’s a plugin conflict. There are various approaches to this (such as picking 1/2 of them and starting there). After each deactivation, you’ll need to check a post edit screen to see if your screen options are back to normal.

And just to clarify, I assume you are checking screen options on the post edit screen and you’re running the latest version of WP, which is 3.5.1?

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

@CynthiaC – I think you understand you can’t do this with media queries/responsive design.

If you want to redirect mobile users to 1 page, the fastest way to do it would be via UA detection or MIME-type support (such as a check for WML) followed by redirection in your htaccess file (assuming your site is on an Apache server). These methods aren’t 100% foolproof, but they are pretty reliable. Your script solution would be another route (you could use Genesis settings to get that into the head of your document). There are also open source PHP libraries, like php-mobile-detect. I think the htaccess route would be the fastest.

While you can do what you want, you might want to pause and ask yourself whether you should do what you want. From an SEO perspective, what you want to do isn’t a great SEO strategy. More info here.

Hope that helps.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

The concepts won’t become obsolete. The names might change, and you might get some extra hook names to learn.

If you learn the concept of hooking in 1.9.2, that knowledge won’t be wasted when it comes to thinking about 2.0. If you wait until 2.0 to start learning, you’ll just be further behind when you do start compared to the alternate you who started earlier.

If you create templates using the old hooks, you will have to make changes, but if you understand the concepts, you’ll have the knowledge to make them.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

1) On image sizes: Using the WP media manager, images are sized when uploaded based on the settings in effect at that time. WP stores a copy of each size of each image. When you change themes or plugins, WP doesn’t automatically generate the new sizes unless you tell it to. You can use the Ajax Thumbnail Rebuild plugin in the WP plugin repo to solve this problem.

2) On double images: Generate uses a home.php template that makes use of Grid loop. If you have an image in your post and images are hard-coded into the home.php template, you’ll could see double images.

Hope that helps.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

On a post where you can’t enter comments, try clicking Screen Options in the upper right, make sure the Discussion option is checked, then scroll down to the Discussion metabox and make sure comments are allowed.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

Here you go:

add_theme_support( ‘genesis-html5′ );

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

1. Give the CSS or CSS3 link in the left sidebar a spin, http://www.w3schools.com/. You can also try Google with whatever words come to your mind. If you read and learn, over time your word guesses will get better.

2. This is a little more complicated. It’s one of those things that one might try, get wrong, and have to repeat. It’s hard to give you many specifics without an image on your site, so you should upload one and include it as a background on a nearby ID. It should be a good guess as to size, but the image can be a black box. At this stage, you’re just trying to get the size you want and learn how to position it. The background method is easier, but makes it harder to change the image. The other method is more complicated from a CSS perspective, but makes it easier to change the image.

2a. I haven’t tried the method of adding an image to eNews Extended, but conceptually you would do something like this in the text box for content before the form:

Hi there, here is my my signup form! Rain your signups down upon me!

2b. You want mobile responsive too? Can you change the name of your site to Mom Gets Ambitious? Yes, you’ll have to adjust the mobile responsive CSS. My recommendation is to work out the change in your normal site CSS, and then tackle the mobile CSS 1 media query at a time. You may have to come up with images of different sizes for different media queries, so when you name your first image, keep that in mind and make the name indicate which site width it serves.

Yes, your final thought would work, but that is just a simpler variation of changing the image itself in the media query. Note the notion of changing things in the media query would be very difficult unless you stick to putting the image there via a background. If you opt for putting the image in the content directly, you’ll have to choose an image that is small enough for your smallest supported device in your media queries.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

1. Modify your child theme’s stylesheet for .feature-box h4 near line 696 to include width: 65%;

2. Several possible ways. One way is to set a background on the .feature-box that includes the image, and position it where you want it. Second way would be to include the image in your content at the beginning (ie, where you “Here’s how Mom Goes Online …”) and give it a CSS class, such as .myimage; then you’d add styling for .feature-box .enews p and float that left and .feature-box .enews .myimage and float that right;

3. For .feature-box .enews #subbox near line 728 of your child theme’s stylesheet, add a width, similar to width: 300px;

Mom, let me introduce you to Firebug.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

Just grab the current sample child theme and delete the media queries at the end of the stylesheet. Responsiveness will be gone.

---

Twitter: @wpperform

[Bill MurrayParticipant Post count: 463]

Deactivating a plugin does just that – it makes it so it is no longer active. In that state its code is not executing. So deactivation will get you essentially back to the state you were before you activated the plugin – except for the options the plugin wrote to the database.

Some plugins provide an option to delete plugin settings on deactivation, but most don’t. Most users want to keep plugin settings on deactivation because deactivating plugins is a common troubleshooting technique where a plugin is deactivated only for a short period. If you ever want to go back to Better WP Security, you can simply re-activate, and any configuration work you did is still intact because the options are in the DB.

If you don’t want to use Better WP Security, you can look through the database, find the options settings for that plugin, and delete them. However, you have to do that with extreme caution, because some options might not be clearly labeled, and if you’re not familiar with doing this, it’s easy to delete the wrong thing. Having a few unused options is not a big deal, but if you are regularly activating plugins just to test/evaluate them, you shouldn’t be doing that testing on a live site.

---

Twitter: @wpperform

[Author]

Posts