scody

Hello @hakikzaman

Not sure from which version I started but the issue seems to have started from the update in version 1.1.9. Now currently I have updated to version 1.1.13 and the issue is resolved in this version.

Hello @supportadtribes

Thanks for the update. I have checked the newly generated review feed, it has indeed removed the review with no text in them.

There is just one more issue with the newly generated review feed in the case of variable products. I will explain the issue with an example here,

Let’s say there is a product “Ninja T-shirts” with two color variants Red and Black, and has just 1 review for one of them, for the sake of simplicity. Now the generated XML feed has 3 review nodes, one for each of the variants and one with the base product name. It is fine if the review node is created for each and every variant, but the problem is with the review node created for the base product name. In this example review nodes for “Ninja T-shirts Red” and “Ninja T-shirts Black” is fine as it will have the corresponding identifiers like SKU, MPN, GTIN, etc. but the review node created for the base product “Ninja T-shirts” will not have any corresponding identifiers, so this makes the review node invalid.

I was wondering whether this redundant review node for the base product can be removed, as all the variants review nodes are already present in the feed.

Please check if this can be solved.

Thanks in advance.

Thanks for your quick reply.

We have mapped the GTIN field to product SKU, but for a few of the products, this is not true so we want remove gtin tag for them.

How can we achieve this?

Hi Patrick,

Thank you for your solution.

Now I have checked the option to subscribe user automatically, as directed by you. But will this work on already collected data in the Emails list? If not how can we transfer that data to Mailchimp?

Thanks

Thanks @khungate, for a quick reply. We are getting this below response for the cURL command,

* About to connect() to xxxx.api.mailchimp.com port xxx (#0)
*   Trying xxx.xxx.xxx.xxx...
* Connected to xxxx.api.mailchimp.com (xxx.xxx.xxx.xxx) port xxx (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate:
*       subject: CN=wildcardsan2.mailchimp.com,OU=IT,O="The Rocket Science Group, LLC",L=Atlanta,ST=Georgia,C=US
*       start date: Jul 09 00:00:00 2019 GMT
*       expire date: Oct 07 12:00:00 2020 GMT
*       common name: wildcardsan2.mailchimp.com
*       issuer: CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US
> GET /3.0/ecommerce/stores?apikey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx HTTP/1.1
> User-Agent: curl/7.29.0
> Host: xxxx.api.mailchimp.com
> Accept: */*
>
< HTTP/1.1 503 Service Unavailable
< Server: Apache
< Content-Length: 125
< Content-Type: application/json
< ETag: "953d389c654d003dd7a67b8f959df97a:1452000673"
< Cache-Control: max-age=71090
< Date: Tue, 26 Nov 2019 13:55:45 GMT
< Connection: keep-alive
<
* Connection #0 to host xxxx.api.mailchimp.com left intact
{"type":"akamai_error_message","title":"akamai_503","status":503,"ref_no":"Reference Number: 00.d5bbc217.1574776545.5567624"}

Kindly advise the next steps.

Thanks

Yesterday, I was able to install the plugin (v 1.9.13) via plugins page, after that, I was hoping my account lockout issue will be resolved. Today when my account came out of lockout I went on to reconnect my Woocommerce to Facebook and update my API key, as soon as I log in my Facebook account gets locked out again.

What is the Security issue you have fixed in 1.9.13? Is it been tested?

Any update on this?