[Erik D. Slater]

Or should I perhaps enter a new ticket?

Yessy ... since this will allow others to contribute to the discussion 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

ellafitz: By "WPML", are you referring to the https://wpml.org/ plugin?

Also, this may help: https://wpml.org/forums/topic/using-the-studiopress-genesis-altitude-pro-child-theme/.

Generally speaking, there shouldn't be an issue with multilingual support for the Genesis child themes.

Was there something specific that you were looking at or found, and which you think might be an issue?

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

TheresaSh: You've got the following line in your footer:
<p style="text-align: center;">___________________________________________________________</p>

This is causing issues with responsive behaviours for widths of 523px and lower.

As a replacement, you could do something like:
<p style="border-top:1px solid #000;margin:15px auto 10px;"></p>

For best practices, you should replace the "style" part with a "class" ... then move it from your HTML to your style.css file.

For now though, give this a go and see if this helps 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Nice one 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Ah-haaa. I see now what you're asking for 🙂

Take a look at this: http://codepen.io/cbracco/pen/zekgx (not mine, but I think it's what you're looking for).

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

paaljoachim was on the right lines, and was almost there with just the very last bit (the rest of what he provided is not necessary).

Replace all of that with the following:

.site-footer {
	bottom: 0;
	height: 100px;
	position: fixed;
	width: 100%;
}

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Ah-haaaa ... yes ... that makes sense ... especially since you had "migrated over to the Pro version — that’s when everything went wonky" 🙂

thanks so much for hanging in there with me. I didn’t even realized that had worked, until your comment!

I think your coffee deserves all the praise here 😉

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Hmmm ... they all look OK now. Did you update something?

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

The reason I ask is because all of the images - with the exception of the first two on the first row - are originally 280x200.

The original dimensions of the first two - on that first row - are (respectively):
- 740x411
- 740x555

I'm just wondering if you need to upload those two images with the right version and dimensions for the home page ...

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Thanks for the link 🙂

Who is uploading these images to the site?

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

cccmedia: Would be really helpful if you could post a URL which highlights your problem 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

/themes/altitude-pro/lib/customize.php, line 74:

$images = apply_filters( 'altitude_images', array( '1', '3', '5', '7' ) );

/themes/altitude-pro/lib/output.php, line 19:

$opts = apply_filters( 'altitude_images', array( '1', '3', '5', '7' ) );

'1', '3', '5', '7' relates directly to the front page/featured image sections. You probably want to change them to '1', '3', '6', '8' ... but you should probably remove the images first ... so you don't get confused at a later date if you decide to switch these values back 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

This is defined by WordPress I think…and it didn’t change although I edited all the necessary CSS fields…

(1) It's defined by the theme, which has added these options to the WordPress Customizer.

(2) You missed the very first point I mentioned, i.e.
"For the background images, you need to go into Appearance -> Customize and reassign them. The image that is currently assigned to Front Page 5 needs to be removed … and then assign it to Front Page 6, etc."

In other words ... remove the images from Feature Section 5 Image and Feature Section 7 Image ... and then add images to Feature Section 6 Image and Feature Section 8 Image accordingly.

You haven't done this part yet ... as confirmed by the image you just uploaded 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

For the background images, you need to go into Appearance -> Customize and reassign them. The image that is currently assigned to Front Page 5 needs to be removed ... and then assign it to Front Page 6, etc.

For the background colour for front-page-5, look in your CSS for:
.front-page-4 .solid-section
then change it to:
.front-page-4 .solid-section,.front-page-5 .solid-section

For the margins, look for the .flexible-widgets definition in your CSS. It will look something like:
padding-bottom: 60px;
padding-top: 100px;
Don't touch those ... but define a new definition immediately below it that looks something like:

.front-page-4 .flexible-widgets {
	padding-bottom: 0;
}
.front-page-5 .flexible-widgets {
	padding-bottom: 0;
	padding-top: 0;
}

Lastly - for completeness - in your CSS, you should add .front-page-8 to where you see something that looks like:
.front-page-2, .front-page-3, .front-page-4, .front-page-5, .front-page-6, .front-page-7

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

The proposal from Brad - which, as he pointed out is also "the easiest way to do this" ... by far - along with the supporting point from Victor (to ensure a seamless transition between the two widget areas) would be the way I would typically handle this sort of thing myself.

The reason why this is the easiest approach is because the theme deliberately determines which CSS selector to use based on the number of widgets found inside a widget area ... and it won't display more than 4 widgets in one so-to-speak "row".

So ... it's not that the design itself is breaking. It is behaving as per theme design 🙂 And it's not the only Genesis child theme to do this, e.g. Author Pro does something similar.

If you would prefer not to do this yourself then I can certainly sort this one out for you ... but I will charge for the time. But since Brad was here first, I think he should be given first opportunity for a paid engagement. If that doesn't work out - and Victor can't or doesn't want to do it - then I'll be happy to pick this one up 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Hi Vasilis,

Adding the extra widget area to your theme would be the more robust approach 🙂

Given the image to which you linked - and the spirit in which Altitude Pro approaches CSS - one way to achieve what you would like to have would be to do the following:

(1) Add the extra widget as you normally would, e.g. add a text widget to the end of the fourth widget area.

(2) Add the following CSS:

.front-page-4 .flexible-widgets section:last-child {
	margin: 0 auto;
	width: 100%;
}

Since you are using Jetpack to minify your CSS file, I can't tell you exactly where this CSS should go. But, make sure it appears after any other definitions for .front-page-4 and .flexible-widgets (in case certain specificity rules take priority) ... but before the media queries stuff.

Just keep in mind that this CSS will always target the last widget that appears in the Front Page 4 widget area.

I have assumed that the yellow background and red text in your example image were for illustration purposes.

This should at least get you moving along 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

You could have left me with my delusions of grandeur and now your Genesis rep in tatters 😉

Hahahaha ... we'll just keep that one between us ... our little secret ... nobody ever needs to know 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Glad someone isn’t a lazy bum (like me) and read through the new version documents.

I'd love to seem that conscientious 🙂

But actually, I have my own archive title ... and when I checked it earlier, I noticed I had two of them on those pages. I'm using the following:

// Add intro text for date archives
remove_action('genesis_before_loop', 'genesis_do_date_archive_title');
add_action('genesis_before_loop', 'eds_genesis_before_loop_date_archives', 10, 0);

so you can see the similarity 🙂

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

Try the following:

remove_action('genesis_before_loop', 'genesis_do_date_archive_title');
add_action('genesis_before_content', 'genesis_do_date_archive_title');

Function genesis_do_date_archive_title() is new with version 2.2.0 ...

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Erik D. Slater]

If you use Print Friendly, use the https version for sites/pages that are served over https ... otherwise your pages will break ... and that violates PCI DSS compliance.

---

Erik D. Slater: Digital Platform Consultant • LinkedIn

[Author]

Posts