Did you remove the internal_data/code_cache directory?
That one needs to stay locally.
Did you remove the internal_data/code_cache directory?
'endpoint' => 'https://s3.eu-west-2.amazonaws.com'
'endpoint' => 'https://compatibleservice-endpont-url.com'
https://s3.amazonaws.com
is hardcoded somewhere?Fatal error: Uncaught Error: Class 'Aws\S3\S3Client' not found in /home/nginx/domains/mattwservices.co.uk/public/src/config.php:29 Stack trace: #0 [internal function]: XF\App->{closure}() #1 /home/nginx/domains/mattwservices.co.uk/public/src/XF/FsMounts.php(17): call_user_func(Object(Closure)) #2 /home/nginx/domains/mattwservices.co.uk/public/src/XF/App.php(858): XF\FsMounts::loadDefaultMounts(Array) #3 /home/nginx/domains/mattwservices.co.uk/public/src/XF/Container.php(28): XF\App->XF\{closure}(Object(XF\Container)) #4 /home/nginx/domains/mattwservices.co.uk/public/src/XF/App.php(2154): XF\Container->offsetGet('fs') #5 /home/nginx/domains/mattwservices.co.uk/public/src/XF.php(543): XF\App->fs() #6 /home/nginx/domains/mattwservices.co.uk/public/src/XF/Util/File.php(488): XF::fs() #7 /home/nginx/domains/mattwservices.co.uk/public/src/XF/Error.php(196): XF\Util\File::installLockExists() #8 /home/nginx/domains/mattwservices.co.uk/public/src/XF/App.php(1947): XF\Error->displayFatalExceptionMessage(Object(Error)) #9 /home/ngin in /home/nginx/domains/mattwservices.co.uk/public/src/config.php on line 29
Sorry Chris, updating to 2.0.11. It occus when going to theXF 2.0.11
install
folder. This update now includes two different add-ons. One is compatible with XF 2.0 and the other is compatible with XF 2.1.
The instructions have also been changed to avoid errors when accessing the install system in XF 2.0.
This change also introduces a slightly changed approach to avoid the repeated code when setting up the AWS SDK client.
The XF 2.1 version of the add-on also does not require the autoloader stuff to be applied as the add-on does that automatically. However, note that...
Hey there,
that’s an error in the underlying library. As the stack trace indicates, XPress hasn’t been called anywhere at that point. My assumption would be that it’s caused by the fact that the code is run outside the native XenForo directory, or similar. Not really anything we could do here I guess, as it’s not our code.
PHP message: PHP Fatal error: Uncaught TypeError: Argument 1 passed to Aws\Handler\GuzzleV6\GuzzleHandler::Aws\Handler\GuzzleV6{closure}() must be an instance of Exception, instance of TypeError given, called in /var/www/html/community/src/addons/XFAws/_vendor/guzzlehttp/promises/src/Promise.php on line 203 and defined in /var/www/html/community/src/addons/XFAws/_vendor/aws/aws-sdk-php/src/Handler/GuzzleV6/GuzzleHandler.php:45
Stack trace:
#0 /var/www/html/community/src/addons/XFAws/_vendor/guzzlehttp/promises/src/Promise.php(203): Aws\Handler\GuzzleV6\GuzzleHandler::Aws\Handler\GuzzleV6{closure}(Object(TypeError))
#1 /var/www/html/community/src/addons/XFAws/_vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promise\Promise::callHandler(2, Object(TypeError), Array)
#2 /var/www/html/community/src/addons/XFAws/_vendor/guzzlehttp/promises/src/TaskQueue.php(47): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise{closure}()
#3 /var/
Maybe I missed it, but where did you see in the instructions to make the bucket pubic? I didn't see anything mention that.Isnt't it a security issue to use the same, publically accessible bucket for both data and internal_data?
Maybe I missed it, but where did you see in the instructions to make the bucket pubic? I didn't see anything mention that.
Note: When copying your existing data files across, they will need to be made public. You can do this by setting the ACL to public while copying:
We use essential cookies to make this site work, and optional cookies to enhance your experience.