- 🇦🇺Australia kim.pepper 🏄♂️🇦🇺Sydney, Australia
I think this can be closed (outdated) as we have deprecated
system_retrieve_filein 📌 deprecate system_retrieve_file() without replacement Fixed
https://api.drupal.org/api/drupal/core!modules!system!system.module/func...
Currently the function system_retrieve_file generates a variety of Drupal error messages that cannot be suppressed or otherwise modified. This function should probably be modified to return the error to the calling function, allowing that function to determine what happens on an error instead of making an assumption on how errors should be handled.
With the way this is currently developed, it makes using this function for batch imports or other automated systems difficult without clearing all Drupal messages after executing the function. Furthermore, there is no easy way to programmatically determine why this function fails (ie, 404, 403).
Closed: outdated
9.5
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think this can be closed (outdated) as we have deprecated system_retrieve_file in
📌
deprecate system_retrieve_file() without replacement
Fixed