JWardee

Hey @tezalsec, can you open a ticket on our GitHub tracker here and add in the link to that email templates plugin you are using. I can’t promise that it’ll be fixed as it’ll depend on how the email template plugin functions but I’m happy to take a look – although I have no idea when that’ll be timewise!

I like your idea of adding the resend button into the modal! I’ve added your feature request to the GitHub tracker here.

I’m going to close the issue here as I handle support requests on the GitHub tracker.

Going to close this due to inactivity. If you believe this is an issue with WP Mail Catcher, please open a bug ticket in our bug tracker ??

Hi @tobilotta, it’s going to be very hard to find out what’s going on without exact steps to replicate the issue.

* Are there any errors in your logs from the date and time your customer placed the order?
* Are you using any plugins that interfere with or alter the way emails are sent from WordPress? There’s a list of plugins that are known to cause issues here

If you can reproduce the issue on a fresh WordPress install with WP Mail Catcher installed, let me know how to trigger the issue, then I can look into it.

WP Mail Catcher will just capture what is sent out by your wp_mail function. Its priority is set to 999999 so it could be possible that a translation plugin that you’re using, that is also hooking into the wp_mail function with a higher priority could cause WP Mail Catcher to save the untranslated message.

But that doesn’t explain why it’s working on some of your sites and not others. If you manage to replicate this issue on a plain install of WordPress, then let me know the exact steps and I can take a look.

Hi @f14m07,

No problem, I’ll mark it as resolved.

Cheers,
James

Hey @tpaksu, I’m going to close this here and we can continue chatting on the open GitHub issue.

Cheers!

Hi @naresh11381, glad you like the plugin!

You can actually add these with the cron_schedules filter and WP Mail Catcher will automatically pick them up. As per the docs linked above you could do something like:

function my_add_intervals($schedules) {
    // add a 'weekly' interval
    $schedules['weekly'] = array(
        'interval' => 604800,
        'display' => __('Once Weekly')
    );
    $schedules['monthly'] = array(
        'interval' => 2635200,
        'display' => __('Once a month')
    );
    return $schedules;
}
add_filter( 'cron_schedules', 'my_add_intervals');

Making the jump to 2.0.0 required a change to the database table schema that WP Mail Catches uses to save logs. An additional column is_html is added to improve the html detection of the emails being recorded.

Normally this column would be automatically added when the plugin is updated so the user won’t need to do anything and the plugin will continue to function as normal. However a few users have mentioned that the column was not added which caused the plugin to throw errors.

2.0.5 adds an additional button in the WP Mail Catcher settings page to allow the user to manually re-trigger the migrations (in this case just adding the is_html column) so it can attempt to add the column again.

I hope that answers your question!

Hi @curiousrob, I’ve just released version 2.0.5 which should resolve the issue, it also adds a link in the settings page to manually re-run the migrations if needed

Hi @emilycestmoi, I’ve just released version 2.0.5 which should resolve the issue, it also adds a link in the settings page to manually re-run the migrations if needed

Hi Rob, I’ve opened this issue on the Github tracker to investigate this further and get a fix out in the next patch – so I’ll mark this topic as resolved, but feel free to respond on Github if you want to add anything further.

https://github.com/JWardee/wp-mail-catcher/issues/159

Cheers,
James

Hey @emilycestmoi, who knows – the mods work in mysterious ways! I handle all bugs on the GitHub tracker, I’ve opened an issue there to investigate and will get a solution out in the next patch. So will mark this topic as resolved, but feel free to respond on Github if you want to add anything further.

https://github.com/JWardee/wp-mail-catcher/issues/159

Hi @curiousrob, it looks like your db didn’t update itself. In the next patch I’ll add a button so it can be manually re-triggered, when you click it it’ll add the necessary column and solve the error.

P.S love the profile picture ??

Just released v2.0.3 which should resolve this issue. Let me know if anything else comes up

Hi @f14m07 thanks for the report, you’re right this is a bug. I’ll have a fix out in about 6 hours or so. I’ll reply to this thread and mark this as resolved once the fix is out.