acub

In Dashboard > Appearance > Customize > Pages and Posts Layout you may select excerpts or full content for post lists. If you want full content, select it. If you want to have more control over what’s displayed in the lists, select excerpts and manually set excerpt for each of the posts (in each post’s edit screen).

Notice that if your excerpt is set manually it will ignore the character limit (that only applies for auto generated excerpts).

gm_dwivedi, the proper way to overwrite parent theme files is to copy them into your child theme, keeping folder structure (i.e.: if it’s inside /parts in Customizr you need to create a /parts folder in your child theme). Now hack and slash away the copy from the child theme and upload it. WP will only read files from the parent if they don’t exist in the child theme.

There are only two exceptions from this rule: functions.php and style.css. This is why neither of those files in child theme should contain anything from the parent theme counterpart contents, as it will result in duplicate code.

If you want your child theme translated in multiple languages, here’s how to do it: add this to your functions.php:

add_action( 'after_setup_theme', 'customizr_child_theme_setup');
function customizr_child_theme_setup() {
    load_child_theme_textdomain( 'customizr-child', get_stylesheet_directory() . '/lang' );
}

Now, install Poedit, create a lang folder inside your child theme, set it’s base path to ../ (dot-dot-slash) and add a . (dot) path and click update. poedit will search all your child theme directory for any localization texts in the form of

__('Text in default language', 'customizr-child');

and will put them all in your .pot or .po file. There are more localization functions, __() is just one of them. More here. After that, you may add translations for as many languages you want. When the user will have ?lang=xx in their browser they will see the translation from the corresponding .mo file, in your lang folder.

If you don’t want to internationalize your child theme and all you need is a translation of Customizr that hasn’t been done already, you should write to nikeo and maybe contribute with the translation yourself. He’ll tell you how it’s done.

You’re using version 3.0.6. And I have no clue why this setting doesn’t work in your installation.

I’ll give you the steps you need to do, assuming your child theme is Customizr Child:
1. Create a child theme with the name of Customizr Child.(if you haven’t already).
2. Create a lang folder inside it.
3. Add this php code to your child theme’s functions.php:

add_action( 'after_setup_theme', 'customizr_child_theme_setup');
function customizr_child_theme_setup() {
    load_child_theme_textdomain( 'customizr-child', get_stylesheet_directory() . '/lang' );
}

add_action ('__header', 'display_homepage_slogan', 100);
function display_homepage_slogan() {
	ob_start();
	if(is_home() && !is_paged()):
		echo '<div align="center">
		<span style="font-size: large;">';
		$line_break = "<br />";
		printf( __('Yellow Bridge is an international knowledge center that inspires %s and supports small and medium organizations
to improve their performance through sustainability.', 'customizr-child' ), $line_break );
		echo '</span></div>';
	endif;
	echo ob_get_clean();
	}

4. Download, install and open Poedit.
5. File > New. Instert your language code in there (let’s assume it’s french: you need to type fr_FR in the input that shows up).
6. Go to Catalog > Properties and put there:

Project name and version: Customizr Child
Team: put your name there
Team’s email address: put your email there (it’s safe)
Charset: UTF-8 (recommended)
Source code charset: UTF-8 (recommended)

7. Save the catalog inside the lang folder as fr_FR.po (use your own language locale, of course – ro_RO.po for romanian, etc…)
8. Go to Catalog > Properties and open the second tab. Put ../ (dot-dot-slash) as base path and add a . (dot) path (2nd icon). Click save.
9. Click Update. Your Yellow Bridge… text should now show up in the translations.
10. Select it and input your translation in the Tranlation field. Watch for the position of %s (that will be your line break).
11. Save again.
12. Now upload all your lang folder and functions.php of your child theme to your server.

Your text should correctly display in the selected language now.

Yes, you need to put it in between single or double quotes. It’s php. On the other hand, I don’t think the above function will work, though. When you put “customizr” in textdomain, it searches the xx_XX.mo file from Customizr folder for the translation of

Yellow Bridge is an international knowledge center that inspires %s and supports small and medium organizations
to improve their performance through sustainability.

But that text is not part of the language files of Customizr, so it will never get translated (it will be displayed untranslated). In order to get it translated you have to declare a textdomain for you child theme, create a pot file for it, set the child theme folder as source path in the file’s settings and hit “Update from sources” in poedit. At that point your child theme’s pot file will be updated with your string and you may create a xx_XX.po (and a xx_XX.mo subsequently) for your language, in your child theme’s declared textdomain folder and provide a translation for your text. You could do all the above in Customizr, but you’ll lose it upon update, that’s why I suggested you do it in child theme folder. It’s complicated, and it’s something only theme and plugin developers should be doing, not the end user, in order to internationalize their code.

Are you sure you got the solution right from WPML? Because, if you did, they forgot to tell you how to implement it. 🙂

Dashboard > Appearance > Customize > First Page options > Slider options:
Select “no slider” from the list.

For the search results part, the only way to achieve this in the current version is to create a /parts folder in your child theme, copy class-content-slider.php from Customizr/parts in this newly created folder and replace all 5 occurrences of

tc__f('__is_home')

with

(tc__f('__is_home') || is_search())

However, there is a chance that this solution will stop working on future updates of the theme. At that point you’ll have to do the same replacement again, but on the updated version of class-content-slider.php.

I’m not sure I understand the “and the tag-cloud” part. If it means you want the slider on tag archives too, you’ll need to add || is_tag() to your replacement, like this:

(tc__f('__is_home') || is_search() || is_tag())

If not, please be more specific.