daniels

No worries I suggest testing the subscribe function in a normal doc with test data. If this works (which should :)) try to dump your real data wherever you want to implement the subscription. If you can var_dump the right data there, you should be able to perform the subscription there Let me know if you have questions regarding the module itself or run into errors there.

Ok @MarcoPLY , I think I got your question completely wrong I leave my reply anyway if someone needs it one day... Have you tried to var_dump the subscriber? What do you get there? Is the $ before country_title intentional?

Hey @MarcoPLY , not sure if I get it right, but do you want to add user to specific categories? In the API naming, groups are called 'interests'. You can add them as additional parameters as in the example below. To get the interest IDs is a little pain-in-the-ass but I'll try to guide you: 1. Go to https://api.mailchimp.com/playground/ and enter your API key. 2. Click on 'Lists' and choose 'interest-categories' from the 'Subcategories' of your related list. 3. Choose 'interest' from 'Subcategories' of your related interest category 4. Now you can click on each interest and you'll get the id which should be the ID that you have to use in the 'interests' part of the example below. Please let me know if this works for you! When I find some time, I'll add a way to get these ids in the module Settings in PW admin. Example from the docs: // Work with additional parameters (not merge_field values!) $mc->subscribe('john.doe@example.com', NULL, NULL, [ 'language' => 'en', // find language list here: https://kb.mailchimp.com/lists/manage-contacts/view-and-edit-contact-languages#Language-Codes 'vip' => true, // boolean vip status 'location' => [ // geo location based on lat/log coordinates 'latitude' => '48.8722344', 'longitude', => '2.7736192' ], 'interests' => [ // subscribe user to interest categories / groups based on group id '32fec3561e' => true, '63mel4395m' => false ] ]);

Ok, thanks anyway. I think it might have something to do with is_file(). I have worked around it for now

@LostKobrakai thank you so much for your great driver, I use and love it for quite a while now. I just experienced something weird, and I'm not sure if it has to do something with valet and your driver: I'm in the need of accessing a non-processwire php file in the processwire root (e.g. domain.test/myfile.php). On my staging & live server, this works great – on my local dev environment (including valet and your driver), I land on the 404 processwire page. I tried a few things: On Staging (with valet): domain.test/myimage.png -> domain.test/custom/myimage.png -> domain.test/myfile.php -> domain.test/custom/myfile.php -> On Live Server (apache): domain.com/myimage.png -> domain.com/custom/myimage.png -> domain.com/myfile.php -> domain.com/custom/myfile.php -> Is it possible that it has something to do with valet and the driver? Or could there be other reasons? Best, Daniel

Updated to version 0.0.4 - checkout the changelog . The Github user ml-s fixed a major issue, where you could not use a Mailchimp core function, the ADDRESS mergefield.

I've just rolled out version 0.0.3 - checkout the changelog . You should be able to update without any changes in your code.

Thanks for your effort @flydev, let me know if you need some updates in the SubscribeToMailchimp module. The module would not be what it is made for, if you cant use it with the loginregister or any other way a dev prefers. I just want it to stay lightweight and flexible.

I've created an issue regarding features of MailChimp, that currently can't be used with the module. Also I'd like to make it more flexible, if Mailchimp roles out new stuff. My question to you: Do you currently use this MailChimp features or would like to have it in the module? - Groups (Interests) (Setup up - VIP - manually fill IP, Language and/or Location

Thank you for the feedback @MarcoPLY I've not worked with loginRegister and hooks yet. If you or someone finds a solution, please share it in here

@horst this is awesome!! Thank you, I will totally merge it in. It looks really great and is super helpful. I didn't even know, that this is possible via the module settings I also had a look at the issue mentioned by @Mikel . To resubscribe users (and I think this is indispensable) I had to add a getStatus method and change how the subscription method works. Now if a user resubscribes, he will get the double-opt-in mail again. I made a PR for this too, maybe you can take a look. I will merge both PRs than to version 0.0.3 (and hopefully don't mess it up .... :D) later this week. https://github.com/danielstieber/SubscribeToMailchimp/pull/2

Hey @Mikel, seams like with the original mailchimp subscribe forms, it is possible (and in my opinion it should be) to resubscribe. I will have a look on that! Thanks for the input. Meanwhile (e.g. for testing) you can use the delete method to completely delete and resubscribe a user. That is working for me with the current version.

Oh, that is cool. Thank you for help and clarification @LostKobrakai

Hey, thanks for the feedback @giannisok and for the solution @wbmnfktr. I have just updated to version 0.0.2 with the ability to unsubscribe and delete users. I also removed the 'string' type declarations, hope it works now with your PHP version @giannisok . When I have the time I'll change my dev machine setup, so I can test with different PHP versions. But since I use Valet, I think I can only downgrade to php5.6 anyway.

Sorry for rewarming this old beauty, but it was the closest answer to what I'm looking for by forum search and google. For my privacy policy and cookie information, I currently create a list of all cookies that are used by a PW-site. I'd like to provide my users an easy to understand but still informative idea of what the cookies are for. Here is an example: __utmb: Cookie by Google-Analytics that contains a timestamp of a users first visit. Together with __utmc, it can provide information about the time, a user spent on a page. Lifespan: until the end of a session For the wire cookie, I currently have: wire: Necessary cookie by ProcessWire, the CMS-system of the website. It stores and identifies a user session. Lifespan: one year Is this correct and/or can you maybe give me a hint of what I could write here, so a user gets an idea about the necessity? Thank you so much!