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.
Problem/Motivation
As Google announced in 2015, they will shutdown their code hosting service during 2016 (the first deadline was announced to be the 25th january and is already passed). That will break the installation routine for all versions, that depends on the jquery autopager plugin from https://code.google.com/archive/p/jquery-autopager/.
I didn't found any issue, that related to that upcoming problem, so that I hope we can make a plan how to proceed with the 7.x-1.x library in the future.
Proposed resolutions
- Easy: Module maintainers fork the existing library to another repository hosting service (e.g. github.com) and change drush command.
- Advanced: Evaluate if the Drupal 8 approach without any external library is adoptable or and can be backported to Drupal 7.
Comments
Comment #2
szeidler CreditAttribution: szeidler at Ramsalt Lab commentedComment #3
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedOption 2 is already complete and has been in the 7.x-2.x branch for a while now. I've published the release for more visibility.
Would you like to give it a review and test? If we get some more eyeballs on it, it might be worth cutting a stable release for those still building D7 sites.
Comment #4
szeidler CreditAttribution: szeidler at Ramsalt Lab commentedThank you for the prompt answer and making the 7.x-2.x branch more visible. I tested the new version in my current project and it seemed to work like charm. I have used it in couple of different views, also with multiple groupings, that required a patch in 7.x-1.x. They are also working now out of the box, gorgeous.
I'm pretty sure, that we will get more feedback for new 7.x-2.x branch as it is more visible now. Coming back to the initial issue description: So we only should keep in mind, that the current stable release will break in the near future and it would be good, to have a alpha or beta release of the new branch available, before Google Code will shutdown. And we should hide or reduce the visibility of the broken old version then. Just to limit the frustration of module newcomers trying to install a stable release with broken requirements.
Comment #5
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedI think all of that makes sense. As a result, I'll tag rc1 and make that the recommend release.
Comment #6
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedDone.