createProxyHeadersArray(): Argument #1 ($headers_string) must be of type string

@naidim, I have fixed the issue and created MR. please review it once.

Some research needs to be done. But just an empty check doesn’t count as it could be masking a larger issue

Not able to reproduce could additional info be provided?

@abhishek_gupta1 to receive credit need to be able to reproduce and show it's an issue.

FWIW I hit this problem after updating from 2.1 to 3.0@alpha. As far as I can see the stage_file_proxy_update_8003() did not get to add the proxy_headers into the config. However I have not reproduced this in isolation, I am updating code from 10.1 to 10.3 and hitting numerous issues.

Update on my previous post: in my case, although I was not seeing any output from Drush that the 8003 update hook has run, it appears to be doing so. The cause of the code error is more likely that my site has a copy of the stage_file_proxy.yml in config/development, the contents of which override anything else in a development context. Ensuring the additional settings are in that copy of the file eliminated my problem.

I can confirm that this issue exists and is blocking updating to 3.1.0 (2024-Jul-21).
This is troublesome because my "Available Updates" reports in relation to my currently
installed version of Stage File Proxy 2.1.4:
Release not supported: Your currently installed release is now unsupported, and is no longer available for download. Uninstalling everything included in this release or upgrading is strongly recommended!
This implies I must update but I'm blocked because of this issue.

Followup question is the proposed fix I see here (see url below) considered a suitable patch
or is work going on to do a more complete fix?
https://git.drupalcode.org/project/stage_file_proxy/-/merge_requests/74/...

Thank you, @sp3boy

We're using config_split and while everything looked good on our 'devel' environments, I ran into this error on our 'staging' environment.

proxy_headers: '' had made it into our config/devel/stage_file_proxy.settings.yml file, but not into our config/staging/stage_file_proxy.settings.yml file. Adding it fixed the problem!

We ran into the same error in our 'local' config split and when I applied the same fix
that @sp3boy used it works. I do think that *either* the fix in #1 should be added and/or
the hook fixed so it updates the appropriate stage_file_proxy.settings.yml files in
config splits. If this cannot be fixed soon, I urge that the previous version of this
module Stage File Proxy 2.1.4 be modified to stop reporting this following way:
"Release not supported: Your currently installed release is now unsupported, and is no longer available for download. Uninstalling everything included in this release or upgrading is strongly recommended!"
At least until this issue is fixed.

Same issue as will_frank, we were missing proxy_headers and excluded_extensions from our settings file.

Faced with same issue after updating stage_file_proxy to v3.1.
Using config_split. Thanks to all comments issue was fixed with adding proxy_headers: '' to all
config/*/stage_file_proxy.settings.yml

Just wanted to add a 'me too' on stage_file_proxy 3.0.0-alpha2. Adding proxy_headers: '' to the config in the relevant config split folder fixed the issue for me

Had the same.

I would say lets close the MR and issue with status Closed: works as designed.

smustgrave → closed merge request !74