Closed (works as designed)
Project:
Scheduler
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Jul 2019 at 10:52 UTC
Updated:
29 Nov 2019 at 16:59 UTC
Jump to comment: Most recent
Comments
Comment #2
kallado commentedComment #3
jonathan1055 commentedHi Kallado,
Thanks for mentioning this. However it has already been fixed. The lines in 8.x-1.0 are
But these lines have already been deleted in -dev. Please can you confirm that you are using 8.x-1.0 when this error happened.
Jonathan
Comment #4
jonathan1055 commentedHere is the other issye #3038746: Remove deprecated EntityDefinitionUpdateManagerInterface::applyUpdates() from hook_install and hook_uninstall
Comment #5
kallado commented@jonathan1055 Ok I was using 8.x-1.0 version (that composer installed by default) my mistake. Guess the problem is solved already. Thanks for the reply you can mark this as fixed if you want.
Comment #6
jonathan1055 commentedHi kallado,
You did not make any mistake. Version 1.0 does have the fault and it is perfectly acceptable to only run full release versions not -dev code.
Scheduler 8.x-1.1 is going to be released soon. You can check the progress on
#3030243: Plan for Scheduler 8.x-1.1 release
Comment #7
jonathan1055 commentedComment #8
jonathan1055 commentedComment #9
kristen polPer a Slack discussion with Gábor Hojtsy regarding usage of D9 tags (Drupal 9, Drupal 9 compatibility, Drupal 9 readiness, etc.), "Drupal 9 compatibility" should be used for contributed projects that need updating and "Drupal 9" was the old tag for D8 issues before the D9 branch was ready. Doing tag cleanup here based on that discussion.
Comment #10
jonathan1055 commentedThis issue is already closed 'works as designed'. There was no fix.
Why did not not read the status and leave it alone. Or maybe these comments were automated, as I have seen dozen's of them in the last two days.
Comment #11
kristen polThese updates weren't automated. I spent many hours yesterday going through many issues to find ones that had deprecated errors in them. It's useful tagging closed/fixed issues with the tag because then we know the issues were addressed. We're trying to get people contributing to these issues so seeing both open and closed issues with the tag is helpful. It gives us data on progress as well. I won't re-tag this because you don't agree with that and you're maintaining the module.
Comment #12
jonathan1055 commentedWow, I appreciate your effort in doing this. Yes, I am fine with tagging the closed issues when they actually had a deprecation fix. But this one was a duplicate, which had no commit. The real issue was #3038746: Remove deprecated EntityDefinitionUpdateManagerInterface::applyUpdates() from hook_install and hook_uninstall so I have tagged that one instead.
Thanks for your efforts, sorry if I appeared to grumble :-)
Comment #13
kristen polThanks! I definitely don't want to add noise but glad you found an issue to tag. I gathered some stats for a blog post that I hope to get out in a couple days so this is helpful. There's been a lot of work going on to get modules ready for D9 which is good news. Thanks for your help.