Adding Custom Fields to the Shopify Dashboard

[Jason]

What was the namespace you used? It needs to be either "custom_fields" (or the shorter "c_f" - in newer versions). Feel free to contact me directly if you want to show some specific info if you don't want to dump it here.

[Tristan_James]

Thanks! Forgive my blindness, I must've missed that. Showing up happily now. I'd like to make shop level metafields though and I can't see where to add these so they aren't product specific?

Edit: Never mind - just found in General Settings. Thanks again for your work!

[Jason]

If using ShopifyFD  I added the metafield editor for shop level items in the settings section.

/admin/settings/general

[Jason]

Did some work today on a tailored version of the tool that adds the Custom Fields to variants. It's cool. but I'm not sure if others would need this functionality included into the general tool. Let me know...

[Jason]

Something else on the horizon. Custom fields for variants.

[Jason]

About to drop a version that allows you to show fields any namespace that appears on a white-list. The old method should also still work so this update shouldn't break existing functionality (though I've not had a chance to test this outside my own usage).

This means that metafields created by other tools and apps can also be shown directly in the editing window too. Or you just might really hate having to use the namespace names that I've set. 

[Jay_Freestone]

This is a fantastic tool, thanks!

I'm having a bit of an issue though, and I'm not sure if it's by design or a bug. I can fill in the custom fields, save them and refresh the page and the boxes will be empty again. The thing is, the field data has been saved. If I launch a metafield editor (or even ShopifyFD) the values are shown. It's just the custom field boxes are empty.

This isn't the end of the world, but it stops clients being able to easily edit the fields. It also makes it look as if they're empty when in fact they're not.

Bug or just the way it works at the minute? Either way, great work!

[Jason]

Poop. Sounds like a bug. Shoot over some details on the namespaces and keys and I'll try and replicate it here. You can open an issue on github too if you like.

[Jay_Freestone]

I'm currently using:

namespace: c_f

key: [p]Short-Description

namespace: c_f

key: [p][_t]Directions

namespace: c_f

key: [p][_t]Ingredients

Here's a video of the bug.

Thanks! Your plugin is a lifesaver.

[Jason]

Thanks Jay -- I'll check it out soon.
(I've downloaded that video so you can kill off that link if you need to)