1

Having the same issue as in this thread:

Console Error with Assets when Attempting to Index Amazon S3 folder

When trying to update the index for an S3 source, getting the following error in the Firebug console:

missing ) in parenthetical
</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;"
assets.js?2.0.5 (line 5626, col 11)

This was working fine until recently adding additional folders within an S3 bucket. Any ideas?


UPDATE: 04/01/2013

This issue ended up being an NAT issue with the Amazon cloud server, which is behind a firewall. It was blocking all outgoing requests. This is what was causing the JS errors I'm assuming.

I discovered this by editing my S3 source and trying to refresh the bucket list. Eventually I got the following error message:

Access denied by target host
  • What version, Synergema? And have you already tried uploading a fresh copy of the folders, both assets primary folder and the themes folder? Also, do you have any local File Upload preferences? Or is this all S3? – Lisa Mar 29 '13 at 0:37
  • Hi Lisa, Uploaded a fresh copy of all Assets files to the server, still getting the same JS error. We do have some local uploads, but trying to migrate all of those assets to S3. This was definitely working, so I'm a little perplexed as to what would have changed. Could it be something with the S3 source, permissions, etc? Unfortunately, the JS error doesn't give much hint, to me at least. – Synergema Apr 1 '13 at 15:55
  • Also, running Assets 2.0.5 – Synergema Apr 1 '13 at 16:05
  • Synergema - I may need to have a look on your server; but before we do that, can you test in another browser and see if it is browser specific? thank you! – Lisa Apr 1 '13 at 18:22
  • Thanks Lisa. Ended up tracking this one down, and updated my original post. This was a firewall issue. May be something to look at for the future though, that if Assets doesn't get a valid response from S3, that some error is displayed. As always, thanks for your help! – Synergema Apr 2 '13 at 1:03
1

Per original question poster's comment above:

Thanks, Lisa. Ended up tracking this one down, and updated my original post. This was a firewall issue. May be something to look at for the future though, that if Assets doesn't get a valid response from S3, that some error is displayed. As always, thanks for your help!

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.