Home → Problems →

Assets API appears to have changed suddenly

• Edit

Soren Bjornstad

13 May, 2016 12:43 PM

Hello,

I've been using the download_path attribute of assets through the comments API for about a year without incident. Suddenly yesterday I started getting exceptions in code that's worked fine before. When I looked up what information was stored in the asset, I found the following (Python dictionary format):

{u'attachment_file_processing': False, u'code': u'4d001433c3be45161aa719534b2ef2c028b12f28', u'width': 651,
 u'updated_at': u'2016-05-05T23:13:05Z', u'created_at': u'2016-05-05T23:13:02Z', u'site_id': 28313,
 u'thumbnail': None, u'height': 564, u'parent_id': None, u'via': u'comment', u'content_type': u'image/png',
 u'processed_at': u'2016-05-05T23:13:05Z', u'filename': u'160506_Anki_crash.PNG', u'id': 6396401, u'size': 54239}

Obviously this does not include download_path, and it isn't at all the same as the list of attributes that's documented on the comments API page. Has something changed and the documentation not been updated, or is this a bug? It would really be nice to have the download path option back.

In case something's buggy and you need to take a look at it, our site is Anki and the discussion causing problems is the initial post on this discussion (unfortunately it's private; I don't know what ability you have to look into private discussions).

Thanks!

1. Support Staff 1 Posted by Courtenay on 14 May, 2016 03:58 AM

   

   Hey Soren, we pushed some urgent security enhancements to assets so some attributes may have been dropped. I'll dig into it over the weekend.

   • Edit

2. 2 Posted by Soren Bjornstad on 14 May, 2016 04:17 AM

   

   Thanks!

   • Edit

3. Support Staff 3 Posted by Courtenay on 14 May, 2016 06:31 PM

   

   OK, this is fixed and old behavior restored.

   • Edit

4. Courtenay closed this discussion on 14 May, 2016 06:31 PM.