New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mailchimp script failing #870
Comments
The relevant bit of code only runs if Mailchimp returned an error ("errored_operations" > 0): jethro-pmm/scripts/mailchimp_sync.php Lines 260 to 294 in 9d0f015
This is not a common codepath, and it's quite possible Mailchimp now returning something the script doesn't expect. Specifically, the script assumes the returned bytes are a Perhaps you could edit jethro-pmm/scripts/mailchimp_sync.php Line 266 in 9d0f015
Copy the tar.gz somewhere for later inspection:
Then see what's in it:
|
Having experienced this for myself, I can confirm it happens when Mailchimp returns errors in a tar.gz file with an unnecessary
See attached response.tar.gz for an example. The PHP code: <?php
$tgzfile="response.tar.gz";
$p = new PharData($tgzfile);
$p2 = $p->decompress();
$p2->extractTo("subdir", NULL, TRUE); results in the error:
|
#870 - properly parse Mailchimp's broken tgz file with '.' entry
Hi,
The mail chimp script is failing with an exception:
Fatal error: Uncaught PharException: Extraction from phar "/tmp/jethro-mc-1676867940/response.tar" failed: Cannot extract ".", internal error in /home/aliceang/public_html/jethro/scripts/mailchimp_sync.php:271
Stack trace:
#0 /home/aliceang/public_html/jethro/scripts/mailchimp_sync.php(271): PharData->extractTo('/tmp/jethro-mc-...', NULL, true)
#1 /home/aliceang/public_html/jethro/scripts/mailchimp_sync.php(81): run_mc_sync(Object(DrewM\MailChimp\MailChimp), 2, '41f1a38d0e')
#2 {main}
thrown in /home/aliceang/public_html/jethro/scripts/mailchimp_sync.php on line 271
==
It worked a few days ago. I'm unaware of having changed any mail chimp related settings either on mail chimp or in Jethro.
thanks,
Kristan
The text was updated successfully, but these errors were encountered: