Fred17

I’ve installed the dev version and no error so far. Thank you very much for your quick response.

Hi

Message to the developer to reproduce this notice. You need to be in debug mode and set the site to a foreign language.

Thanks a lot for the quick fix

The theme is Twenty Twenty-ThreeVersion: 1.6.

I used other plugins but as I said when I desactive Simple History, no error logged. When I reactive, there are these errors.

when I desactive Simple History, no error logged. When I reactive, there are these errors.

The last entries:

[15-Nov-2024 10:12:01 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>simple-history</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114 [15-Nov-2024 10:12:04 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>simple-history</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114 [15-Nov-2024 10:12:06 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>simple-history</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114 [15-Nov-2024 10:12:06 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>simple-history</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114

Hi,

I use the 5.1.0. The message is since WP 6.7 update

Same question

Hi @wardee, the new release resolve my issue. All is fine now. Thanks for your work.

I tested the Plugin Organizer plugin on my Local installation. I swapped the loading order of WP Mail Catcher (now loaded first) and WP HTML Mail (now loaded after).
But this doesn’t change the problem of the template not being used when the mails are not stored.

Yes, I’ll look into it. But it’s strange that for stored emails there’s also the template, whereas for those that aren’t stored the template is forgotten?

Hi, I have an undesirable side effect.

I have several plugins that work on the emails sent by my site.
Easy WP SMTP, which makes sure that emails are sent by my host’s SMTP server.
WP HTML Mail – Email Template Designer which gives a unique template to all outgoing emails.
Mail logging – WP Mail Catcher, which keeps a record of all e-mails sent.
I added my code to the wp_mail_catcher_before_success_log_save hook.
Since then, emails that are filtered according to a specific subject are not stored in the database and are sent to the recipients, but the unique template is not applied to them.
In other words, the WP HTML Mail plugin fulfils its role for emails that are stored but not for others.
Do you have any idea what causes this difference?

Thanks for your quick answer. There is a .htaccess which deny all. The file is 660. But maybe WP doesn’t see that. I’m reluctant to place the file above the root because I’m not sure my host allows it

Here is an example. Maybe there is better. This will not save the mail with subject XXXX or YYYY

<?php
/**************
* desactivate log mail by mailcatcher
* ************ */
add_filter('wp_mail_catcher_before_success_log_save','my_mail_catch_filter');
function my_mail_catch_filter($transformedArgs){
    if ($transformedArgs['subject']=='XXXXX' || $transformedArgs['subject']=='YYYYY'){
        return false;  
    }
    return $transformedArgs;
}

Hi,
Some pb:

I don’t find the filter hook wp_mail_catcher_before_success_log_save in the WPMC code.

Have you a short example with this hook please ?