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.
The following drush commands need to be ported to Drupal 8:
- cron-logs
- cron-list
- cron-job-get
- cron-job-set
- cron-run
- cron-enable
- cron-disable
- cron-unlock
Comment | File | Size | Author |
---|---|---|---|
#16 | port_drush_commands_to-2665728-15-interdiff.txt | 2.84 KB | Berdir |
#16 | port_drush_commands_to-2665728-15.patch | 16.58 KB | Berdir |
#11 | interdiff.txt | 7.08 KB | dermario |
#11 | port_drush_commands_to-2665728-11.patch | 16.13 KB | dermario |
| |||
#8 | port_drush_commands_to-d8-2665728-8.patch | 13.62 KB | dermario |
|
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedbugsonly created an issue. See original summary.
Comment #2
BerdirThe drush commands are not ported yet.
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #4
BerdirPostponed usually means that it's postponed on *something*. For example another issue needs to be fixed first.
That's not the case. It just requires someone to spend time on this and actually do it.
Comment #5
dermarioComment #6
dermarioComment #7
dermarioI wonder if it makes sense to have 1 (child) issue per command or if its better to handle it all in this here?
Comment #8
dermarioHere is a patch for a drush integration with D8. With this patch i got the following commands running:
This patch is not ready yet - there are some open questions i need to get answered somehow.
Comment #9
dermarioComment #10
BerdirLooks good.
You can remove this completely IMHO. The standard cron command works fine, we no longer need to replace it.
while we touch this anyway, lets rename to $modules.
Is the force option really useful? If not, then we could just drop that and just call out to the cron service in this case. Not sure..
Comment #11
dermarioI applied all changes proposed in #10. Beside this i made some bigger changes. They are more or less a starting point for a discussion.
Comment #12
g18724 CreditAttribution: g18724 commentedIs this latest patch/update already "in"
I've installed that but don't see the 'drush crun' cmd.
Do I need to patch? wait?
Comment #13
ahillio CreditAttribution: ahillio commentedI think you should apply the patch, as https://www.drupal.org/node/1247158/commits doesn't list anything regarding drush commands. Typically when an issue's status is "Needs review" the patches have not yet been committed.
Comment #14
g18724 CreditAttribution: g18724 commented> the patches have not yet been committed
Thanks. Was unclear to me with "I applied all changes proposed ..." & "3 months ago".
Comment #16
BerdirSorry for letting this lie around so long. Finally got to testing this. Made a few small additions/fixes and committed.
* Added the ID to the list. That's important for the other commands, so it should be thee.
* Fixed cron-run
* Some Cronjob => CronJob replacements
Comment #17
g18724 CreditAttribution: g18724 commentedInstalled
checked
list available cron jubs
exec
Comment #18
g18724 CreditAttribution: g18724 commentedComment #19
BerdirAs you can see in the backtrace, that's an exception thrown by search_api that is apparently broken. Has nothing to do with this issue, it just triggers it.
Comment #20
g18724 CreditAttribution: g18724 commented-->
exception thrown by search_api, invoked in drush cron-run