acub

http://wp.tutsplus.com/tutorials/creative-coding/understanding-the-walker-class/

The Tweeter Bootstrap jquery script that toggles the “open” class to your parent containing li doesn’t seem to be working. Reinstalling Customizr might fix this.
Another cause might be a plugin that uses a newer bootstrap library than 2.3.2. Try disabling plugins one by one to see if your submenus start opening again.

My advice is to remove the snippet until you find the source of the problem and only apply the snippet after your submenus open on click.

1. Create (or find) bigger flags than the ones used by qtranslate for each of the languages you’re going to use. Mine are 32px x 32px centered both vertically and horizontally. Note that if you use a different size you will need to change the CSS accordingly, so they fit nicely in your box. Save the flags in your child theme folder, as {language_code}.png (example: en.png, it.png, etc…) in a folder named flags.
2. Add this code in your child theme’s functions.php (just above the ending ?> (if that’s how your functions.php ends – if not, just below the last function)

add_action ('__before_header', 'qtrans_lang_chooser');
function qtrans_lang_chooser() {
	ob_start();
	echo qtrans_generateLanguageSelectCode('image');
	$output = ob_get_contents();
	ob_end_clean();
	echo $output;
	}

3. Place this code in your style.css of your child theme:

ul.qtrans_language_chooser {
	background-color: rgba(51, 102, 153,.45);
	box-shadow: 2px 5px 7px rgba(0,0,0,.21);
	border-radius: 10px;
	border: 1px rgba(255,255,255,.5) solid;
	left: -17px;
	list-style-type:none;
	margin: 200px 0 0 3px;
	padding: 7px 10px 7px 22px;
	position: fixed;
	-webkit-transition: background-color linear 200ms;
    transition: background-color linear 200ms;
	z-index: 201;
	}
ul.qtrans_language_chooser:hover {
	background-color: rgba(153,204,255,.65);
	box-shadow: 3px 8px 10px rgba(0,0,0,.15);
	}
ul.qtrans_language_chooser li.active {
	display: none;
	}
ul.qtrans_language_chooser li a {
	height: 32px;
	width: 32px;
	}

Feel free to play with position and/or colors and/or shadows of normal and :hover states of ul.qtrans_language_chooser.
Finally, add this to the CSS above, for each of your languages, replacing {language_code} with each language’s code:

a.qtrans_flag.qtrans_flag_{language_code} {
	background: url(flags/{language_code}.png) no-repeat;
	}

Example, for english:

a.qtrans_flag.qtrans_flag_en {
	background: url(flags/en.png) no-repeat;
	}

Upload style.css, functions.php and the flags folder to your child theme and you’re done.

1. Rename your customizr folder through ftp. That will disable the theme and you’ll be able to log into WordPress.
2. Go to themes and activate any other theme.
3. Rename your Customizr folder back.
4. Download the version of Customizr you have initially installed on your website (you can see the version in your themes page) from here. Upload the broken file.
5. Reactivate Customizr.

If that doesn’t work, I suggest upgrading Customizr to the latest version or clean re-installing if you already had latest version installed.

I wouldn’t advise on that. Not until we hear what @nikeo has to say on this matter.

Here’s what I think: providing a responsiveness switch is generally viewed as a good design decision and it’s where we’re heading. Probably in a less than a year’s time, it will be a standard feature on all responsive layouts.

Therefore, there’s a good chance that Customizr will implement it soonish, as it’s the most popular responsive free WP theme out there. If my presumptions are right, when this happens, CSS will need to be adapted for it and your quite consistent effort will be rendered useless. So, before you set out for this big task, wait for nikeo’s answer on this. (I just marked the subject for his reading).

If he says this is not going to happen soon, I’ll assist you with guidelines and code overview to make this switch, but I’d more happily do it for theme implementation in a future release so all theme users benefit from it, rather than as a mod for a single user, that’s prone to breaking on future updates of theme’s CSS.

The code to remove the icons is good, but it removes all icons on website, not just on pages. This removes it only on pages:

.page #main-wrapper h1.format-icon:before {content: none;}

But the centering… is actually indenting in that code, and it scales erratically with page width. Besides, there’s a big risk that it will affect lists of posts (or other content) displayed on pages (by plugins or custom templates). Here’s how to responsively center the page title and only the page title (with icon or not):

.page h1.entry-title {
text-align: center;
}