Daniel

Hey Javier! Thank you for your help!

I tried again today and ended up with the same results.

Will send you an email with admin access along with my import file — maybe you’ll see something I’m missing!

Thanks again! ??

Hey Mike!

Though the original poster didn’t care to respond, the points listed in your post are certainly helpful.

I’m experiencing a similar problem and I can’t figure it out.

Let me answer your questions…

On the Settings page (Dashboard > Settings > Email Users) there is a Test Notification message. Does that work?

Unfortunately not.

Also on the Dashboard are a couple of notification boxes on the upper right hand side which tell you if any of the filters which affect WordPress email are active – what do they report?

wp_mail_content_type: No
wp_mail_charset: No
wp_mail_from: No
wp_mail_from_name: Yes

The “Yes” comes from the following code in my functions.php, but when removed and “wp_mail_from_name” changes to “No” — It still doesn’t work.

function change_wp_mail_from_name($from_name){
return "CHOSEN_NAME_HERE";
}
add_filter("wp_mail_from_name", "change_wp_mail_from_name");

Email Users utilizes wp_mail(), the same mechanism WordPress itself uses to send email. Do you receive email from your WordPress site (user registration, comment notification, etc.)?

Yes. WordPress, BuddyPress and Contact Form 7 all send emails. Furthermore, I deactivated all plugins to see if they might be causing conflict. Still no dice.

How many users are you trying to run your test with? I recommend starting with one and once that works, try two or three.

I tried with 1 user and the Test Notification Message, neither worked.

Also, expected and actual do match.

Hopefully you can help me figure this one out! ??

Thanks in advance!
Dan

Sweet!! That did it! Thanks for the speedy fix!!! ??

Yes, this last update made a mess is some places adding blank <p> tags.

Does anyone know a quick fix until this is corrected?

Thanks!

Brilliant!!! You ROCK Siobhan! ??

I especially love how you explained each step in detail — have you considered teaching?

I can’t tell you how much I fought with this — Thank you so much for bringing your experience to the table.

I just had to make a few styling fixes to tackle those inconsistencies you foresaw.

First, I had to add the padding globally:

.page .site-content {
	padding: 3em 4.661%;
}

Then I included your snippet here along with 2 of my own to address the entry content and the pages without featured images:

@media screen and (min-width: 1180px) {
.page .site-content {
	padding: 3em 55px;
}
.page .entry-content {
	padding: 0 0 0 146px;
}
.page .without-featured-image > .entry-header {
	margin-left: 146px;
}
}

…and we’re as good as gold — at least from what I can see! ??

Thanks again for your kind support, it’s VERY appreciated!!! ??

Hello and thank you for your reply!

I recognize the similarities between the single post and the single page, but there is also a significant difference as you can see here…

Though the default “single page” layout can be nice in some cases (especially when you have good imagery to work with), the featured image is very dominant and occupies more real-estate above the fold line, including the widget area.

The layout of the “single post” displays the featured image at nearly half the size and adds some nice white-space above it — this makes for a “lighter” look while bringing the sidebar back into view.

I certainly agree with you in regards to the child theme — definitely good practice! ??

Such a beautiful theme here. Very happy with it!! ??

Hey John! Thanks for the invite — I would certainly need to create a test site in order to take advantage of this.

I actually knew you could manually install a “zipped” file through the “add plugin” feature within WordPress — What I didn’t know is that there are “stable versions” of the plugin out there that aren’t recognized from within the WordPress platform.

Just curious as to why (if they’re marked as stable) they are not released through the WordPress platform?

I know we’re off topic here, but I appreciate the insight.

Cheers! ??

This happened to me too, but I believe it fixed itself as the error is no longer there. ??

Thanks for the helpful feedback John! ??

I didn’t realize newer versions of the plugin was available for download and use outside the wordpress platform.

Just curious as to why this is? I’m so used to updating via the plug-ins section of my websites.

Is there an approval process (like what apple does with their apps) before stable versions of plug-ins are available within WordPress?

Cheers!

Hahah! I did some digging on your forum and found the solution!

I just had to change:
<?php echo $cat_menu->description;?>

to:
<?php echo __($cat_menu->description);?>

Sweet!! ??

I’m not sure if it makes a difference, but this code is used inside a custom widget. It’s meant to display the “category descriptions” from a “custom post”.

Same problem here — Only with Custom Post Types!

i have the following plugins installed….
qTranslate-X
qTranslate slug
Integration: Yoast SEO & qTranslate-X

Any word on this yet?

Thanks so much!!

This made me realize I had some old fixes in my functions.php which were likely addressed by you guys a loooong time ago! LOL! Removing the code below fixed the problem and everything still works — though I have not yet tried the WC3 validation thing! ??

Thanks again! ??

/*
=========================================================
Enables qTranslate to work with Custom Posts
=========================================================
*/
function qtranslate_edit_taxonomies(){
$args=array(
‘public’ => true ,
‘_builtin’ => false
);
$output = ‘object’; // or objects
$operator = ‘and’; // ‘and’ or ‘or’

$taxonomies = get_taxonomies($args,$output,$operator);

if ($taxonomies) {
foreach ($taxonomies as $taxonomy ) {
add_action( $taxonomy->name.’_add_form’, ‘qtrans_modifyTermFormFor’);
add_action( $taxonomy->name.’_edit_form’, ‘qtrans_modifyTermFormFor’);
}
}
}
add_action(‘admin_init’, ‘qtranslate_edit_taxonomies’);

/*
==========================================================
Removes output to <head> created by qTranslate causing WC3 validation error
==========================================================
*/
add_action(‘init’, ‘remove_header_info’);
function remove_header_info() {
remove_action(‘wp_head’, ‘qtrans_header’);
}

I should probably mention I recently moved the site…. where would it be pulling that path from?

Does anyone know if this is at all possible?