firebird75

Awesome, thanks for your prompt answer!!!

Hello,

Thank you for testing! I guess the right thing to do would be to not pass the email to Stripe if it isn’t valid and not a mandatory requirement in current configuration. That way, Stripe wouldn’t check it out and reject the order.

A lot of people don’t have a mail or don’t want to share it. They will eventually fill in dummy data just to make sure they have filled in all fields. This is a natural behavior. Rejecting orders because of that isn’t a good business practice. Control is ok as long as it doesn’t hurt business ??

Thanks a lot for taking the time to reply ??

Thank you for your answer. This core use of the API is for logged in users only, isn’t it? So if I disable it for non logged in users, it is safe and won’t hurt the site, isn’t it?

Thanks again!

Hello Joey,

Have you set the email to not be required via hooks? Here is the code I use to achieve that :

add_filter('woocommerce_checkout_fields','custom_override_checkout_fields');
  
function custom_override_checkout_fields($fields)
{
	$fields['billing']['billing_email']['required'] = false;	

	return $fields;
}

Thank you!

I have checked and found out that the table had been created as with latin1_swedish_ci encoding. So I have checked the plugin code and it looks like you aren’t explicitly setting the character encoding to be used. This is what is causing the issue to happen. The right way to create the table is to check user DB charset and then to explicitly force it for new tables. Otherwise, it will switch down to random values and eventually cause problems.

Here is a code snippet to help you :

	if ($wpdb->has_cap('collation')) 
	{
		if (!empty($wpdb->charset))
			$charset_collate = "DEFAULT CHARACTER SET $wpdb->charset";
		if (!empty($wpdb->collate))
            $charset_collate .= " COLLATE $wpdb->collate";
	}

$wpdb->query("CREATE TABLE IF NOT EXISTS {$wpdb->prefix}mytable (
	  id int(11) unsigned NOT NULL auto_increment,
	  optionvalue text,
	  PRIMARY KEY  (id)
	) $charset_collate;");

The query part is missing quotes (those get stripped off in this editor).

To fix the issue for existing installs, you will need to alter the DB encoding for your plugin tables. This should correct the issue.

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

Right now, this isn’t possible. If you are looking for this feature, please reach out to me directly via the official website to see how it could be Added to the premium release.

Hello Emad,

I am not sure I understand the question. When a ticket is submitted or updated, an email notification is sent out (in the premium release). The update is also available in the single ticket page in the frontend.

There is a true bug, this has been confirmed by the folks on Github. It will be fixed in next release.

Indeed the issue is also on this demo site :
https://demo.woothemes.com/storefront/checkout/

I can’t really play with themes on a live site to debug this issue. I have checked the source code and both forms are with woocommerce namespaces so I assume that those are generated by woocommerce…

Have you enabled the registration on your woocommerce? I guess the unexpected one is the login nonce.

Please contact me via email or through the official website. I don’t provide premium support here (this is just not allowed). I have other ways to deliver the plugin for people with Gmail addresses.

Hello,

Replies to tickets are achieved via comments in the frontend.
Feel free to contact me via the official website for further support.

Thanks!

Hi,

No, the login data is the WordPress one.
You can modify email notification Template to include user data into it via filter hooks.

Regards,

Olivier