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.
Upgrading to Drupal 10 has begun, and a 8.x-1.x-dev release is available. Here is the current status of the port:
- base module - upgraded
- CL - upgraded (but does not include all the new features of 7.x-1.1.)
- LR - pending
- PET -pending
- test framework - partly upgraded
I am looking for a co-maintainer to oversee the D10 port and to implement the missing components. Please post a comment in this issue tracker if you want to work on the upgrade.
MRs and reviews are also welcome, and will be dealt with in a timely manner.
Comment | File | Size | Author |
---|---|---|---|
#4 | anonymous_publishing-dmu-analysis.pdf | 107.46 KB | juliencarnot |
Comments
Comment #2
gisleA Drupal 8 port is not currently on my schedule. That may change if someone is willing to sponsor a port to Drupal 8, but at the moment, all my client's sites are using Drupal 7.
However, if someone is willing to create a version for Drupal 8, please contact me to discuss co-maintainership with responsibility to oversee development for Drupal 8.
Please note that unless you have a CV that shows some experience with Drupal and ability to produce good quality code, I would like to see some code before assigning co-maintainership. The best way is probably to create a sandbox with an initial Drupal 8 version (i.e. not only a stub). I'll review the sandbox and if looks OK, I'll assign co-maintainership.
Postponing until either a sponsor or a qualified co-maintainer is found.
Comment #3
juliencarnot CreditAttribution: juliencarnot commentedSorry for this delayed follow-up and thanks a lot for your swift and complete answer! I understand your priorities and am afraid I don't have the skills/experience needed, and probably not the budget to sponsor it either... I'll keep learning meanwhile and will follow this issue!
Comment #4
juliencarnot CreditAttribution: juliencarnot commentedJust in case somebody with better coding skills than mine would be interested, here is the Drupal Upgrade Module analysis report on the last available release (7.x-1.0 2015-Mar-29). My dmu-upgrade attempt failed though.
Comment #5
juliencarnot CreditAttribution: juliencarnot commentedGisle,
My project is progressing and I find myself missing this feature to lower the threshold to contribution, especially the CL mode. Do you have a rough estimate of the budget and time needed for a Drupal 8 port, given your schedule for the coming months? I'd like to know if I could afford it or if I have to do without this feature, as apparently I seem to be the only user waiting for this at the moment.
Thanks again for your time!
Julien
Comment #6
gisle@juliencarnot
I did run it through the Drupal Module Upgrader (DMU) this morning.
It does not look good. DMU seems to have a lot of issues e.g. #2635944: InvalidArgumentException' with message '$string ("") (fixed in dev, but still trips up the stable version), and #2670932: FlagHookDeriver: NULL given when array was expected (crashes the latest dev). After patching those issues myself, the DMU did run and also produced some analytics, and I was even able to do a "dmu-upgrade". Unforuntately, the "dmu-upgrade" only addressed very basic stuff (such as varaibles), not heavier things such as API-changes. In other words: DMU isn't really much of a helper in its present unfinished state, and doing it "by hand" will require a lot of hours - at least if I am the person doing it.
I'll create a 8.1-1.x dev branch and push the result of the automatic "dmu-upgrade" later today - maybe it may inspire somebody else to have a go on finishing the upgrade.
I tried to look into those API-changes in order to produce a rough estimate of the budget and time needed. The D8 API is of course is documented on api.drupal.org, but it introduces a lot of new concepts (at least for me). This means that in order to convert Anonymous Publishing to Drupal 8, I first has to learn these new concepts.
With my present schedule, I don't even have the time to go back to school to learn Drupal 8. Also, I would of course not charge you (or any client) money for the required schooling - as a consultant, I need know my stuff before I start the taximeter.
I am sure that by now, there are a lot of developers familiar with Drupal 8 out there. If you can hire one of those to do the conversion, I'll assist in answering any questions he/she may have about Anonymous Publishing, and provide him/her with full access to the repo.
Comment #7
juliencarnot CreditAttribution: juliencarnot commented@Gisle:
Many thanks for your time and thorough explanations, and for starting this dev branch! I understand your point perfectly, I will investigate the options to find an experimented D8 developer and let you know ASAP!
Comment #8
gisleAdding related issues that currently impede on automatic upgrading in the Drupal module upgrader issue queue to keep a watch on them getting fixed.
Comment #9
gisleSetting version to 8.x-1.x.
Comment #10
juliencarnot CreditAttribution: juliencarnot commentedAs discussed with Gisle, I am hiring Dom. to port the Anonymous publishing parent module and the CL submodule only.
This partial port will be committed to the 8.x-dev branch but a full release won't be published until all the submodules are ported.
Comment #11
gisleGreat! Welcome onboard Dom.. I've added you as co-maintainer to the project. Feel free to contact me if there is anything you need.
Comment #12
Dom. CreditAttribution: Dom. at ACINO for oqp.io commentedHi @gisle, @juliencarnot and all,
I said previously, I will port Anonymous Publishing CL submodule for @juliencarnot (credit oqp.io).
@gisle: Do you have a preference for contribution ? Via patch or direct commit in branch. With or without a tracking issue (this one or a new one) ?
Comment #13
gisleYup!
Via direct commit in branch 8.x-1.x (you should already have access).
Also, I think you'll be better off cleaning out my botched attempt from that branch and start from scratch. I am pretty close to releasing 7.x-1.1, so I think you'll be better off working from the latest 7.x-1.x dev snapshot than from the almost one year old 7.x-1.0 release. Some bugs have been fixed and there are also automatic tests in place - which makes testing a lot easier.
Please use a tracking issue. I don't have any strong feelings about whether you use this one or a new one.
Comment #14
Dom. CreditAttribution: Dom. at ACINO for oqp.io commentedHi @gisle,
Thanks for letting me know about the new version, I used the GIT indeed.
I use : "Issue #2588475 by Dom.: ...." commit messages, but I will push them all at once when receiving payment from my client. It may happen that bot will report all individual commits in this issue then at the time ! Don't you mind ?
Comment #15
gisleJust go ahead whenever you've ready.
Comment #17
Dom. CreditAttribution: Dom. at ACINO for oqp.io commentedThe portage of Anonymous Publishing CL sub-module is now on the repo.
Comment #18
juliencarnot CreditAttribution: juliencarnot commentedThanks @Dom., just had time to install but not to test it yet, I will do that tomorrow and open separate issues if necessary (I just added one for now).
Comment #19
gisleThere is nothing to review. Setting back to Active.
Comment #20
Dom. CreditAttribution: Dom. at ACINO for oqp.io commentedIndeed, everything is on 8.x-1.x-dev branch. CL only is ported, not the other 2 sub-modules.
Have you had a chance at trying it ?
Comment #22
gisleDom. wrote:
Haven't made any extensive tests yet, but I discovered that visiting the "help" page made the site crash. Just pushed what I hope is a fix for that.
It also is a bit behind 7.x-1.x-dev as it does not implement the feature that lets the anonymous poster set a byline.
And of course there remains two sub-modules (LR and PET) to port.
Otherwise, it looks good.
Comment #24
gisleUpdated issue summary with current status of port.
Comment #25
gisleComment #26
gisleComment #27
gisleReverting to unassigned.
Comment #28
gisleChanged title to reflect that Drupal 8 is EOL.
Comment #29
gisleSetting status to "Active".
Comment #30
gisleChanged title to reflect that D9 is EOL.
We probably need to deal with deprecations before releasing a version for D10.
Comment #31
gisleUpdated for D10 and branch 2.0.x.