szabesz

One more thing: I have just checked the logs, and in our case the Order list probably was not generated as the plugin caused a fatal error:
CRITICAL Uncaught Error: Cannot access empty property in .../wp-content/plugins/html-editor-syntax-highlighter/hesh.php:492
And in hour case there was nothing to click on or any way to start the Survey.

Hi,
I agree, while the plugin is really useful and I would also like to say thanks, the recent addition of the Survey has turned out to be a big error, for example in our WooCommerce shop it made the Orders list vanish. What our shop managers got instead is just the Survey messages so as a quick fix I deactivate the plugin so that they can work.

Please notify us over here when we can safely re-activate the plugin. Thank you in advance!

Hi Alex,

Thank you for the quick response! I thought this change was intentional but now I’ve leant it wasn’t.

Thanks in advance for fixing it! And keep up the good work, Clearfy is the best WordPress tamer plugin!

Regards,
Szabesz

I am also waiting for this fix. Thanks @alx359 for reporting it. I do use the log file on production to track real issues and that is why any deprecation notice is just cluttering it and such code should be refactored asap, anyway.

I do not think that disabling php notifications is a “solution”. For those who keep an eye on and manage the WP logs – like me – it is not an option.

Thanks @webcraftic fro fixing it in the next release!

Thanks for informing us!

I should have checked it before posting this:
https://www.ads-software.com/support/topic/woocommerce-3-notices-in-log/

Anyway, it is easy to fix. I have already hacked the code but obviously it gets overwritten by an update, so the plugin author should do it ??

I think we all know the answer to this question: no. Common sense tells us that it will be impossible to be compliant and not “just in time” but ever… EU GDPR is outrageous out of the box.

Hello,
Any possibility of a reply to this?

Thank you for the reply, we are glad to hear you are working on it. Keep up the good work!

Hi @mbrsolution

Thank you for the quick reply! I am probably on the way to track down this issue. Since I moved the site to a subdirectory, some settings and code had to be adjusted, and I forgot about the add_filter(‘wp_mail_from’, function ()…) in my functions.php. In this filter I constructed the from address based on get_option(‘siteurl’), so that is why I started to get invalid email address.

My current guess is that because of the fatal error of trying to send the email when the Affiliate registered with the site, your plugin could not finish the registration process properly, hence the state of “Affiliate has been approved, but has not accepted terms.”

So my first question is: could you please test it by generating the same error, with something like:

add_filter('wp_mail_from', function () {
	return "[email protected]/subdir";
});

If you can confirm that indeed this is what caused the issue, you might be able to handle this scenario to make the plugin more robust. I understand that it is not really an issue with the plugin but still…

However, the most important question is still this one:
How do I manually set it to be accepted?
I want to set the state of the application to be accepted. What should I do?

Please advise. Thank you in advance!

Hi,

I have the very same issue. I do have “I have read and agree to the Terms and Conditions” enabled and it shows up in the form, but the registration went through.

How do I manually set it to be accepted?

Note that I have another issue, probably related. I keep Enable Debug on, so I have the log of this registration in question:

[05/xx/2017 8:37 PM] – SUCCESS : New Affiliate Registration
[05/xx/2017 8:37 PM] – SUCCESS : Sending an email to [email protected]

However, we did not get the email maybe because of this:

[31-xx-2017 20:37:40 UTC] PHP Fatal error: Uncaught exception ‘phpmailerException’ with message ‘Invalid address: (setFrom) [email protected]/live’ in /home/ilikeorg/public_html/live/wp-includes/class-phpmailer.php:1023
Stack trace:
#0 /wp-includes/pluggable.php(352): PHPMailer->setFrom(‘customer.care@b…’, ‘mydomain.com’, false)
#1 /wp-content/plugins/affiliates-manager/source/Util/EmailHandler.php(14): wp_mail(‘customer.care@b…’, ‘New Affiliate R…’, ‘New affiliate r…’)
#2 /wp-content/plugins/affiliates-manager/source/Pages/AffiliatesRegister.php(76): WPAM_Util_EmailHandler->mailAffiliate(‘customer.care@b…’, ‘New Affiliate R…’, ‘New affiliate r…’)
#3 /wp-content/plugins/affiliates-manager/source/Pages/PublicPage.php(67): WPAM_Pages_AffiliatesRegister->processRequest(Array)
#4 /wp-content/plugins/affiliates-manager/source/Pages/PublicPage.php(93): WPAM_Pages_PublicPage->proces in /home/ilikeorg/public_html/live/wp-includes/class-phpmailer.php on line 1023

As you can see the plugin tried to send the email to [email protected]/live

/live is the directory in which the site is located, as I moved it recently there, formally it was in the root of the linux account. When it was in the root directory the email address was OK, and all the affiliate registrations did work as expected.

Also Affiliates > Settings “Email name” and “Email address” were left empty both before AND after the move to /live.

After these errors, I filled in “Email name” and “Email address”, but I have not yet tested it with this setup. I will do it when I have the time.

Thank you for the tip! I will try it as soon as I have time.
No istructions are included in the changelog which I did read:
– fix google captcha issue in form preview
– add prefix to the custom tables
I guess the last one is the problematic change.
What careless developers. Shame on them.

• This reply was modified 8 years, 1 month ago by szabesz.

Thank you for you clarification! I am new to this plugin, but I like what I’ve seen so far. Keep up the good work!

Hi @team Heateor,

Thank you for your quick reply. I’ve just prepared a test environment for you (on the very same server, but another instance of the site) so that you can take a look at the site, however, on this cloned version of the site I do not get the warnings. I will further investigate the issue and will be back to report on the results.

The strange thing is that I also get the warnings on my local machine (a clone of the site I use for development).

Hi Hash,

While we are waiting for Thomas’s answer, I can report that I have just updated my site to WordPress 4.6 and running WP-Forge 6.2.3.1 without any problems.

cheers
Szabesz