Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
The "i18n page views" module has as the git repo name and the project machinename on d.org is i18_page_views.
The worst part of this typo is that the module has a lot of uses, has been covered on the Drupal 7 i18n book, and could have other references in the full www.
Would be possible to just create a i18n_page_views module and make a redirect from i18_page_views on d.org?
How that would mess with the update system? What is the best solution?
Project URL: http://drupal.org/project/i18_page_views
Issue: #1401062: path for download is different than to install
Comments
Comment #1
dddave CreditAttribution: dddave commentedComment #2
dddave CreditAttribution: dddave commentedComment #3
dddave CreditAttribution: dddave commentedNot sure if this is the right place...
Comment #4
drummi18_page_views can be moved, even including the Git repository if wanted. However, www.drupal.org is the only place we can do redirects at this time. The old update status files would remain for the foreseeable future, so update status would be the same. If the Git repository is moved, every clone would get confused by having a nonexistent remote.
We can either:
A) Keep the name as-is and redirect i18n_page_views to i18_page_views. Everything remains the same and the urls from the book work.
B) Make a fresh project and keep both. The old project page will explain the move. Users can switch projects whenever they notice the change and feel motivated to move.
C) Move the project, and redirect the old URL. Users are more likely to notice faster.
Comment #5
erwangel CreditAttribution: erwangel commentedAny news on this ? With the new core warnings on missing modules it becomes painful to install the module until finding this page. Things go round and round after a drush en with repeating messages
For those coming here, this is the way I gone: drush dl i18_page_views then drush en i18n_page_views
Comment #6
drummI no longer recommend this, I'm not sure why I suggested it.
I recommend this. Once the new project is there, the old project can be marked as unsupported so update status alerts people with it installed that something changed.