- Issue created by @championlife
- π¦πΊAustralia championlife
Instead of enabling via drush, I did a cache clear first.
I tried again by pulling down my database from Pantheon and starting anew.
Instead of enabling via drush, I did a cache clear first, then enabled from the UI.I now get "S3fs require AWS library" when clicking the Install button.
- Status changed to Postponed: needs info
about 1 year ago 6:00am 17 May 2023 - πΊπΈUnited States cmlara
I snuggest reviewing the previously opened support request #3279546: Error: Class 'Aws\S3\StreamWrapper' not found in include() (line 24 of modules\composer\s3fs\src\StreamWrapper\S3fsStream.php). β .
Please advise if the steps there resolve your issue.
- Status changed to Active
about 1 year ago 6:04am 17 May 2023 - π¦πΊAustralia championlife
I have reviewed that ticket before, but unfortunately not.
Runningcomposer show aws/aws-sdk-php
shows that the SDK exists
composer dump-autoload
does not fix anything. - πΊπΈUnited States cmlara
Unfortunately this is almost certainly going to be an issue outside of the S3FS module.
- An AutoLoader fault is still most likely in my experience. I will mention that the AutoLoader may be cached in OpCache and require restarting services (apache/FPM/nginx/etc) to fully clear. Purging the vendor directory and reinstalling is sometimes a solution. Ultimately the best source for this portion would be Compsoser based support forms. Its also possible for the Drupal Core autoloader to interfere.
- Related to the Autolaoder fault is a local deployment fault of some kind (file permission issues or similar.)
- Last candidate is the AWS SDK, you can try an older version though I don't expect that to be the cause.
- π¦πΊAustralia championlife
Thanks cmlara. I'll take a look at all that. That's super helpful debugging tips.
I'm running a local lando install from a Pantheon site. - Status changed to Fixed
about 1 year ago 5:58pm 15 June 2023 - πΊπΈUnited States cmlara
With no further updates in 4 weeks Iβm going to assume this was able to be solved outside of the s3fs module as noted in previous comments.
If this issue still persists and can be confirmed to be an issue inside of s3fs please feel free to re-open the issue.
Automatically closed - issue fixed for 2 weeks with no activity.