EkoJR

Thank you for the kind words

Sorry for the delay; was mostly waiting on DNS propagation.

If you would like, contact me and I’ll supply you with a code so you can get the Pro version.

Pagination is one of the features that got built into the Pro version. Which is currently down; so over the weekend I’ll have to get it back online, and push an update for it.

Adding support for pagination isn’t something that can be easily implemented, but on the Pro version it adds some additional functionality and internal shortcodes to make it easier.

Not directly, but it is possible I’ve applied a fix for that in the newer version since I did come across a bug with add_meta_boxes hook. There were a few other fixes I added that weren’t directly related to the situation.

The plugin isn’t closed. Currently it’s temporarily down and pending review.

There’s been some changes added to resolve a situation, and there were additional changes added over the weekend; the download zip should work in GitHub, although it is a dev repository. When WP approves it, it should be back up for others to get the download here.

Well, I was been able to get a traceback with a phpmailerException to /wp-includes/class-phpmailer.php on line 1337.

Why it is occuring is still trivial.

• This reply was modified 5 years, 10 months ago by EkoJR.

It was passing the correct Name and Email values.

I did a clean install after enabling that setting. No luck. I also went in and did some debugging and it’s rather odd why this is occuring. Especially when other plugins that use wp_mail have no problems.

I added a hook to catch phpmailer errors

function action_wp_mail_failed($wp_error) 
{
    return error_log(print_r($wp_error, true));
}

add_action('wp_mail_failed', 'action_wp_mail_failed', 10, 1)

…and I did catch [phpmailer_exception_code] => 2. Which would appeared to be an issue with header From or Reply-To. However, none of the modifications had positive results; even when the header param was completely removed from wp_mail.

I did also however setup a clean WP site and it passed. Even adding additional themes and plugins. So, I don’t think the host is blocking it. Although, the live site is a multi-site instead.

What doesn’t make sense is the live site’s wp_mail() is functioning as it should except for the AwesomeSupport plugin. I’m not sure what other changes may have occurred indirectly, but it didn’t look like there were many changes that occurred in WPAS_Email_Notification::notify().

• This reply was modified 5 years, 10 months ago by EkoJR.
• This reply was modified 5 years, 10 months ago by EkoJR.

Yes, I did do a clean install of the plugin, and theoretically it should be a clean install; assuming the plugin uses the uninstall hook and properly removes all the data. However, when I reinstalled, old tickets were still present, and I didn’t see any additional options to delete all plugin data.

I also haven’t had any problems with other plugins that use an email notification. So, I don’t think my hosting provider would be the issue.

This would be an upgrade. I received emails a year ago when initial testing, but the plugin was left dormant.

Screenshot of email setting https://imgur.com/a/DgLw87A

I did deactivate & uninstall, and then tried to clean up the data as best as I could before reinstalling. I also went through checking for plugin conflicts and didn’t found anything.

Unfortunately mail() on localhost is essentially useless, and I don’t have anything setup to do remote debugging. I suppose I could still breakpoint it, but haven’t had the chance yet, and that’s also assuming the migration to localhost preserved the issue.

Was mostly curious if something changed and was reported.

Thank you for the rating. Much appreciated.

That PHP function should convert the string to an int.

Ah, thank you! That resolves the issue.

Thank you for reporting this. It could be a number of possible reasons the issue is occurring, and will need to further investigate it.

I’ve opened an issue on Github – Conflict with Siteorigin Page Builder.

• This reply was modified 6 years, 8 months ago by EkoJR. Reason: Grammar Corrected

Thank you for looping back around, and no worries.

I remember you left a review when APL was going through a dark age, and remember reaching out to you when APL was starting to get some light. Ultimately, I was hoping to improve APL’s rating with a revised version of your review.

I believe it was 0.3.B6 is when you last used the plugin. Since then, there’s been a lot added to the changelog ??