Code Monkey home page Code Monkey logo

mc-magento2's Introduction

Labels applied by the team

Label Description
bug Bug report contains sufficient information to reproduce. Will be solved for associated Milestone.
enhancement Improvement accepted. Will be added for associated Milestone.
done Issue has been solved and will be applied in the associated Milestone.
duplicate Issue has been already reported and will be closed with no further action.
wrong issue format Issue has not been created according to requirements at the Issue reporting guidelines. Will be closed until requirements are met.
feature request Feature request to be considered by the team. After approval will be labeled as enhancement.
could not replicate The team was not able to replicate issue. It will be closed until missing information is given.
contact support Contact our support team at [email protected]. Issue will be closed with no further action.
low priority Issue is considered as low priority by the team.
priority Issue is considered as high priority by the team.
conflict Issue reports a conflict with other third party extension.
need feedback Feedback is required to continue working on the issue. If there is no answer after a week it will be closed.
blocked Issue can not be solved due to external causes.
read documentation Issue will be closed. Available documentation: MailChimp For Magento doc

Issue reporting guidelines

To maintain an effective bugfix workflow and make sure issues will be solved in a timely manner we kindly ask reporters to follow some simple guidelines.

Before creating an issue, please do the following:

  • Check the documentation to make sure the behavior you are reporting is really a bug, not a feature.
  • Check the existing issues to make sure you are not duplicating somebody’s work.
  • Make sure, that information you are about to report is a technical issue, please refer to the Community Forums for technical questions.

If you are sure that the problem you are experiencing is caused by a bug, file a new issue in a Github issue tracker following the recommendations below.

Title

Title is a vital part of bug report for developer and triager to quickly identify a unique issue. A well written title should contain a clear, brief explanation of the issue, making emphasis on the most important points.

Good example would be:

Unable to place order with Virtual product and PayPal.

Unclear example:

Can't checkout.

Issue Description

Preconditions

Describing preconditions is a great start, provide information on system configuration settings you have changed, detailed information on entities created (Products, Customers, etc), Magento and mc-magento versions. Basically, everything that would help developer set up the same environment as you have.

Example:

1. Magento CE 2.0.1 without sample data is installed.
2. mc-magento 1.0.6.
3. Test category is set up.
4. Virtual Product is created and assigned to the Test Category.
...

Steps to reproduce

This part of the bug report is the most important, as developer will use this information to reproduce the issue. Problem is more likely to be fixed if it can be reproduced.

Precisely describe each step you have taken to reproduce the issue. Try to include as much information as possible, sometimes even minor differences can be crucial.

Example:

1. Navigate to storefront as a guest.
2. Open Test Category.
3. Click "Add to Cart" on the Virtual Product.
4. Open mini shopping cart and click "Proceed to Checkout".
...

Actual and Expected result

To make sure that everybody involved in the fix are on the same page, precisely describe the result you expected to get and the result you actually observed after performing the steps.

Example:

Expected result:
Order is placed successfully, customer is redirected to the success page.
Actual result:
"Place order" button is not visible, order cannot be placed.

Additional information

Additional information is often requested when the bug report is processed, you can save time by providing Magento and browser logs, screenshots, any other artifacts related to the issue at your own judgement.

Pull requests

Before creating a pull request please make sure to follow this guidelines or it will be rejected.

mc-magento2's People

Contributors

agustinbv avatar alexalisov avatar andrey-legayev avatar arendarenko avatar blackikeeagle avatar brian-ebizmarts avatar centerax avatar ebizmarts-keller avatar federicocanedo avatar gonzaloebiz avatar gundamkid avatar ihor-sviziev avatar jhruehl avatar luciaebizmarts avatar maximbaibakov avatar mpchadwick avatar roberto-ebizmarts avatar robertsp86 avatar santiagoebizmarts avatar t-richards avatar thespacersm avatar tristanhofman avatar valguss avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mc-magento2's Issues

Purchases made via campaign not attributed to the campaign

Purchases made via clickthrough a campaign are not correctly attributed.

To repro:

  1. connect M2 to MC
  2. create a campaign that includes a product link, send
  3. clear cache/cookies/go incognito
  4. open product email, click through (note url includes tracking: mc_cid=6091822d5b&mc_eid=1adac90a9b)
  5. add to cart
  6. navigate to another part of the store, add another item
  7. complete purchase
  8. note that Order appears in MC, but is not associated with a campaign: https://cl.ly/2B1D3c0r3W3L

Swap lines in Configuration page

Currently, we list total subscribers(in the MC account) under Data Uploaded, I'd recommend moving it as that might be misleading.

Currently:
Account Details
Username: DinoPets
Data uploaded to MailChimp:
Total Subscribers: 7798
Total Customers: 0
Total Products: 2042
Total Orders: 0
Total Carts: 0

Change to:
Account Details
Username: DinoPets
Total Subscribers: 7798
Data uploaded to MailChimp:
Total Customers: 0
Total Products: 2042
Total Orders: 0
Total Carts: 0

Request: Display Sync status

Generally, it is not clear if a APIkey and store are actually connected, which leads to a lot of confusion.
https://cl.ly/2Q3t2m0r1W11

Sync states and messaging:
API key selected, no associated MailChimp stores

  • current: https://cl.ly/1t2Y1w2U0o1N
  • add in Account Details - "This MailChimp account is not connected to Magento."
  • Change MailChimp Store dropdown text to "You must create a MailChimp Store for this API key to connect to this account".
  • add, if possible, a link to the MailChimp Stores section next to the MailChimp Store dropdown.

API key selected, MailChimp stores been selected and but not saved

API key selected, MailChimp stores been selected and saved

API key selected, MailChimp stores been selected and saved, sync is complete

List MC account and List

On the MailChimp Stores page currently(v1.0.9): https://cl.ly/1y0w0p0j153k
It would be more helpful if we displayed MC account and List name in this grid.

It would be helpful if we can list it on the specific store page also, since the API key and list selection dropdown dispapear after the store is first created.

Support guest abandoned carts.

M2 doesn't save abandoned carts for guest checkouts, we'd need to do a workaround to get these to pass to MailChimp.

This is an M2 issue, if they don't fix it we'll need a plugin workaround down the line.

Add webhooks

Add webhooks for the list associated to the mailchimp store defined in the config.
Be sure to delete the webhook if none of the magento stores in this installation is linked to this list

Store information not passing to MailChimp

Store passed to MC:

"id": "104.131.96.113_...",
"list_id": "....",
"name": "104.131.96.113_....",
"platform": "Magento",
"domain": "",
"is_syncing": false,
"email_address": "",
"currency_code": "USD",
"money_format": "",
"primary_locale": "",
"timezone": "",
"phone": "",
"address": {
"address1": "",
"address2": "",
"city": "",
"province": "",
"province_code": "",
"postal_code": "",
"country": "",
"country_code": "",
"longitude": 0,
"latitude": 0}

Store info in M2:

https://cl.ly/1V0W1e1d1q0e

Passing store info(address, email, etc) allows MC to populate list and footer with store info. note: this appears to also be missing for M1.

Enable not saving on a MailChimp store level

Unsure if this is related to having multiple store, or recent changes to configuration.

steps to reproduce
1.add APi key to Configuration
2. create a new store, add all necessary details, enable = yes and save.
3. add a second API key on the Configuration page
4. add a second MailChimp store connected to the second API key
5. on the MailChimp stores page, edit each of the stores and not that they're both enabled = No
6. switch them to enabled = yes and save
7. note that enabling doesn't persist.

Error with default config allows unassociated list to be attached to a store config.

In MailChimp for Magento 2, a MailChimp store must be created before it can be selected for use in a store configuration. However, if default configuration is selected for list but not store when setting up a second store, this will return the following error:

Something went wrong while saving this configuration: Notice: Undefined index: value in /var/www/html/magento/vendor/mailchimp/mc-magento2/Model/Config/Backend/MonkeyStore.php on line 85

We should either clarify the error or remove the option of selecting a list within the MailChimp configuration and only allow list selection in the store creation step.

Use a checkbox on Checkout to determine Opt-in status.

Add a Subscribe checkbox to the Checkout process, use that to determine opt-in status.

If the user opts in via checkbox, they should be passed to MailChimp as subscribed.
If the user does not opt in via checkbox, they should be passed to MailChimp as nonsubscribed.
If the user had previously subscribed and does not check the box on a later purchase, the user should remain subscribed.
If the user creates a cart without a checkout, they should be passed to MailChimp as nonsubscribed.

Inital sync: without checkbox data for previous orders, Customers should be passed to MailChimp as subscribed. Email addresses associated with orders who are not Customers should be passed to MailChimp as nonsubscribed.

Review the Customer process

A Magento customer that is not subscribed to magento newsletter, must pass to mailchimp as transactional.
And a Magento customer subcribed must pass to mailchimp as subscribed

Avoid error when for some reason the process cancel

When the process runs, new registers are added to the table of syscommerce, but in some situations the process can cancel and the batch is neves synced, the register added in that table means that this registers are already processed.

Account no longer syncing

Case: Added a second store today, now it looks like it's no longer syncing at all.

First store+list, which showed POST and GET activity yesterday, shows nothing for today, and no data from orders placed today has been synced.

Problem when receive the response of batch

Sometimes when receive the response of a batch, one the process cancel and response files stay in the var/Mailchimp directory and the next runs already fails
Warning: mkdir(): File exists in /var/www/html/magento/vendor/mailchimp/mc-magento2/Model/Api/Result.php on line 103
Error with a response: Warning: rmdir(/var/www/html/magento/var/Mailchimp/f605959ae8): Directory not empty in /var/www/html/magento/vendor/mailchimp/mc-magento2/Model/Api/Result.php on line 76

Add actions to webhooks

When a webhook is called, save the content of the call in a table, and process it with a cron job

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.