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.
libraries.module on line 83
libraries.module on line 136
I'm not familiar enough with the new D8 code to determine if these can safely be commented out for now or not.
Comment | File | Size | Author |
---|---|---|---|
#2 | libraries-conf_path-2579283-2.patch | 1.03 KB | Berdir |
|
Comments
Comment #2
BerdirComment #3
r0nn1ef CreditAttribution: r0nn1ef commentedI have applied the patch in #2 and no longer receive the previous errors. Thanks for the quick turn around on this!
Comment #4
rjacobs CreditAttribution: rjacobs commentedThe patch seems consistent with #2384675: Deprecate conf_path() and the relevant change record.
Just curious, will getting the request via
\Drupal::request()
cause any problems if library detection needs to happen via a non-http request? I suppose that the logic in question (libraries_get_libraries()
andlibraries_scan_info_files()
) only make sense to use during a normal Drupal page request, but I just wanted to confirm that I understand the request management details correctly for this scope.Comment #5
tstoecklerLooks good to me. @rjacobs do you want to pull the trigger? ;-)
Comment #7
rjacobs CreditAttribution: rjacobs commentedSounds good to me. Committed.
I also removed that tag that I think only really applies to core queues.
Comment #9
tstoeckler