Trouble updating assets using python ShopifyAPI

[Richard Antecki]

Hi guys,

I'm having trouble updating the value of an asset using the python version of ShopifyAPI.  I'm not sure if I'm doing something wrong, but I couldn't find many examples of updating objects via the API.

Here's what I'm doing:

        asset = shopify.Asset.find(remote_path, theme_id=theme_id)
        asset.value = "new contents"
        asset.save()

Asset.find() pulls the file contents correctly, but updating the value attribute doesn't seem to be updating the file on the server.

After the asset.save() call an 'attachment' attribute appears to be added to the asset object containing the base64 encoded value of the new file contents, and the 'value' attribute is also still there with the original value.

Also, the theme ID doesn't seem to be being passed in the XML request to the server during the save() call.  I found another similar topic regarding this (https://groups.google.com/forum/#!searchin/shopify-api/ShopifyAPI$20asset/shopify-api/Kvxt1nL6nls/P1mlENlIY_QJ) which gives me the impression that it's meant to be there.  I can't work out how to replicate the authors workaround in the python version of activeresource though.

Would appreciate any help.

Thanks!

Richard

[Dylan Smith]

This was a bug in the attribute setting for Asset objects. Thanks for letting me know about it.

I have fixed the bug and made a new release.  You should be able to `easy_install -U ShopifyAPI` the new version if you are using easy_install, and your problem should be fixed.

[Richard Antecki]

Hi Dylan,

Thanks for the quick response, it now works for assets in the currently published theme.

However, it still doesn't seem to be working for assets in unpublished themes.  When an unpublished theme asset is updated, it just overwrites the asset in the published theme.  No theme ID is being passed with the request.

The XML request currently looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<asset>
<value>NEW VALUE</value>
<created-at>2011-12-02 16:25:23+11:00</created-at>
<public-url nil="true" />
<updated-at>2011-12-02 16:25:23+11:00</updated-at>
<key>templates/index.liquid</key>
</asset>

Thanks,

Richard

[Dylan Smith]

You're right, it seems that the prefix option doesn't get stored after the call to find.  It looks like this is also a bug with the ruby shopify_api gem.

I have filed a bug report for both projects:

https://github.com/Shopify/shopify_python_api/issues/2

https://github.com/Shopify/shopify_api/issues/14

I'll let you know when I have fixed shopify_python_api, after which I will make another bug fix release.

[Richard Antecki]

Awesome, thanks!

[Dylan Smith]

Fixed and released.

Let me know if you experience any other problems after upgrading.

Thanks for reporting the issues.

[Richard Antecki]

All seems to be working fine now Dylan.  Thanks again for the fast turnaround.

[Richard Antecki]

One more thing...

When creating a new Asset, there needs to be some way of specifying
the theme_id. At the moment I'm doing this:

asset = shopify.Asset()
asset.key = path
asset.attach(read_file(path))
asset._prefix_options["theme_id"] = theme_id
asset.save()

Is there a more elegant / recommended way of doing this?

Cheers

[Dylan Smith]

  asset = Asset(dict(key=path, theme_id=theme_id))
  asset.attach(read_file(path))

  asset.save()

The resource constructor can take a single dictionary argument with attributes and prefix_options, and will split them according to the known prefix options.