Sridhar Katakam

Genesis and WordPress Tutorials

Custom Page Template in Altitude Pro for setting up an inner Page similar to the Front page

by 7 Comments

In my Facebook group a member asked if I can write a tutorial on setting up an inside Page in Altitude Pro similar to that of the homepage.

Please watch the screencast below to get an overview of the end result after implementing the steps in this tutorial.

We shall ensure that background images of featured sections 1, 3, 5 and 7 of the inner page can be changed in the Customizer independently from those of the front page.

Step 1

Add the following in Altitude Pro's functions.php:

To view the full content, please sign up for the membership.

Already a member? Log in below or here.

  • Another excellent tutorial thanks

    I really want to use this template more than once in Altitude Pro but ran into a few issues when trying this – the customizer functions don’t seem to work to call the images – widgets appear and layout is fine just the default bgd images are blurry spaces…

    It may be due to already using the Front Page as static?? – please see below

    Also – if I want to use this more template more than once – what do you suggest as the cleanest approach – e.g. clone template and CSS?

    Thanks

    I am already using the Front Page template as a static Home Page with active widgets – using this code in front-page.php

    add_action( ‘genesis_meta’, ‘altitude_front_page_front_page_meta’ );
    function altitude_front_page_front_page_meta() {
    function altitude_front_page_genesis_meta() {

    if ( is_active_sidebar( ‘front-page-1’ ) || is_active_sidebar( ‘front-page-2’ ) || is_active_sidebar( ‘front-page-3’ ) || is_active_sidebar( ‘front-page-4’ ) || is_active_sidebar( ‘front-page-5’ ) || is_active_sidebar( ‘front-page-6’ ) || is_active_sidebar( ‘front-page-7’ ) ) {
    if ( is_singular() ) { // check if the home page is a static page
    remove_action( ‘genesis_entry_header’, ‘genesis_do_post_title’ ); // if it is, remove the page title.
    }
    else {
    remove_action( ‘genesis_loop’, ‘genesis_do_loop’ ); // if it’s not a static page and widget areas are active, remove the loop (latest posts)
    }
    add_action( ‘genesis_loop’, ‘altitude_front_page_widgets’ ); // regardless, show the widgets.
    }
    }

    Reply

    • Hi – please scrap my last comment – it works perfectly!! Must have been my code editing!!

      Just one question – if I wanted to create more than one inner page using this template – I can see that changing the widget names and css classes is not difficult – but not sure about the lib output and customize.php

      Does the lib support multiple entries

      e.g. Inner Page 2, Inner Page 3

      Thanks

      Reply

  • Thank you so much for your great tutorials, Sridhar! If I wanted to apply the inner page template to multiple inner pages, but with different background images for each page, what would be the best approach? In this case, I’m building the site for myself, so I’m fine adding the background images via CSS, but if it were for a client it would be nice for them to be able to easily switch up the photos on their own. Also, I’m not sure the CSS route would be best practice? What are your thoughts on this?

    Thanks again – your tutorials are the best!
    Lisa

    Reply

  • Sridhar,
    Do you have tutorials that describe how to add custom content on the background images of the Front Pages in Altitude Pro without the use of widgets? The widgets appear to restrict the positioning of content boxes.
    I am trying to add custom content boxes specifically placed on each background image.
    I also am having trouble getting my revolution slider to appear on Front Page 1. Any thoughts?
    Thanks.
    David

    Reply

  • I am getting an error with helper-functions.php regarding getting default link colour already being called. I can get by this by deleting that code from your customise.php code but the end result is not displaying full width. I am assuming that there has been updates to the core theme that is conflicting with your code which is a few years old now. Any chance you might update this?

    Reply
    • >