acub

in CSS (panel or style.css of child theme):

@media (max-width: 979px) {
	.navbar .nav > li {display: block !important}
}

or you could wrap the lines from 20 to 52 in your child theme’s style.css in a @media condition:

@media (min-width: 980px) { // line 19

} // line 52

Leap, it’s pretty clear you messed up somewhere. So let’s start fresh.

1. Disable and delete your child theme and activate Customizr (or any other theme). Make sure that Customizr is updated to last version.
2. Create a new folder in your local copy of the site, under wp-content/themes/ and name it inStyle
3. Using a simple editor (notepad) create a new file and put this in it:

/*
 Theme Name:	inStyle Boutique
 Theme URI:	http://www.instyleboutique.com.au
 Description:	Theme for inStyle Boutique
 Author:	Leapmkt
 Author URI:	http://www.instyleboutique.com.au
 Template:	customizr
 Version:	1.0.0
*/

4. Save this file in the inStyle folder as style.css (make sure encoding is set to UTF-8).
5. In the same folder, create another file, also UTF-8 with the name functions.php and put this in it, making sure there’s no empty space or empty line before the first character:

<?php

All the php snippets you’ll use for your website will go in this file, starting from line 2 (or 3). Line 1 needs to remain untouched.
5. Upload all the inStyle folder to your server (same path: wp-content/themes/)
6. Go to Dashboard > Appearance > Themes and activate your inStyle Boutique theme
7. Go to Dashboard > Appearance Menus > Manage Locations tab, select your menu and click “Use new menu”.

You now have a working child theme, properly installed. Any css code you add to style.css will apply to your webpages and any php code you add in functions.php will also work.

Note: Change category-slug above with the actual category slug.

Another note: The first code is supposed to work, too, I don’t know why it didn’t in my tests. It might have to do with a bug on using is_category(tag_ID) on $wp_query, according to comments in this thread.

So basically it needs a check on whether the category with that id actually exists:

function sort_category( $query ) {
	if (	$query->is_main_query()
	&&	term_exists(314,'category')
	&&	$query->is_category(314)
	&& ! 	is_admin() ) {
		$query->set( 'orderby', 'modified' );
    		}
	}
add_action( 'pre_get_posts', 'sort_category' );

where 314 needs to be replaced with the actual category ID.

Yes, it’s possible. There are two requirements:
1. You need a child theme.
2. You need to know your category ID or the category slug. To find out the category ID go to your categories and hover over the edit category link. Watch the href displayed for the value of tag_ID.

Now, add this code in functions.php of your child theme and replace {$cat_ID_or_slug} with either category ID or the category slug:

function sort_category( $query ) {
	if (	$query->is_category('{$cat_ID_or_slug}')
	&&	$query->is_main_query()
	&&	! $query->is_admin() ) {
		$query->set( 'orderby', 'modified' );
    		}
	}

add_action( 'pre_get_posts', 'sort_category' );

I can’t test it right now. Get back to me if it doesn’t work. It should work, afaik is_category() is inside query.php, so it’s usable with pre_get_posts.

You’re right.

Go to Dashboard > Appearance > Menus > Manage Locations Tab, select the menu you want from the list and click Use new menu.

I see you solved your problem. However, I noticed another error you might want to get fixed: the nggimagerotation plugin has a jQuery script error and I’m pretty sure things are not working right with your current rotation.
You need to replace line 19 of wp-content/plugins/nggimagerotation/view.js from:

});

to:

})(jQuery);

If it’s a plugin you got from WP repository, you should let authors know about this. If you made it, well, just update your view.js and it will work.

Cheers.

From WP’s point of view, the header, sidebars and footer of this template all know they’re on a page. The page you set the template for. If you want it to know you’re on a blog page, you have to extend the query accordingly, to include whatever you want it in (header, sidebars, footer, etc…). (In the case any of them displays different content on pots lists). To do that, move the lines 1 and 2 in the template, to include the parts you need.

query_posts is discouraged because it creates another instance of the main query. But in our case it is what we need.

Besides, it’s not efficient (does both the initial page query and, when it gets to the content it does a new one and replaces the first). And you also need to be pass the pagination from the list to the page.