- Issue created by @debrajn
- Status changed to Postponed: needs info
over 1 year ago 4:29pm 13 October 2023 - 🇺🇸United States cmlara
Reducing priority as Support Requests on D.O. are never critical unless other arrangements have been made with the project.
3. When I go to admin/config/media/s3fs form manually and save ...
Now all the s3 functionality is working fine... But in our old release use have used s3fs version: '8.x-3.0-alpha17' where do not need to save...This sounds like you may not actually have all the settings in your settings.php, there is both settings.php only items, and configuration which can (but isn't recommended) to be in settings.php or can be in configuration files.
This could be that the site have not run the database update tasks after upgrading It is also possible that a config field that is required was not migrated during Alpha, though I believe I did try and maintain backwards compatibility as s3fs had been in alpha for an extended period of time.
I suggest researching Configuration Management → as one solution for managing site config instead of settings.php, doing so might also help you determine what configuration is missing that should be apart of your rollout process.
- 🇮🇳India debrajn
Thank you cmlara,
Your help is really appreciated. I got the issue and fixed. It was the configuration issue. Now sites are working fine.
- Status changed to Fixed
over 1 year ago 8:09am 16 October 2023 Automatically closed - issue fixed for 2 weeks with no activity.