Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I am using Custom Publishing Options version 7.x-1.4 on several websites:
A nasty red box just appeared in my "Available updates" report:
Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!
Seriously? There has been no prior announcements bout EOL for the Drupal 7 branch and Drupal 7 itself is maintained until 2022. Nor is there any notice on the project page about EOL for the Drupal 7 branch.
I am not ready to migrate the websites hit by this to Drupal 8/9.
Hopefully, you just unticked the box about the Drupal 7 being supported in error, please tick it again.
If you unticked it because there is nobody around to maintain the Drupal 7, please consider this an offer to step up and co-maintain the Drupal 7 branch until Drupal 7 itself reaches EOL.
Comments
Comment #2
jelle_s+1, sharing the same concerns as the issue creator.
Comment #3
jacobbell84 commentedApologies, I'm still getting the hang of maintaining projects. I unchecked it to indicate that there's nobody currently active on the project to support it, but I forgot about the red messages that would broadcast. VladimirAus and myself only became co-maintainers a few weeks ago, but we're only maintaining the D8/9 branch, so the status seemed accurate since the D7 issue queue hasn't been touched in years and the module itself hasn't received updates in 4 years.
Thank you for the offer on helping to maintain it! I'll get you added to the project in a few.
Comment #4
jacobbell84 commentedActually, looks like I don't have permissions to add other maintainers. I've set the 7.x build as re-supported in the mean time to get rid of the red alert box, but I'd reach out to the project owner kevinquillen and request to help maintain it. He's the one that added me and VladimirAus so he's still around.
Comment #5
gisleThanks for fixing it so quickly!
And yes, Kevin Quillen and Adam Gregory (the owner) are the only ones that can add additional maintainers.
Just a note on maintainer best practices:
If there is nobody currently around to support the Drupal 7 branch, a gentler approach is to put a notice about it on the project page to disclose that, and perhaps also change the "Maintenance status" to: "Seeking co-maintainers"? If you're happy with your Drupal 8/9 team and don't want a third party to interfere with that branch, just say to any co-maintainer that is added that he/she is only expected to touch the Drupal 7 branch. In my experience, seasoned community members will observe such as restriction.
The Drupal 7 branch is pretty mature and is IMHO in pretty good shape. It will probably not require much work to maintain it. But if you want my help, I happy to offer it.
Most of this issue has been resolved. Leaving it open to await decision on co-maintainer offer.
Comment #6
jacobbell84 commentedThank you @gisle, I was actually wondering what a better way would have been to handle it :) I like that approach, I'll keep that in mind for future projects.
Comment #7
gisleTo get an overview over what maintainers can do, edit the project page URL and append "maintainers.json".
https://www.drupal.org/project/custom_pub/maintainers.json
Comment #8
kevinquillen commentedSorry - catching up. What is happening here and what needs to happen?
Comment #9
gisleWhat happened?
D7 release got unpublished and then was republished.
What needs to happen?
According to jacobbell84, nobody is around to maintain the D7 branch. I still use that branch, so I offered to maintain it. You are the owner, if you accept the offer, please add me as maintainer.
Comment #10
kevinquillen commentedDone.
Comment #11
gisleMoving ti fixed.