Closed (fixed)
Project:
Mailchimp
Version:
7.x-2.x-dev
Component:
General
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Jan 2013 at 00:21 UTC
Updated:
17 Jul 2013 at 05:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
gcbErin, have you checked the permissions on that folder? Some others have had issues because of permissions:
http://drupal.org/node/1883984#comment-6976100
Also, we just rolled out 7.x-2.10 which fixes some other issues: I recommend updating immediately. 2.10 won't resolve this issue for you, though: follow that link.
Comment #2
erin814 commentedThanks, I changed the permissions on the libraries and mailchimp folders to 777 but still no luck. Also upgraded to Mailchimp7.x-2.10. My site is somewhat complicated with a lot of modules so it could just be an issue unique to my site since no one else is reporting it. I'll keep plugging away at it and post if I find a solution.
Thank you,
Erin
Comment #3
relish27 commentedI also am having the same problem.
Comment #4
relish27 commentedActually, I followed this -- http://drupal.org/node/1883984#comment-7002038 -- and got it to work.
Comment #5
gcb#1883984: Fix for "Can't get module to recognize library"
Comment #6
ericamp commentedI had the same problem. It disappeared when I added README file to libraries/mailchimp/ directory (it is required)
Comment #7
wiifmI am going to re-open this issue, and remove the duplicate tag.
My problem is that we utilise
.gitattributesin order to remove certain files from our git repo from making it to staging or production. One global file pattern we use isREADME(along with many others). The reason being is we do not want to serve essentially useless text files to the general public, not only is this bad practice, it can be a security hole as it advertises the versions of modules and libraries you are running.Attached is a patch the removes the dependency on the MailChimp API README file, keeping it solely for it's intended purpose - i.e. reading about the API. The version of the API is also defined in the the PHP class, and is trivial to parse out.
I suggest we use this file to define the version.
Does anyone else have thoughts on this?
Comment #8
wiifmUpdating the title to reflect the new scope of the issue.
Comment #9
gcbThanks wiifm, that's a great patch. It's been rolled into the latest Dev and will be in a stable release very very soon.
Comment #10
wiifmMany thanks @gcb!