jhebbel

But you dont support people on your site either….

They aren’t testing any new version, they have been saying that all year. Fact is it is a new owner who is milking the cow for every drop but not doing ANYTHING with it. This plugin is abandoned.

A per Version patch notes firld would be a good feature

Even the above blog says “The next version of Awesome Support is due to arrive in early 2019″…

No, this plugin has been abandoned over a year. The same person has said the same thing about testing new versions for months. Their GIT shows virtually no activity on the code base whatsoever all year.

Glad I saw this, I was about to screw up and buy some of the plugins, but not if I see they are a dead project.

My posts dont seem to show the featured image either, are they supposed to?

This is good enough for me, It is for a plugin I was writing anyway, so this will work perfect!

Yea, its insane considering the ridiculous cost of the plugins needed to even make this on par with some of the free solutions. I have no ide why they insist on using their own email wrapper instead of hooking the default wpmail so it could be compatible with all mail plugins…

I would like to see this as well, my software has a portal to access portions of our site that I would like to have a little bit easier access.

I have a recaptcha plugin for my login form, doesn’t show one on your plugin though. I use “Login No Captcha reCAPTCHA (Google)” 1.6.4

• This reply was modified 5 years, 6 months ago by jhebbel.

I have to pay every month for a pro version? Why are your pro version monthly and not a one time cost, I dont see anything that implies that you guys host or process the data that would explain a monthly fee.

Yes, me as well, having the user forced to select a worker is not wanted for me either!

Try getting rid of the other lines until it works, none of them are actually needed, you could just replace with array();

Don’t you love it when a developer abandons you? Anyway, I dug into their code and found the issue. I originally thought they weren’t using wp_mail() like they should be and thus sidestepping the filters our SMTP plugin puts in place, but it turns out the headers they are using are what is at fault.

Open “wp-content/plugins/awesome-support/includes/class-email-notifications.php”

Goto line ~806 and look for somthing like the following:

		/**
		 * Prepare e-mail headers
		 * 
		 * @var array
		 */
		$headers = array(
			"MIME-Version: 1.0",
			"Content-type: text/html; charset=utf-8",
			"From: $from_name <$from_email>",
			"Reply-To: $reply_name <$reply_email>",
			// "Subject: $subject",
			"X-Mailer: Awesome Support/" . WPAS_VERSION,
		);

Change it to read:

		/**
		 * Prepare e-mail headers
		 * 
		 * @var array
		 */
		$headers = array(
			"Content-type: text/html; charset=utf-8",
			"From: $from_name <$from_email>",
			"Reply-To: $reply_name <$reply_email>",
			// "Subject: $subject",
			"X-Mailer: Awesome Support/" . WPAS_VERSION,
		);

Notice I got rid of the “MIME-Version: 1.0”, It should work now, but you will likely have to make this change after each update they push.

• This reply was modified 5 years, 7 months ago by jhebbel.