Try these settings, there isn't much documentation on these. My site runs on SSL and all the TinyMCE editors work. I'm running Mezzanine 3.14 + Cartridge.
*STATICFILES_STORAGE = 'storages.backends.s3boto.S3BotoStorage'* *AWS_QUERYSTRING_AUTH = False* *AWS_S3_SECURE_URLS = True* *AWS_S3_CUSTOM_DOMAIN = 's3.amazonaws.com/bucket_name'* *S3_URL = 'https://s3.amazonaws.com/bucket_name'* *MEDIA_URL = S3_URL* *STATIC_URL = S3_URL* On Friday, May 23, 2014 2:36:24 PM UTC-4, Brad Bode wrote: > > Although you are having a slightly different issue you might want to join > in on my discussion (with myself). It's a very similar problem. > > https://groups.google.com/d/msg/mezzanine-users/A7wEDWprYZY/gb-FBYxJjzQJ > > I am using AWS S3 with SSL for the admin. The only problem I have left is > getting the source editor to work. I might be able to advise you on your > issue as well. You may first want to read the replys here: > > https://groups.google.com/d/msg/mezzanine-users/r5DXu0dkCMU/3eH4wdczaZcJ > > It relates to getting S3 working with mezzanine. > > > On Tuesday, May 20, 2014 5:33:07 PM UTC-7, John Briere wrote: >> >> Hi all - I ran into a weird situation using a very basic S3 setup - this >> is without even trying to use the filebrowser with S3 which I know can be >> an issue. >> >> The basic problem is that when ever I go to an admin page that uses the >> tinymce JS files to render a rich text editor, I was getting a lot of >> 404/permission denied errors. Specifically the error was >> <Error> >> <Code>SignatureDoesNotMatch</Code> >> <Message> >> The request signature we calculated does not match the signature you >> provided. Check your key and signing method. >> </Message> >> >> >> where Django was referencing the tinymce JS files using a URL like this: >> https://<mybucket>. >> s3.amazonaws.com/grappelli/tinymce/jscripts/tiny_mce/plugins/inlinepopups/editor_plugin.js?Signature=<some >> >> signature> &Expires=1400621225&AWSAccessKeyId=<somekey> >> >> However, I've set my bucket to be completely public for reads so a URL >> like this works fine: >> https://<mybucket>. >> s3.amazonaws.com/grappelli/tinymce/jscripts/tiny_mce/plugins/inlinepopups/editor_plugin.js >> >> >> Now everything else works great - collect static, uploading an image (not >> using file browser, just using a regular image field) - and in the case of >> uploading an image, the AWS signature field is included and seems to work >> correctly. So only the admin JS files seem to be broken. >> >> The only thing that seems to get the tinymce JS files to view correctly >> is when I set >> >> AWS_QUERYSTRING_AUTH = False >> >> in my settings file. >> >> The only thing I can think is that grappelli is picking up the wrong AWS >> secrets when generating the link to the JS files. >> >> Is there something very basic here I'm missing? >> >> I've noticed a lot of the boto/storages examples that I see around the >> mezzanine forum have the query string auth turned off, but I'd like to >> understand the reasons behind this in case I want to roll out some >> cache-busting code later. >> >> thanks- John >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
