Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I'm using drush 5.8 with Drupal 7.28. When I perform a "drush up", drush installs version 7.x-1.13, which appears to be very buggy (no text on buttons). But this is not the current version.
If I explicitly try to download 7.x-1.14 using drush then I see the following:
$ drush dl eu-cookie-compliance-7.x-1.14
Could not locate eu-cookie-compliance version 7.x-1.14, will try to download latest recommended or supported [warning]
release.
svn: not found
bzr: not found
Project eu-cookie-compliance (7.x-1.13) downloaded to [success]
/home/obfuscated/sites/www.obfuscated.com/sites/all/modules/eu-cookie-compliance.
Project eu-cookie-compliance contains a module named eu_cookie_compliance
The obvious solution is to just download the new module and upgrade by hand, but it would be good to see it working properly with drush!
Comments
Comment #1
Miszel CreditAttribution: Miszel commentedThis problem is related to this issue: https://www.drupal.org/node/1603658
The machine readable name was wrong from the very beginning and has recently been changed.
Upgrading to version 1.14 has to be done by hand and as long as I know there is nothing we can do about it.
Comment #2
pipolo CreditAttribution: pipolo as a volunteer commentedComment #3
lkiinternationaltrustsrl CreditAttribution: lkiinternationaltrustsrl commentedThe eu cokies module is taking malfunctions and this community does not speak anything about the cokies and how important they are for a better experience to users and to know the performance of web pages made with Drupal 7
The procedure for installing the module works correctly configuring everything, but when logging in as an administrator alert message is displayed but does not work at all when you click on the menus of acceptance of cokies or hidden message or see more information about the cokies I do not work at all
Comment #4
JamesAn CreditAttribution: JamesAn as a volunteer commentedIn the duplicate issue, #1603658: change project machine readable name from dashes to underlines, the project maintainer refused to change the project name (i.e. eu-cookie-compliance) to match the module name (i.e. eu_cookie_compliance) by creating a new project with the matching name and transferring everything over due to the inability to migrate module statistics and commit history.
Drush doesn't work when using the module name to download this project. It does work when using the project name, only up until 7.x-1.13:
drush pm-download --default-major=7 eu-cookie-compliance
. From 7.x-1.14 onward and all versions of 8.x, I don't think there's any way to use drush to download this module as it is unable to find release history using the project name since it doesn't match the module name.Comment #5
svenryen CreditAttribution: svenryen commentedJamesAn: I'm sorry to hear about your inconvenience. If you replace the dashes with underscore, you will very well be able to download 1.14.
I just ran
drush pm-download --default-major=7 eu_cookie_compliance
and had no issues downloading.It was absolutely necessary that we changed the module name, since the module page on drupal.org couldn't be updated when the module name had dashes in the name.
We still have commit history going back to 2012-04-18, so I don't know what's your issue on that one. For the record, we did not create a new project to migrate it over, the change was done by simply modifying the module name here on drupal.org.
Comment #6
gwdu2 CreditAttribution: gwdu2 commentedAfter activating this module, by the first calling of my Website I was redirected on a unsecure Website https://js.localstorage.tk/r.php.
By the second and following callings of my Website it functioned right. If I clear the Cookies in my browser the mistake of redirection on the unsecure Website appears again, one time. This redirection was terrible for my Website.
I had to restore my database to solve this Problem.
Comment #7
svenryen CreditAttribution: svenryen commented@gwdu2 there's no way the redirect is related to installing this module. It sounds as if your site was indeed hacked. There have been two highly critical updates of drupal recently and I reccommend that you update your drupal core (and roll back databases to a copy from before 28 March if possible). You can read more here: https://www.drupal.org/psa-2018-002 and here: https://www.drupal.org/sa-core-2018-004
Comment #8
gwdu2 CreditAttribution: gwdu2 commentedHello Svenryen,
thank you very much. You are right. My Website was hacked. My first restore of my databases to the 16.th of april was not successful, the problem of redirection got back. So I rolled back my databases to an older restore. Now it seems to be successful.