Jump to content
daniels

Subscribe To Mailchimp

Recommended Posts

Hi @daniels, on a site, where I had installed and used the module since its first release, the subscribe method doesn't work anymore.
To clarify: The module is upgraded to the last master version.

Could it be, that there was a change introduced by MC, maybe two months ago? Since then it seems not to work anymore.
I setup a logger at these two points:
A) https://github.com/danielstieber/SubscribeToMailchimp/blob/fd5039ec94e2b4ad49458ce090a240ba2d3979d6/SubscribeToMailchimp.module#L53
and
B) https://github.com/danielstieber/SubscribeToMailchimp/blob/fd5039ec94e2b4ad49458ce090a240ba2d3979d6/SubscribeToMailchimp.module#L62

The responses are now all the time:

A) (status) 401
B)

{
  "type":"http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/",
  "title":"Resource Not Found","status":404,"detail":"The requested resource could not be found.",
  "instance":"c31XXX66-XXXX-XXXX-XXXX-47c61XXX89eb"
}

Do you know about any changes?

EDIT:
This only happens when I try to subscribe a NEW user. When I send a already known user, I get back correct responses, like before:
A) (status): unsubscribed or subscribed
B)

{
   "id":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
   "email_address":"mctest13@xxxxxxxxxxx.xxx",
   "unique_email_id":"xxxxxxxxxxx",
   "email_type":"html",
   "status":"pending",
   "merge_fields":{"FNAME":"","LNAME":""},
   "stats":{"avg_open_rate":0,"avg_click_rate":0},
   "ip_signup":"xxx.xxx.xxx.xxx",
   "timestamp_signup":"2018-04-25T14:56:05+00:00",
   "ip_opt":"xxx.xxx.xxx.xxx",
   "timestamp_opt":"2018-04-25T15:11:24+00:00",
   "member_rating":2,
   "last_changed":"2019-04-04T08:15:30+00:00",
   "language":"",
   "vip":false,
   "email_client":"",
   "location":{"latitude":0,"longitude":0,"gmtoff":0,"dstoff":0,"country_code":"","timezone":""},
   "marketing_permissions":[],
   "source":"Unknown",
   "tags_count":0,
   "tags":[],
   "list_id":"xxxxxxxxxx",
}

 

Share this post


Link to post
Share on other sites

Hey @horst,

thanks for reaching out. I have to check the details, but just on first sight:

I think error B is just because of a problem at A. Line 62 is not supposed to be executed for new user.

I'm very sorry, but I won't be able to look into it before Friday/Saturday due to a business trip. I made a todo and will do some testing and refactoring when I'm back.

Maybe a quick and dirty fix for you meanwhile:

With an if, check If you get the 404 in line 62 (patch), and if yes, execute the post request which is supposed to be executed for new users:
$response = $http->send($api, json_encode($param), 'POST');
 

 

Share this post


Link to post
Share on other sites

Hi @daniels,

thanks for the quick response! Now, when so say it, maybe I have added a bug by myself when editing the module to add the logger. I've also wonder why not the other send method was invoked. I will check / resolve that and post here again with the new results before friday!

Share this post


Link to post
Share on other sites

Hi @daniels,

I'm using your module and I have to thank you a lot, it is saving me hours of time.

However I'm facing a problem: if I subscribe a user (goes fine), unsuscribe him (goes fine too) and then try to subscribe him again there goes nothing. He stays with the "Unsubscribed" status inside my Audience section of the Dashboard.

How could I try to solve this issue?

Thanks!

 

Share this post


Link to post
Share on other sites

If I remember correctly that has to be enabled in Mailchimp first. Allow someone to re-subscribe again. 

Share this post


Link to post
Share on other sites
On 4/7/2019 at 8:17 PM, horst said:

Hi @daniels,

thanks for the quick response! Now, when so say it, maybe I have added a bug by myself when editing the module to add the logger. I've also wonder why not the other send method was invoked. I will check / resolve that and post here again with the new results before friday!

Hi @horst,

I'm facing similar problems with subscribing a new user to my list, here is my code: (an hook for the LoginRegister module by ryan)

wire()->addHookAfter('LoginRegister::processRegisterForm', function($event) {
    $form = $event->arguments[0];
    foreach($form->getAll() as $f) {
        $name = $f->attr('name');
        if(strpos($name, 'register_') !== 0) continue;
        if($name == 'register_subscribe_newsletter' && wire('input')->post->register_subscribe_newsletter == 1) {
            $mc = wire('modules')->get("SubscribeToMailchimp");
            $email_dirty = wire('input')->post->register_email;
            $email = wire('sanitizer')->email($email_dirty);
            $subscriber = [
                'FNAME' => wire('input')->post->register_nome_iscritto,
                'LNAME' => wire('input')->post->register_cognome_iscritto
            ];
            $mc->subscribe($email, $subscriber);
        }
    }
});

And here is what the mailchimp console said about the request:

Cattura.thumb.JPG.005781d18809040f419525c754e4f0b6.JPG

I've tested everything I can imagine (list_id, api key, etc...) but nothing.

I've also tried to edit the line 62 of the module with

$response = $http->send($api, json_encode($param), 'POST');

but the error still remain....

Did you solved it somehow?

Thanks!

 

EDIT:

I've solved changing line 54 of the module from:

if($status !== false) {
//...
}

to

if($status !== 404) {
//...
}

Basically Mailchimp returns a status of 404 (and not false) when the module tries to insert a new user. This is correct because the user is not there in the list at first.

Share this post


Link to post
Share on other sites

Hey @horst, @3fingers,

I'm very sorry for the late response. I finally found some time to look into this.

@horst at the beginning, you mentioned a 401 error. I think this could be caused by a wrong audience id. But seems like this was no problem later?

- Regarding 404: you get a 404 for every new user, because the "getStatus" method simply can't find a status for that user. This is absolutely correct behaviour and the check itself is suggested by the API documentation. I guess it is not a good idea to log this as a warning, as it is part of the normal process. I removed that.

- @3fingers do you have double opt-in enabled or disabled? there was an extra 'if' on line 55 that has caused problems with resubscription when double opt-in was disabled. This should be fixed in 0.0.5. Thanks to jliebermann for posting this issue on github. (Note, that after a 'resubscribe', the user has to confirm his email adress again and will disappear in your "contacts" list until he does that!) 

- @3fingers your solution with updating line 54 can not really work, because the $status you are checking is not the HTTP_STATUS. It is supposed to be the subscription status, and it will be false, when you (correctly) get a 404 during the API call. So there should never be a 404 in $status 🤔.

Besides that, I changed the wording in the readme and comments from 'list' to 'audience', since this is the new wording by Mailchimp. Version 0.0.5 is live in a minute. Appreciate your feedback.

Thanks a lot for posting your issues and for your patience! Trying to answer you faster next time. Let me know if you still have problems.

  • Like 5

Share this post


Link to post
Share on other sites

hello, I need some help with a strange error:

Raw data option with CURL not supported for PATCH 

I checked all parameters and they are ok, any idea? I'm using PW 3.0.141 dev

Share this post


Link to post
Share on other sites

Hey @Sevarf2,

the module is using WireHttp. It seems like wirehttp introduced a curl fallback as mentioned here

You could try to play around with the options of the send methods in the mailchimp module e.g. trying socket instead of auto (=curl?) as a fallback  (here are the options of the send method of http wire https://github.com/processwire/processwire/blob/dev/wire/core/WireHttp.php#L434). Let me know if this makes a difference!

Another possibility:
Have you made the module work on that same server already? Maybe there are some serversided settings that make problems with curl.

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, daniels said:

Hey @Sevarf2,

the module is using WireHttp. It seems like wirehttp introduced a curl fallback as mentioned here

You could try to play around with the options of the send methods in the mailchimp module e.g. trying socket instead of auto (=curl?) as a fallback  (here are the options of the send method of http wire https://github.com/processwire/processwire/blob/dev/wire/core/WireHttp.php#L434). Let me know if this makes a difference!

Another possibility:
Have you made the module work on that same server already? Maybe there are some serversided settings that make problems with curl.

I added a parameters array to the send command using socket as fallback as suggested, don't see the error anymore but neither the user subscribed 😞

$params = array(
   'fallback' => 'socket',
);
$response = $http->send($api . '/' . md5($email), json_encode($param), 'PATCH', $params);

Share this post


Link to post
Share on other sites

 @Sevarf2 thanks for giving it a try. I'll try to reproduce your error in the next days, maybe I can find a solution. sorry for your troubles.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
12 hours ago, daniels said:

 @Sevarf2 thanks for giving it a try. I'll try to reproduce your error in the next days, maybe I can find a solution. sorry for your troubles.

thanks, I appreciate.

Share this post


Link to post
Share on other sites

Did anyone figure out the issue with error:

Raw data option with CURL not supported for PATCH

I'm having the same issue, and digging around can't see where the issue is...

Any help would be greatly appreciated.

UPDATE: Thought I'd sorted it but it turns out I haven't. I've added a log to output the parameter to make sure that data is set and not empty and it appears to be correct: {"email_address":"someemail@here.com"} yet I'm getting the PATCH error.

Hoping someone has figured this out 🙏

Edited by alexmercenary
NOT SOLVED

Share this post


Link to post
Share on other sites
On 4/28/2020 at 2:22 PM, alexmercenary said:

Did anyone figure out the issue with error:

Raw data option with CURL not supported for PATCH

I'm having the same issue, and digging around can't see where the issue is...

Any help would be greatly appreciated.

UPDATE: Thought I'd sorted it but it turns out I haven't. I've added a log to output the parameter to make sure that data is set and not empty and it appears to be correct: {"email_address":"someemail@here.com"} yet I'm getting the PATCH error.

Hoping someone has figured this out 🙏

@alexmercenary, Maybe the fix here will help you: https://github.com/danielstieber/SubscribeToMailchimp/issues/9

 

I am also having troubles using this module. 

The test for the api settings works but when i try to subscribe a user it does not work. I dumped the response text and I get 

"{"type":"http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/","title":"Resource Not Found","status":404,"detail":"The reques ...

I am on localhost at the moment but I guess that should not matter? Anybody had this problem so far?

 

 

EDIT: Problem fixed with 0.0.6 dev branch on github. 

Share this post


Link to post
Share on other sites

Hey all,

open issues are fixed in 0.0.6 (changelog), you can update it now. I would strongly recommend to update it, as there were major issues regarding subscription of new users.

Thanks for your help and patience! Keep me updated if you run into errors ❤️

 

  • Like 3

Share this post


Link to post
Share on other sites

Hi,

I have not clear how to update a user information. Is it possible?

Ok super easy! Just use $subscriber method!
Wow thank you, this really speeds up my work!

 

Share this post


Link to post
Share on other sites

Hey @Marco Ro,

you should be able to update user information with the subscribe method. If a user is already subscribed, it overwrites / sets field values. Let me know if this doesn’t work.

Users can not update their mail adress though.

In general, users can probably update their data and settings via Mailchimps preferences link directly in MC. The module is not meant to be a Mailchimp database editor, viewer or sync, it is mostly made to add People to MC without saving their personal data on the webspace. 

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @daniels,

Yes, the subscribe method works very well. I have just tried and all the fields are correctly updated.

Thank you for your module, this really speeds up my work.

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

There is a way to use an antispam system instead of using the opt-in or reCAPTCHA ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...