Hmm... I'm pretty sure it should be generating that index. I'll pass this onto our S3 guy and see what he has to contribute.
Alright, looks like there might have been an issue with index generation for some communities. Should be back up now. You may have to delete the contents of the bucket and let it refresh/repopulate the content before the index is there.
about 5 days ago I deleted all the contents of the bucket but until today I still can't find the index file here http://club.zenius.net.s3-website-us-east-1.amazonaws.com/
Thanks for the heads up. We'll look into this.
has there been any progress on resolving this problem?
Thanks for the ping. Asking the server team to see what's up. :)
So, word is that if you want to regenerate the contents you need to update the bucket name. That means delete the bucket name setting and re-add it. If you delete the setting and then set it again Muut thinks it has to sync it from scratch and delivers all the static content.
I'm sorry. But, I've already deleted all my content on my s3 bucket then deleted the S3 bucket name in the muut setting and re-added it again. Up til now, my S3 bucket is still empty and Muut haven't synced it again.
I'll look into this for you
News about this problem?
Courtney was unavailable for a couple days. Pressuring him to take a look today. We should have some clarity soon. Thanks for your patience
OK, It should be working now. There was an invalid UTF character that was causing it to silently fail. And we have protections from spamming aws so after a number of failures we stop trying for a while. We fixed it so the invalid characters are handled correctly, and regenerated your forum onto your bucket. You should be good to go
Thank you, I can see that all the forum contents are there on my s3 bucket. I need a further clarification about the documentation http://learn.muut.com/developer/s3-bucket The documentation says: `Then Save the setting and if you then visit your bucket’s publicly accessible URL (eg. YOURBUCKETNAME.s3-website-us-east-1.amazonaws.com) you will see the index of your forum’s static content.` If I access my bucket here http://club.zenius.net.s3-website-us-east-1.amazonaws.com/ , I get 404 Not Found but, If I access my bucket with this url http://club.zenius.net.s3-website-us-east-1.amazonaws.com/i/ , I get the index of my forum. The difference is, I append `/i/` path
Hmmm It looks like our documentation is wrong, or rather has a typo. We've actually never had the root bucketname so it would load content. It is always prefixed it with '/i/' so that we don't conflict with any existing content and the muut client uses that as an identifier so it can look for the forumname (when embedding you can point to your s3 bucket) :)
Ah, so there is always a prefix '/i/' before the forum name. Thank you for the clarification.