Error message extraction:
- phpList v3 nests the actual message inside data.message:
{"status":"error","data":{"code":0,"message":"invalid call"}}
Previous code read data as a raw value and got "Array" in the logs.
Now checks data.message first, falls back to top-level fields.
listSubscriberAdd:
- Send both naming conventions (listid/subscriberid AND list_id/subscriber_id)
so the call works regardless of which phpList REST API build is installed.
- Add debug log line showing exact param values sent, making future
diagnosis straightforward without needing server-side inspection.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
phpList REST API v3 returns subscriber data wrapped in a "data" key:
{"status":"success","type":"Subscriber","data":{"id":"2400",...}}
Both subscriber_get_by_email and subscriber_add responses are now read as
response['data']['id'] with a fallback to response['id'] for compatibility.
Previously the code checked only response['id'] (top level), found nothing,
and reported failure even though the subscriber was created successfully.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Root causes identified from logs:
1. All params (login, password, cmd, email, etc.) were appended to the URL
query string; phpList REST API v3 expects them in the POST body.
wp_remote_post now sends body=>$params instead of an empty body.
2. subscriber_get_by_email and subscriber_add called rawurlencode() on the
email before passing it to call(), which then ran http_build_query() on
it again — double-encoding '@' to '%2540'. Both rawurlencode() calls
removed; wp_remote_post handles POST body encoding correctly.
Additional improvements:
- endpoint_url() returns just the bare ?page=call&pi=restapi URL
- On API error, log full_response (entire JSON) not just the message field,
so phpList's exact reply is always visible in WC Status Logs
- Non-JSON response now gives an explicit error message pointing to the
endpoint URL / credentials rather than a generic JSON parse failure
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- New WooList_Logger class writes to wp-content/uploads/woolist-logs/woolist.log
- INFO level: subscription events, test connection results (always recorded)
- ERROR level: API failures, config problems (always recorded + php error_log fallback)
- DEBUG level: full request URLs (password redacted), raw responses, step-by-step
flow (only when "Enable debug logging" is checked in settings)
- Auto-rotates at 1 MB; log directory protected by .htaccess
- API class: logs every request URL (redacted) and raw response body at DEBUG,
errors at ERROR; subscribe_email_to_list logs each step (lookup/create/add)
- Hooks class: logs hook fire, skip reasons, and sync intent at DEBUG/INFO/ERROR
- Shortcode class: logs AJAX submissions, coupon generation, and failures
- Admin: new Logging section with "Enable debug logging" checkbox;
log viewer textarea (last 300 lines, dark theme) + Clear Log button
both visible at bottom of WooCommerce → Settings → phpList tab
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- phpList REST API wrapper with subscriber get-or-create + list assignment
- WooCommerce Settings tab (5 sections: connection, orders, signup, newsletter)
- Test Connection button via admin-post action
- Hooks for order completed/cancelled and user_register events
- [woolist_newsletter] shortcode with jQuery AJAX, fixed & auto-generated coupons
- Responsive front-end form styles and JS with loading/success/error states
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
