New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incomplete container listing #5085
Comments
This is possibly an issue we have to analyze together with Rackspace support. Can you please post the transcript from the the logging drawer. |
I removed the xAuthKey. Hopefully everything else was ok to share (if not, could you please obscure or have me obscure it?). Process
Best, |
Now I'm getting 0 items...
|
Please contact Rackspace Support with a reference to this ticket. |
Not sure if a response is needed (or appreciated), but ... I am using a service called "Encoding.com" to encode files and automatically deliver them to Rackspace CloudFiles. When they deliver them, they are not creating the "folder" objects that are apparently required for the Rackspace API to call them up. Here's the official response from Rackspace: Somehow those folders you are not seeing were created in such a way that FireUploader (and I guess CyberDuck, etc) were not able to see them -- they were not created as actual folders (content type "application/folder"). I created a folder in the media container called "099904" then created a folder beneath that called "fmobile" -- then all of your objects showed up in that folder in FireUploader. It appears that whatever you used to upload the files didn't create the proper folder structure, so they are not showing up in FireUploader, etc. The files are still serving properly on the CDN however.I'm working with Encoding.com to hopefully have these entered correctly, but I can verify that with these "folders" created, CyberDuck works like a champ. Thanks for looking into this an all your hard work. Best |
Replying to [comment:7 nathanziarek]: Thanks a lot for your input on this. I don't think it is the same issue here according to the ticket description. Nonetheless, to recognize folder placeholder objects we require the to have a MIME type of |
When viewing a CloudFiles container with over 15,000 items, only four show in the interface.
The text was updated successfully, but these errors were encountered: