Carlo Roosen

Hi Dionne,

Please contact me by mail, I will help you out mail at carloroosen dot nl.

Carlo

Hi Booktastik. If you add the category to the user meta data it will automatically appear in the list on the plugin options page. When you select the item will be copied to CM.

There are several ways to add user meta data. This is beyond the scope of the plugin, it depends on how your user registration works.

Hi dDon,

I changed the description so it reflects better what the plugin does exactly.

The original bug is solved (Fatal Error on Activate). And I changed the description of the plugin so hopefully people do not get the wrong expectations. It seems the topic is resolved ??

I am sorry about the confusion.

The Campaign Monitor Synchronization plugin is for a different use case than (just) subscribing users to a mailinglist. It is meant to create and maintain a mailinglist based on the list of registered users inside WordPress.

I have added a warning in the description, please let me know if you think this will help future users from falling in the same trap.

Hi Booktastik,

I am very sorry your data is corrupted by the plugin.

From your description it seems that you started with an existing list of users in Campaign Monitor (maybe with additional fields that are not defined in WordPress).

The designed behavior of the plugin is that it not only adds users from WordPress to CampaignMonitor, it also removes users from Campaign Monitor that do not exist in WordPress. That is what “synchronization” from WP to CM implies. Therefore the first step in the instruction is to start with an empty list in CampaignMonitor.

Let me know if this is the case for you.

Hi,

I am very sorry your data is corrupted by the plugin.

From your description it seems that you started with an existing list of users in Campaign Monitor (maybe with additional fields that are not defined in WordPress).

The designed behavior of the plugin is that it not only adds users from WordPress to CampaignMonitor, it also removes users from Campaign Monitor that do not exist in WordPress. That is what “synchronization” from WP to CM implies. Therefore the first step in the instruction is to start with an empty list in CampaignMonitor.

Let me know if this is the case.

The conflict arose because both plugins tried to load the same library. The problem should be solved now. Please install version 1.0.2 and let me know if it works.

Good luck!

Hi dDon, good question, indeed it is not very clear.

1) For the list ID go to List & Subscribers, select the list you want. On the top part of this page, click the link “change name/type”.

Or, construct an url like this:
https://[accountname].createsend.com/subscribers/createList.aspx?listID=[short list ID]&action=edit

You will find the list ID for the API, it is a 32 character hexadecimal string.

2) You can find the api key by clicking “Account Settings”at the top of the page.

Or, construct an url like this:
https://[accountname].createsend.com/admin/account/

In both cases, click “show API Key” to reveal the key. It is also a 32 character hexadecimal string.

Hi,

We decided not to implement multiple fields right now. The problem we ran into is that Campaign Monitor needs to know beforehand if a filed can contain multiple values. We can solve this, but then we need extra options in the plugin. And we want to keep it simple if possible.

If anyone reading this needs multiple fields, let us know, we might reconsider this decision when many people need it.

Regards, Carlo

Hi Neil,

No problem at all ! I am very happy with people using DirectEdit in this early stage of the product.

Also, in fact DirectEdit should not break even when you load jQuery twice, I will look into that next week.

Thanks for your nice review :). Could you please also mark the plugin as “working” for 3.8?

Thanks for your feedback!

Our plugin uses this WP function to get the metadata:

`get_user_meta( $user->ID, $field, $single )

Currently we use $single = true, which means we only read one value. We will change the plugin so it uses $single = false, the function will then return an array, and we will loop through the array and store the multiple values.

Also we will take care that a value like a:1:{i:0;s:17:”access_to_justice”;} will be stored as text, so at least it does not generate an error.

However, this probably does not solve your problem immediately, because get_user_meta( , , false) searches the database for multiple rows with the same user/field combination, and not as a serilized array as seems to be the case with ‘Advanced Custom Fields’.

So I suggest you upgrade our plugin once we are done, and then find a way to store the field in the native WordPress way. Maybe the authors of ‘Advanced Custom Fields’ can help you on this part of the problem.

Regards, Carlo

I am glad it works!

Good luck, Carlo

I can’t edit my own comments here, why is that?

“The same might be true for child themes, it is therefore recommended to use child themes.”

I mean: “You dont want to overwrite your changes by a theme update, it is therefore recommended to use child themes in combination with the ‘copy files to current theme’ button.”

about using p-lead buttons, be sure you also use p-normal instead of just p. p-normal will remove classes.

It would be great if people submitted their own button definitions. Note that the entire project is on github as free software. Just clone it and make your improvements. If I like them, I might take them on board.