Awesome, thanks Jason!
And thanks for the details. I see from your post it's due to the Shopify admin now using React and GraphQL and requires fundamental changes. For my part, we'll make sure to send some more donations your way.
Anyone else who'd like to donate can find that here: https://freakdesign.com.au/pages/shopify-custom-fields
(In the meantime, if anyone knows of an app that can work with existing custom namespaces for Collection and Variant metafields in a user friendly way, please share. My search continues...)
@K&J, The Other Metafields section in the Bonify app is only for convenience. We don't know the settings used for other apps to generate those fields. We only see the raw stored data in that case, since the field configurations aren't in our database.
The alternative is to simply export your existing data (which you can do in our app), and import it into defined fields in our app, then update your liquid to call on those fields. Having done that, you'd be able to use the Bonify app to its full potential, with field types, image fields, repeaters, etc. or continue to use the basics free. No charge for most (all?) the same stuff in the Freak Design version.
We have a basic tutorial for migrating from one to the other. Normally I'd never post it here, but I will today only because of the current situation where people may be desperate for an alternative. No disrespect to Jason. https://support.apps.bonify.io/hc/en-us/articles/360007242231
In the end, you'll have something in the Shopify UI that looks like this:
@John, understand that. But that can be a ton of code updates for large existing stores, in exchange for losing the use of our custom namespaces. Would be great if Bonify would consider supporting custom namespaces more, as they are often very useful for developers storing large amounts of metafield data.
Even just adding a few more setting fields for Other Metafields where we can enter our custom namespaces that should show basic string fields in the Other Metafields section would improve the usability tremendously, and make it easier to switch without changing all our existing data. Stores that would be interested in this, just speaking from my client base's perspective, are large, paying stores on Shopify Plus and Advanced Shopify plans.
@K&J, I'm all ears. :) Send me your ideas! Let's come up with a solution. https://support.apps.bonify.io/hc/en-us/requests/new
The hardest part of building apps is getting useful feedback on what people need!
@K&J, A bunch of other merchants reached out to us looking for help with this same problem. Today we rolled out an update based on your feedback! We now have improved support for "other" metafields in the app. Thank you for your suggestions!
We published a fixed version on GitHub today.
You'll find it here: https://github.com/tonystrawberry/custom_fields_seido
It's a non official version, just a fix we did for ourselves. We'll try to keep it updated, but we may switch to another system at some point so, no guarantee.
|an hour ago|
|2 hours ago|