medusa
medusa copied to clipboard
Error 404 with Mailchimp subscribe
Bug report
Describe the bug
I can't get the Mailchimp subscription to work. I get 404 error
System information
Medusa version (including plugins): 1.19.0 Mailchimp: 1.1.50 Node.js version: Database: Operating system: Browser (if relevant):
Steps to reproduce the behavior
I get error 404 when I subscribe a new email
Screenshots
My form
Additional context
I followed the guide from the docs.
Are you sure the plugin is loaded correctly? Do you have any logs on your server when starting?
can you share your plugin section of the medusa config
Are you sure the plugin is loaded correctly? Do you have any logs on your server when starting?
I dont have any log about Mailchimp
When I test the route /mailchimp/subscribe I dont receive any
looks like the version 1.1.5 does not include the build output.
cc @olivermrbl we should re publish the plugin including the output files
@lfdadev I suggest you to downgrade until the new version is released
@lfdadev I suggest you to downgrade until the new version is released
Which version can I use?
I would say 1.1.49
I would say 1.1.49
Ok, I will try
keep me posted 👍
I would say 1.1.49
Tested with that version and it worked perfect! Thanks!!!
It worked locally, but not in production. I got Cors error
The plugin router is configured to use the store_cors
const corsOptions = {
origin: parseCorsOrigins(config.projectConfig.store_cors || ""),
credentials: true,
}
app.use("/mailchimp", router)
router.use(cors(corsOptions))
Are you sure it is properly configured?
The plugin router is configured to use the store_cors
const corsOptions = { origin: parseCorsOrigins(config.projectConfig.store_cors || ""), credentials: true, } app.use("/mailchimp", router) router.use(cors(corsOptions))
Are you sure it is properly configured?
I did it on this way. Locally working perfect. I didnt change nothing
Mi package
@adrien2p A mate on the discord told me to try his version and it worked. "medusa-plugin-mailchimp-wine": "^1.1.56" My cors error got fixed. If you wanna compare
something about this? it throws CORS error for me too in production with the version 1.1.49. In development works fine. And only the POST route, the PUT route doesn't work.
Hey, thanks for the report! Since v2 brought a lot of architectural and API changes on the backend, we will be closing this ticket since it no longer applies to our new setup, or the issue has already been fixed. If you are still facing issues with v1, please open a new ticket and we will address it as soon as possible. Thanks! 🙏