Matthias Baier

Ok, I reread the document and I probably need to clarify, what my problem was.
Twentyfifteen’s custom-header.php uses functions without declaring them in an if-statement. So my child-themes functions get overwriten.
If I follow the guide I end up with a redeclaration error:
Cannot redeclare twentyfifteen_custom_header_setup() (previously declared in…
Even, if I can’t find a problem in the custom-header.php of twentyfifteen. If just gets loaded first and I’m out.
I could pass on the parameters via the functions.php, but actually, I’d like my own template-file to be used.

But I solved my problem by using IDs to style my child-theme and displayed the wrong stuff to “none”.
I was just wondering if there was a best way to do something like this.

Well,
[your-name],< [email]> worked for my client for many years. Otherwise CF 7 would send Mails containing “WordPress” as the sender. Don’t ask me why. The default “correct” [your-name] < [email]> would not work. I did some testing that time and found that formating as a working configuration for my client.

That’s why I came up with the question if this would be a host-related issue or client based.
I have installed Postman now and was not experiencing any more issues – I assume it was a Problem with the WP Mail SMTP. What was driving me crazy, that it all worked well here for me on any device, but not at my clients computer and phones. I could have done some Testing with WP Mail SMTP – but I’m already way over my budget.

Thanks for your help! WP Postman did the trick.

I also would like to see that coming. ??
I get error messages from time to time, because I have an IPv6-Adress…

Hello Jason,
Our posts overlaped…
Well the same host is relevant, as CF 7 behaves different.
For example, the client I mentioned changed its hosting company. Before he had no problem sending sucessfull forms.
The From-Field was looing like that at the old host:
[your-name],< [email]>

The new host doesn’t work with this code.
It has to be formed like this:
[your-name] <[email]>

I did a lot of testing, and none failed for me, but for my client.

I don’t want to change the From-Field to a static email-adress right now, as I want to give my client the oportunity to hit the reply-button in his email-client. Only as a last oportunity.

I will install Postman today and do some testing.

Well some of the problems I encountered before were due to a missformed From-Field.
Try the helpfiles of CF7.
The question is: Is the from field the same everywhere? And are all your sites on the same host?
For me this is the case: Same host. I never encountered such a problem with CF 7.
My from field looks like this:
[your-name] <[your-email]>

Try to create a new blank form and see if that works. From that you can go on.

Your error message looks like mine. However I will really need to check the postman log, to see what is really going on. WP-Mail-SMTP is not really helpfull with my problem, as I can send test-E-Mails and also the forms are working. Only my client gets the error popping up. He even receives my successfully filled forms, as it is his site and he is the receiver.

Try this code instead:

<?php

function my_child_theme_setup() {
	load_child_theme_textdomain( 'twentyfourteen', get_stylesheet_directory() . '/languages' );
}

add_action( 'after_setup_theme', 'my_child_theme_setup' );

?>

Note, that the only difference is twentyfourteen instead of twentyfourteen-child. the get_stylesheet_directory() function calls the childthemes folder, where get_template_diretory_uri() calls the parenttheme folder.

I can’t tell, if this is a bug or it is supposed to work like this. According to documentation it is supposed to work like the code you already tried.

Never mind. Problem was in my header-file. A missing ”

I had them both installed.
From my perspective, you can’t really use qtranslate and yoast at the same time and hope you get a good SEO result in all languages.
What you try to do here is a contradiction in terms, as both plugins want to write the meta-tags. Who wins? I actually didn’t try to answer this. Yoast an qtranslate is just something that doesn’t work.
The Yoast developer doesn’t want to support qtranslate and advises to use WPML instead. (Completely different approach to mulitlanguage)

Thank you! Helped me. And it also brought to my attention, I have an autoupdate feature in WordPress now. Hm… Definately will check this out further today.

Try this formating in the “From:”-Field instead:
[your-name],< [email]>

For me it did the trick – even the colon seemed to be of some importance.