-
Notifications
You must be signed in to change notification settings - Fork 25
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
Subscription status not showing #494
Comments
I’m unable to reproduce. The |
@bencroker this is when i try to add an address again: When i add it for the first time there are no error. |
I’m not really seeing anything useful in those URLs. Might a video with the network tab open with the response show more? |
@bencroker I can sent you a link to a google drive file with a video. I couldn't add support@putyourlightson.com as a viewer to the file. What email address should i use? |
Please email a shareable link to support@putyourlightson.com. |
Done! |
Thanks for the sending the video! This turned out to be an issue that only affected draft contacts. Existing contacts are unaffected by it. Fixed in 9dcbd7b for the next release, which should be early next week. |
Release in 3.5.0. |
Bug Report
When i add a contact to a mailing list, i get the notification that the contact is subscribed and i see the subscription status change from none to subscribed. If i reload the page, the status says none. If i try to subscribe to contact again, i get the following error message:
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '301226-219361' for key 'idx_fakcaygyicgsxcbhexsritkrmfcnqxtrxkxd' The SQL being executed was: INSERT INTO
campaign_contacts_mailinglists
(contactId
,mailingListId
,subscribed
,sourceType
,source
,subscriptionStatus
,dateCreated
,dateUpdated
,uid
) VALUES (301226, 219361, '2024-09-10 07:28:26', 'user', '1', 'subscribed', '2024-09-10 07:28:26', '2024-09-10 07:28:26', '1f62e88f-6e2f-4018-9d6a-a6b2f41e5b1e')Plugin Version
3.4.3
Craft CMS Version
5.3.5
PHP Version
8.2.23
The text was updated successfully, but these errors were encountered: