Plugin Contributor
kaarel
(@kaarel)
I am currently not able to replicate this issue.
Is the subscription sent to Smaily right after creating order and checking the “Subscribe to newsletter” checkbox? Is the same subscriber in the WooCommerce store with subscribed status or unsubscribed status?
The only option for this kind of behavior might happen is when customer subscribes to newsletter after creating an order. From profile settings for example.
Or customer synchronization imports subscriber to Smaily. For example, a customer that made an order and didn’t check the “Subscribe to newsletter” checkbox, but has already been subscribed to newsletter.
@kaarel
Hello, thanks for your reply.
The steps to reproduce the error is the following:
1. Anonymous visitor (which is also unknown for Smaily) crates an order
2. During checkout visitor checks “Subscribe to newsletter” checkbox
3. Order is submitted and paid.
Expected behaviour:
4. Visitor’s email is successfully added to Smaily list of subscribers.
Actual behaviour:
4. Visitor’s email is not added to Smaily list of subscribers.
5. After any amount of time visitor’s email is still not added to Smaily list of subscribers (so if that’s supposed to happen during cron, it is still not being done).
@kaarel
Hello,
do you have any news on the subject?
Plugin Contributor
tomabel
(@tomabel)
@turtletrail
I am getting the expected behavior with my store. Are you still experiencing this issue?
I am still not getting people subscribed.
the issue is still not solved.
any help?
Plugin Contributor
kaarel
(@kaarel)
@turtletrail
I am still not able to reproduce your described bug. Only getting the expected behavior. The subscriber addition to Smaily should work as soon the customer has placed order when checking the subscribe to the newsletter checkbox.
During our latest update 1.4.1, we have added a notice to Smaily plugin`s admin page when there is no connection to Smaily API with current credentials. It there is no error message, everything should be okay with the Smaily connection and the problem may be connected with some other Store related settings.
Also, there may be some information about the problem in log files in the plugin directory.
