d
Topic
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited 6 months ago
g
14

Adding Custom Fields to the Shopify Dashboard

What is this madness?

In short, a tool to add Custom Fields to the admin dashboard. Since my other Dashboard tools are proving to be to super handy I figured Store Owners could do with a smaller version for adding metafields. Developers (and the brave) should stick with ShopifyFD. 

How to install:
http://freakdesign.com.au/blogs/news/how-to-setup-the-custom-fields-for-shopify-chrome-extension

Important starting note:

THIS TOOL IS UNDER DEVELOPMENT AND 
MAY CHANGE AT ANY TIME. USE AT YOUR
OWN RISK ON CLIENT STORES.

Rough User Guide (still incomplete)

This tool requires that certain metafields already exist before running the tool. If the whole concept of adding metafields is confusing or just plain scary, this is something you should get your code happy designer or developer to help you with. 

Once some metafields have been created, this tool will show something like this in your dashboard:

When we call these custom fields I am not being quite truthful - these are just standard metafields under a default namespace name, or one that your define yourself. It sure does make editing faster when you need to add the same sort of metafield (like a product youtube link) over and over again.

==================================

So err, where is it?

  1. You can nab it from the product home page over on freakdesign, or
  2. Grab the extension from the Chrome store.
  3. or manually install it as a bookmarklet from the github page.

==================================

Usage notes:

The namespace for all metafields is currently "c_f", though the legacy "custom_fields" version is still available.
Custom namespaces can be made also. 

There are special markers that help us know what sort of field we are showing.

  • "[a]": limit display to articles only
  • "[c]": limit display to collections only
  • "[g]": limit display to pages only
  • "[p]": limit display to products only
  • "[_c]": mark as a collection field
  • "[_t]": mark as a textarea
  • "[_n]": mark as a number field
  • "[_co]": mark as a color field
  • "[_d]": mark as a date field 

Planned to be added (if possible):

  • "[_f]": mark as a file field
  • "[_g]": mark as a page field
  • "[_p]": mark as a product field

Using metafields in liquid is easy. A basic example is shown below where c_f is the default custom fields namespace, and youtube is the key name. If you have brackets in the key name remember to use it as a string. 

{{ product.metafields.c_f.youtube.value }}

# If your key name is using brackets:
{{ product.metafields.c_f['[p][_t]some-key'].value }}

If you used a custom namespace (and setup the whitelist) you do not have to use the c_f namespace.

==================================

What's on the todo / research list?

  • file upload fields (very unlikely here, unless we are talking about uploading to the assets folder)
  • product picker (underway)
  • adding a simple html editor to a textarea field. This won't support images.
★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
i
Replies
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited October 21, 2013
g
1
upvotes

Tool and basic and rough user guide is now online for adding custom fields.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 27, 2013
g
1
upvotes

Chrome extension is in testing now so that guide above is now a little redundant. I don't think that devs would push the bookmarklet option on a store owner when the extension is a far easier install process.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 01, 2013
g
2
upvotes

Adding this one to github too:
https://github.com/freakdesign/shopify-custom-fields

The chrome extension will start using the files from github when it next does its update cycle.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
656
Last edited November 04, 2013
g
1
upvotes

4kin awesome;)

I'm a million different people
Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 05, 2013
g
1
upvotes

Totally handy for avoiding 'store owner brain explosions' when talking about metafields. I need to get the file uploads working for an future project so I might have that (plus some of the other todo items) in over the weekend.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
656
November 05, 2013
g
1
upvotes

bulk export / import?

I'm a million different people
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited November 05, 2013
g
2
upvotes

For this tool - no way. I really don't want to make it have too many features. That's when brains explode. All I want is for this to show a field and the store admin fills it in. Simples.

That said, bulk import and export of metafield data is something I've been looking at for the other tool (shopifyFD), along with doing bulk shipping updates. No one has annoyed for me for it, but if it would be useful I can add it to the list no probs.

Do you see a need for a store owner to have a bulk export with this one?

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
656
November 05, 2013
g
1
upvotes

Ah yes, noodles all over the wall for sure. Please add it to the list for shopifyFD though - would be sweet.

I'm a million different people
Posts:
3720
November 05, 2013
g
1
upvotes

I have learned a ton of lessons by offering up bulk import/export of metafields. My experience has been that it is something I do not want to ever get into again. Far too many ways merchants can screw it up. Not worth the trouble.

Custom Shopify Apps built just for you! hunkybill@gmail.com http://www.resistorsoftware.com
Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 07, 2013
g
1
upvotes

Not as pretty as the current collection picker, but this will do the job. You're going to have to (sorry) add specific strings to the key so the code knows what sort of field it is. Existing fields won't be broken.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 10, 2013
g
1
upvotes

Collection field support is released in the current master. For this to work you'll need to add the "[_c]" marker into the key name. eg:

namespace: custom_fields
key name: some-key[_c]
value: your value

The marker will be hidden from the client side so it does not look as ugly. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
114
November 19, 2013
g
1
upvotes

Jason, looks awesome as usual!
I cannot find the basic and rough user guide - where did you hide it?

Thanks

/Kim
Morfars.dk

Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 19, 2013
g
1
upvotes

I took the link down as the later updates (and conversion to a chrome app) made the doc redundant or wrong in places. I need to make another.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
January 18, 2014
g
1
upvotes

A small updates has been made to resolve this issue. When you next run the tool you should be seeing the new version. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
656
January 22, 2014
g
1
upvotes

It's a beautiful thing!

I'm a million different people
Posts:
3
January 30, 2014
g
2
upvotes

Hi Jason—

Really great plugin. I appreciate your effort and dedication. One question for you—are you able to easily make the inputs for the custom fields <textarea>'s instead of text type inputs? Or an option to do as such? My end hope is to implement a rich text editor for these fields as they are able to maintain any HTML put it them.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited January 30, 2014
g
1
upvotes

It would be easy enough to make them text areas or add a marker to set them as such (or auto switch them). Still early days on this tool with plenty of work still needing to be done but I agree 100% that it needs text areas. People are starting to show some more interest in it, so I'll pull my finger out and do the same.

As for your hope - that pretty easy. I did add a second (and third) RTE for a customised version so it's quite possible should you feel that way inclined. Image inserts and such are flaky, but generally editing is fine.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
billivycarter Member
Posts:
3
February 04, 2014
g
1
upvotes

Thanks for your reply Jason. Can you point me in the right direction on how to implement this as a custom feature? Text input is all I need, image inserts aren't necessary for the store I'm building. 

 

I'd be able to host the customized version on my end, but don't want to go outside your comfort zone with that.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 04, 2014
g
1
upvotes

Are you just needing some help on how to get this thing to work? I know I've given close to zero usage instructions...

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
billivycarter Member
Posts:
3
February 04, 2014
g
1
upvotes

I'm hoping for instructions/guidance on implementing the RTE fields. I have both ShopifyFD and Custom Fields bookmarklets working, and in use for building store with mock content. Desire is to implement RTE fields for input in Custom Fields. 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 05, 2014
g
1
upvotes

I'll do up a proper demo at some point but at it's simplest you'd just want to call the tinymce (v4) function on the field in question. If it's a basic input field, convert it to a text-area first. There's a couple of cleanup things I want to do on both scripts so I'll look at adding the rte option into the next version.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
billivycarter Member
Posts:
3
February 06, 2014
g
1
upvotes

Yep, that's what I was thinking the approach would be. Will you be willing to post the non-minified js file for the Custom Fields on github? Custom Fields seems to use input fields while ShopifyFD does use the textarea. Thanks for your help amd prompt replies btw.

mcgwebdesign Member
Posts:
1
Last edited February 07, 2014
g
1
upvotes

Is it possible to add a second RTE to a Page to add in unique content using this extension? From the frontend, all I can make out is an input area. This is my first Shopify project coming over from Wordpress so trying to wrap my head around the capabilities.


Thanks!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 08, 2014
g
1
upvotes

Is it possible to add a second RTE to a Page to add in unique content using this extension? 

No, not yet. I'd more than likely be adding a RTE metafield popup (or similar) into the ShopifyFD first so once that's working nicely I'll port some of that across here. There are easy ways to split content from within the one RTE so you may not even need this extension - make sure you're not over complicating things for yourself or client.

 

Will you be willing to post the non-minified js file for the Custom Fields on github?

Yes, but not immediately. Once the main functions I'll blast that up for everyone to pick apart / mod / fix. The main logic is pulled from ShopifyFD so if you're looking for some inspiration - check out the source for that. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
February 16, 2014
g
1
upvotes

Hi Jason—

I'm having trouble fully converting the basic input fields in Custom Fields to textarea's. I am able to convert the input so that it is now a text area, but the "Save With Custom Fields" button in the upper right corner does not appear. I am not sure how to update the saving functions and my trial/errors have failed so far.

Do you have any tips?

Thanks, William

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited February 16, 2014
g
1
upvotes

William - I had hoped to have those text areas added in but work got the better of me these last couple of weeks. It is something I plan to add in. Now that I've got a couple of design and dev helpers on board I can spare a bit more time for these things.

If you're not seeing that save button the script must failing somewhere, in the functions that setup the UI on the page. What errors are you getting in the console? 

Part of the issue with making the inputs into a textarea is that the code is only looking for inputs. Eg, on the product page the save function nabs the fields with:

var inputs = $('div.custom_fields_box input');

You'll need to account for that, though I might just amend the code for that part tonight. It won't break anything by including text areas in that group.

[edit] Basic textarea support added. I'll upload it shortly.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
February 17, 2014
g
1
upvotes

I'm new to Shopify so forgive me if this is too basic of a question... but how is this different than the Metafields2 app?  It seems it's within the Shopify interface whereas that app seems to take you to another website, but is the function the same?  Being to provide a non-dev interface for creating and editing metafields?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited February 17, 2014
g
1
upvotes

...Being to provide a non-dev interface for creating and editing metafields?

This one is yes. So a way for designers and devs to give the client some metafield control without making them freak out with too many options. For more advanced editing, use the parent tool - shopifyFD.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Tristan James Member
Posts:
2
Last edited February 17, 2014
g
2
upvotes

Hi Jason. Thanks for your work on this - looks like a super handy tool, though unfortunately I'm not having much luck so far... I've attempted to add new metafields with the ShopifyFD tool, which appears to be successful (I have a "1" beside "Metafields" in that box), however I can't get any to show up in the "Custom Fields" area created by this tool. All I get is "No custom fields found".

I've tried adding new metafields in the product window, and using the bulk metafields tool, but neither are showing. I've entered namespace, key and value with no spaces, all lowercase.

Any ideas?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 17, 2014
g
1
upvotes

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.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Tristan James Member
Posts:
2
Last edited February 17, 2014
g
1
upvotes

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 Shopify Expert freakdesign.com.au
Posts:
6741
February 17, 2014
g
1
upvotes

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

/admin/settings/general

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited February 22, 2014
g
3
upvotes

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...

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited February 24, 2014
g
2
upvotes

Something else on the horizon. Custom fields for variants.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
March 03, 2014
g
1
upvotes

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. 

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
Last edited March 20, 2014
g
1
upvotes

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 Shopify Expert freakdesign.com.au
Posts:
6741
March 20, 2014
g
1
upvotes

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.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
March 20, 2014
g
1
upvotes

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 Shopify Expert freakdesign.com.au
Posts:
6741
March 20, 2014
g
1
upvotes

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

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
March 21, 2014
g
1
upvotes

I am pushing an update now that should fix field population when using the shorter c_f namespace. I've done limited testing, but looks aok from here. Keep me posted.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Evulse Shopify Partner evulse.com
Posts:
411
March 21, 2014
g
1
upvotes

Hey Jason,

Have you come across a special way to pull in variant metafields at all in bulk? I know product ones you can pull in with the X-Shopify-API-Feature header.

Thanks,

Ryan

 

Want an app but can't find what you need? Let us know we custom build apps for Free
Posts:
3
March 21, 2014
g
1
upvotes

Works great, thanks! (Wasn't sure if the extension updated yet so I grabbed the js from Github).

Set a (small, I'm afraid) tip - thanks so much for fixing it!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited March 22, 2014
g
1
upvotes

Have you come across a special way to pull in variant metafields at all in bulk?

Nope. Attached resources have to be nabbed on a per object basis so I don't think there's a super magical way to just call up all metafields at once. It's come up before in discussions but in the end having to do a loop is not a major issue - it's just time.

Works great, thanks! (Wasn't sure if the extension updated yet so I grabbed the js from Github).

The extension just grabs it from Github anyway. Not really ideal as a CDN but it makes it simple for people to check out the source javascript that's getting injected into the page. There's a level of trust involved so I don't really want to mask the files behind a non tracked CDN.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Phillip Member
Posts:
1
April 03, 2014
g
1
upvotes

Incredible work on this, Jason. Are you planning to include support for page metafields?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
April 07, 2014
g
1
upvotes

Are you planning to include support for page metafields?

Yes, including collections and articles.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5840
April 12, 2014
g
1
upvotes

Hey Jason,

In the second post in this thread you show a screenshot of a guide, but the link your provide is not linking to a page where I see that guide available.

Tool and basic and rough user guide is now online for adding custom fields.

Where is that guide ^ ??

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Posts:
5840
Last edited April 12, 2014
g
1
upvotes

Oops, sorry, I just read above that the guide was taken down.

Jason, will you be implementing [p][_p]Label soon? :)

I'd need it for related products.

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited April 13, 2014
g
1
upvotes

I'm hoping to spend some quality time on both soon. This would included getting the product picker added in.

I am also seriously giving thought to dumping the idea of per product custom fields and just sticking to globals. It would save having to use the bracketing system for marking field types as the settings could be added into the shop level metafield value instead. Don't get lots of user feedback so I'm not sure if this would make people cry or not.

May as well keep rolling down the rabbit hole for now.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5840
April 17, 2014
g
1
upvotes

Hi Jason!

I don't see any use for product-specific metafield, so I'd drop those, yes. Metafields are only useful when output in the theme, and all products are rendered by the same product template. A product can have its Whatever Label field left blank, and a theme can check if it contains anything before it uses it.

I am having some trouble using custom fields for products though.

I have this Ingredients custom field:

This is the namespace and key:

So:

  • Namespace: c_f
  • Key: [p][_t]Ingredients

First problem:

Liquid does not like brackets when accessing Liquid tags. Liquid has a reserved use for brackets.

When using this:

<p>Ingredients: {{ product.metafields.c_f.[p][_t]Ingredients }}</p>

I get this warning when I am staff — you won't see these warnings as they are only visible to Shopify staff now:

Liquid Warning (staff only): Expected id but found open_square in "{{ product.metafields.c_f.[p][_t]Ingredients }}"

I work around this by using an additional variable:

{% assign key = '[p][_t]Ingredients' %}
<p>Ingredients: {{ product.metafields.c_f[key] }}.</p>

Second problem is that I can't read my ingredients directly.

On the product that has the Ingredients metafield set, I get nothing:

Oddly, when I inspect all custom metafields with that code:

<ul>
  {% for field in product.metafields.c_f %}
  <li>{{ field | first }}: {{ field | last }}</li>
  {% endfor %}
</ul>

I do see my metafield:

Weird!

So, there's no way to access the metafield directly that I know of.

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Posts:
5840
April 17, 2014
g
1
upvotes

Oh diantre you know what? I saved the key with a leading space in it!

So this works:

{% assign key = ' [p][_t]Ingredients' %}
<p>Ingredients: {{ product.metafields.c_f[key] }}.</p>

Shopify does not trim the white space!

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited April 17, 2014
g
1
upvotes

I'm doing some cleanup on this over Easter. Will make a new branch for it but the plan is to kill off per product custom fields which will also let me move (unless there's objections) the markers into the description of the master metafield so this:

product.metafields.c_f.[p][_t]Ingredients

can become:

product.metafields.c_f.Ingredients

I have got this roughly implemented already - just need to refine and test to avoid making things go boom. 

The whitespace for the fields is something I can help people avoid adding in error too.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
April 18, 2014
g
1
upvotes

The new update is live. Now I just need to get cracking on the docs.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
April 25, 2014
g
1
upvotes

Just as a heads up, the latest edition chrome extension didn't pop up the metafields information on the General Settings page. I thought I was just going crazy until I tried the bookmarklet which worked fine...

This was a first time install so not sure if it's a new issue, or just my particular setup. (Chrome 34.0.1847.116)

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited April 26, 2014
g
1
upvotes

This thread is talking about the Custom Fields extension - not ShopifyFD. This does not add a metafield edit box in the settings (though perhaps it should). I'll guess you're talking about the other one so I'll take a quick peek at it just in case there is some quirk. Do note that both the extension and bookmarklet use the same script source so I would have expected it to fail on both.

Thanks for the feedback - don't get much so even false alarms are handy ;)

 

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
13
April 29, 2014
g
1
upvotes

Thanks so much for creating this tool! Any idea how to preserve newlines within a text field?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
April 29, 2014
g
1
upvotes

It's not? I have the newlines being saved aok.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
13
Last edited April 29, 2014
g
1
upvotes

True, they get saved great, but they don't get outputted to the theme.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
April 29, 2014
g
1
upvotes

Have you tried using the newline_to_br filter on the output?
http://docs.shopify.com/themes/liquid-basics/output#newline-to-br

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5840
April 29, 2014
g
1
upvotes

Oh Jason, I am very much looking forward to the docs!

 

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited April 30, 2014
g
1
upvotes

Me too! I keep hoping the elves will do this for me whilst I sleep but they never do. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
April 30, 2014
g
1
upvotes

(Elves have done a little more work on the docs.)

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
4
May 04, 2014
g
1
upvotes

Hi Jason,

I just installed the chrome custom fields and shopifyFD extensions. I added a store metafield with the namespace c_t but for some reason the custom fields on the product page remain empty. (see screenprints attached) What am I missing?

Thanks.

M

 

Scrprnt thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 05, 2014
g
1
upvotes

Did I manage to write c_t as one of the default namespaces in the document?

That would not surprise me as I pushed the help doc out at stupid o'clock one morning so I'd expect typos. The namespace you might be wanting is c_f. If you want to use c_t you could add that to the white-list.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
4
May 05, 2014
g
1
upvotes

Hi Jason,

OMG... sorry for bugging you... works like a charm...

Mitch

Carson Shopify Expert shopifycustom.com
Posts:
50
May 05, 2014
g
1
upvotes

Hi Jason, I've got a long, enviable record of being daft, so I'm sure it's just me.

Any idea why I can't get this to show up?

...and yet

Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 05, 2014
g
1
upvotes

 I've got a long, enviable record of being daft, so I'm sure it's just me.

You and me both. Especially before I get a dose of caffeine. 

I can see you're using the default namespace but is this a shop level metafield, or just added to the product itself? It has to be a shop level metafield. So if you're using ShopifyFD jump to /admin/settings/general and chuck one in there.

It could also be a bug so keep me posted - I'd like to have all the little quirks cleaned up before the next major update to add page, product and linklist selectors.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Carson Shopify Expert shopifycustom.com
Posts:
50
May 06, 2014
g
1
upvotes

That was it - thanks for the help Jason.

HandHugs Shopify Partner handhugs.com
Posts:
57
May 06, 2014
g
1
upvotes

Did you guys ever figure out the Rich Text Editor functionality for the meta fields? This would REALLY help me out. If you have any instructions as to how to add new rich text editors to the product pages so we can enter in multiple text sections, I would seriously be forever grateful. Has anyone done it successfully?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 06, 2014
g
1
upvotes

It worked for a while but updates to the Shopify Dashboard js had some ill side effects on my end. I'd need to review their code again to see what's possible. For now, RTE additions are on hold.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
May 07, 2014
g
1
upvotes

Hi Jason, 

Building a big shopify site for a music shop, and we need to have different custom fields on each product page.

I have installed your two extensions, but when i add a metafield for the product page it does not add it to the product. The product page says that there are no custom fields found:

 

Any help would be appreciated 

Screen shot 2014 05 07 at 10.43.29 thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited May 07, 2014
g
1
upvotes

I've updated the docs to make this a little clearer, but the main metafield gets added to the shop, not the product. Head to your settings to add it. 
 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5840
May 08, 2014
g
1
upvotes

Jason...

"Rough guide", my a...e! LOL.

This is one of the best looking, most thorough, clear, helpful manual I have ever seen in my life!

You're the best!

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Cam Shopify Expert elkfox.com
Posts:
144
May 12, 2014
g
1
upvotes

Awesome work Jason :)

Designer, Developer, Director, Producer | Head fox at Elkfox | Owner at Green Hosting™ | Compiler of the 'Shopify Theme Framework'
Posts:
13
May 27, 2014
g
1
upvotes

Custom fields in Orders would be awesome! :D

Posts:
2
May 28, 2014
g
1
upvotes

I have a custom field on my products called "materials", but when I try and pull that information into a Packing Slip template (made in Order Printer) it doesn't show anything. 

How would I go about getting that info in there?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 28, 2014
g
1
upvotes

Filipe: Custom fields in Orders would be awesome! :D

Interesting. Since there's limitations on how you can use metafields on orders I did not expect anyone to want this. Should be a no brainer to add in. Thanks for the advice.

@Lachlan: when I try and pull that information into a Packing Slip template (made in Order Printer) it doesn't show anything

Sounds like a question to ask Shopify directly since they develop that app. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
154
Last edited May 31, 2014
g
1
upvotes

Regarding adding metafields to Order Printer templates, then unfortunately it's not possible at this stage, as Shopify do not expose metafields fields to us in the templates. It's something we get quite a few requests for our new templates app, but until Shopify support them it's a no go unfortunately :(

Awesome looking and very detailed guide there Jason, nice work!!

Bjorn Forsberg FORSBERG+two | Shopify Apps since 2011 View in Shopify App Store: https://apps.shopify.com/partners/forsberg-two
Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 01, 2014
g
1
upvotes

Hopefully everyone has been add their limit markers correctly as the latest update (just pushed) will now enforce them. You'll also spot custom fields in a few more places - including orders.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
13
June 02, 2014
g
1
upvotes

Hey Jason!

I can't seem to find the custom fields in the orders, is there anything different that needs to be done?

Thanks!

Filipe

Posts:
3
June 02, 2014
g
1
upvotes

Though custom fields are "ON" I'm getting the message "No custom fields found". 

Many of the details on our product pages are custom fields:

http://www.pauldrybooks.com/products/along-those-lines

Any ideas? This wasn't happening last week.

Thanks,

Will

 

Custom fields thumb
Posts:
1
June 02, 2014
g
1
upvotes

I seem to be having the same issue as a few with "No Custom Fields Found".  It was working fine up until recently.  I currently use "custom_fields" for the name_space.  Any thougts?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 02, 2014
g
1
upvotes

Bug reports are cool (as feedback is rare), but give me some facts to go on. Best place for them is here:
https://github.com/freakdesign/shopify-custom-fields/issues

But here is ok too.

If you have something not showing up show at least let me the namespace and key name of the main metafield. More facts means it's easier to test. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 02, 2014
g
1
upvotes

Mini update to custom fields just pushed. Fixes Gh-6.
https://github.com/freakdesign/shopify-custom-fields/issues/6

I'm assuming this applies to the couple of posts above.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
June 03, 2014
g
1
upvotes

That update solved the problem for me. In the future I'll give details and use the "issues" page. Thanks!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited June 06, 2014
g
1
upvotes

Both the key name and value will be checked for those markers. I've got no plans to stop custom fields working for those early users. Just use the newer approach from this point on. For reference:

  • [p] limits to products
  • [g] limits to pages

​So if you've added [p] it makes sense that they don't show on pages - that's what the limiter does.

Thanks for the info on the button - I'll sort that shortly.

(Sadly the pages and articles reload the page after saving, which means you need to reload the tool again. small drawback I guess)

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 06, 2014
g
1
upvotes

I see what you mean. Never added the code to handle other views for the legacy limiters. Might be able to add it without too much drama -- will look into it. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 24, 2014
g
1
upvotes

I need to add a couple more tweaks to the tools next week (for a client project). If you've got a feature request - let's hear it.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5840
June 26, 2014
g
3
upvotes

I would love a product picker! For 'related/recommended products' ! :)

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
leocrespo Member
Posts:
64
Last edited July 08, 2014
g
1
upvotes

This must be really obvious, sorry in advance for asking but how on earth do you get to this page in the manual? My "/admin/settings/general" url doens't have any of those fields. 

 

 

Google chrome thumb
leocrespo Member
Posts:
64
July 08, 2014
g
1
upvotes

What am I missing? Metafiled is created, namespace is "c_f", everything is saved an loaded however custom fields don't show up? 

 

 

What am i missing thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
July 08, 2014
g
1
upvotes

This must be really obvious, sorry in advance for asking but how on earth do you get to this page in the manual? My "/admin/settings/general" url doens't have any of those fields. 

I've not spent much time on the docs so I'm probably to blame for some of the confusion. You'd only see those fields if you had been using the ShopifyFD tool. If not, you'll need to add the metafields in another way. 

 I'll try and make that much clearer when I update the doc next.

What am I missing? Metafiled is created, namespace is "c_f", everything is saved an loaded however custom fields don't show up? 

You're missing the master metafields that need to be set on the shop object. Since that step got skipped, the fields won't show. 

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
leocrespo Member
Posts:
64
July 09, 2014
g
1
upvotes

Thanks Jason, every thing works fine now! Thanks for sharing the tool too, it's really useful! 

Just out of curiosity, when I add metafields here using Shopifyd, are they just for that particular product? 

 

 

 

What am i missing thumb
Posts:
8
Last edited July 14, 2014
g
1
upvotes

This looks really promising Jason, thanks for developing it! I can't seem to get "Custom Fields" to display any metafields though. All I get is the "no custom fields found" message.

Using another metafield editor (Metafields2), I added these metafields:

1. A shop-level "whitelist" key to whitelist an existing custom namespace for existing product metafields (namespace: "custom_fields_config", key: "whitelist", type: string).

2. A product-level "c_f" namespace metafield (namespace: "c_f", key: "tai_test", type: string).

3. A product-level "custom_fields" namespace metafield (namespace: "custom_fields", key: "tai_test_4", type: string).

I've tried Chrome and FireFox on the Mac.

Note that when I load ShopifyFD on a product page, I see the metafields in the custom namespace that I whitelisted IFF they have been assigned values for that particular product. But I also see other custom namespace metafields, so it seems to display them all there.

Also, are the "type markers" supposed to affect what the "Custom Fields" tool displays? I don't see them having any effect for me right now. Last question: will "Custom Fields" only display metafields that have values assigned (which seems to be the case with ShopifyFD), or should I be able to configure a product field once and then using "Custom Fields" to add values for each product?

Thanks! - Tai

 

Screen shot 2014 07 13 at 9.54.13 pm thumb
manoj Member
Posts:
1
July 16, 2014
g
1
upvotes

hi

i  love you awesome plugin... when i add to the product it is working fine and i can display in the front end.. now i am trying to do the same for the article part .. i can see the custom fields while adding the articles but i cannot display it in front end... i am using {{article.metafields.c_f.image[a].value}} to display since namespace is c_f , key is image[a]... i have use the [a] light marker...can you please guide me what is my mistake

thanks 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited July 17, 2014
g
1
upvotes

@Tai - you started out fine but your second and third steps are wrong. 

Whitelist is shop level, Custom fields to show are also shop level. It says that in doc:

Also, are the "type markers" supposed to affect what the "Custom Fields" tool displays?

The markers can do two things. Either set the type of field (so text area, collection, etc) and the other to limit when they appear. So [p] will make them appear on products only.

 Last question: will "Custom Fields" only display metafields that have values assigned

If a metafield has no value, it does not exist. It can't show what's not there.

 should I be able to configure a product field once and then using "Custom Fields" to add values for each product?

Yes, but only if you setup the field as a shop level metafield first.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
8
July 23, 2014
g
1
upvotes

Great, thanks Jason, it all makes sense now and I've got it working.

One thing I've noticed is that if I browse around between different products the custom fields stay visible, but if I use "Save" or "Save with Custom Fields" then they disappear and I have to re-load. This is true in Chrome and FireFox on Mac. Is this expected? Any solution in sight?

Thanks again!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
July 23, 2014
g
1
upvotes

Is this expected?

Sort of. Since Shopify determines what pages are ajax loaded the script is at the mercy of that.

Any solution in sight?

No - not unless I can find a way to fire the newer ajax loading code that's come with the dashboard update. So far no luck.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
14
July 27, 2014

Hi Jason,

Firstly, thanks for this app. It's a life saver!!!

Secondly, I was reading the thread and someone was asking about the RTE. I was wondering if you added to you app or if we still need to implement that TinyMCE, can you give me some directions on where should I add the

tinymce.init({selector:'textarea'});

Thanks!

Posts:
88
August 07, 2014

Hi Jason,

I'm a store owner, not a developer. But this tool is *potentially* exactly what I've been looking for. I want to centralize all my product info in one place so that I can easily export to a CSV, take the required data, and upload to different marketplaces.

For example - Amazon has a whole bunch of required fields to list on their marketplace. I might want a different photo than on my shopify website. So I could add a custom field for "Amazon Photo" "Amazon Description" "Ebay Photo" etc.

I've gotten everything to work, the only issue I'm trying to figure out is if it's possible to bulk export/import the metafields. Ideally, I'd like to just export my products via Shopify dashboard and have the metafield data included in one of the CSV columns.

This is something I've been looking for over the last week and everything I've found is way too overcomplicated. This would actually be perfect but the bulk export/import would definitely be required so that I could copy/paste data from one spreadsheet to another.

If this is doable then ENERGY DRINK tips coming!!!

Screen shot 2014 08 07 at 12.14.31 pm thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
August 08, 2014
g
1
upvotes

@Fernando Baba: Secondly, I was reading the thread and someone was asking about the RTE. I was wondering if you added to you app or if we still need to implement that TinyMCE, can you give me some directions on where should I add the

It's not as simple as just adding the tinymce,init. Since it's a bundled scripts not all the resources are available and existing hooks fire when you don't want them too. In short, conflicts everywhere. I suspect that I'll end up just side-loading my own version of tinymce whenever it's needed. Would rather not but seems to the be path of least resistance.

 

 

Ideally, I'd like to just export my products via Shopify dashboard and have the metafield data included in one of the CSV columns.

Bulk export is fine but bulk import is a nightmare factory I'd prefer to avoid. If this was a paid app it might be a different story but there's no time (or desire) to deal with the vast issues bulk uploading can bring. Granted I do have my own hacktastic internal scripts that do full json (not CSV) import and export but that's not something for public consumption.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
88
August 13, 2014

Bulk export is fine but bulk import is a nightmare factory I'd prefer to avoid. If this was a paid app it might be a different story but there's no time (or desire) to deal with the vast issues bulk uploading can bring. Granted I do have my own hacktastic internal scripts that do full json (not CSV) import and export but that's not something for public consumption.

I would certainly pay for this feature in the future.

Posts:
3
August 14, 2014
g
1
upvotes

Shopify must give us freedom to add custom fields, rather than by using browser extensions :(

E-Commerce Developer at Sparx Technologies
Posts:
8
August 25, 2014

Hi Jason,

Adding meta fields to variants is awesome! It's not very beneficial to me however if I can't change the metafield data based on the selected variant. Do you know how I would go about this? Any help is much appreciated!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
August 25, 2014
g
2
upvotes

There's an undocumented and not terribly well tested feature (aka: it might change) that will let you add custom fields for variants. Just add a [v] marker when making the shop level metafield. You should then see something like this:

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
8
August 25, 2014
Hi Jason, Thanks for your prompt response! I have already added custom fields to my variants. Now what I am wanting to do is change the custom variant data displayed on the page to correspond with the selected variant. For example I have a custom field called dimensions. I want the dimensions of the variant to change with the variant selected. I can loop through the variant dimensions and output them to the page but that does me no good. My customer has no idea which dimension corresponds with which variant. I need a way to display them dynamically.
Jason Shopify Expert freakdesign.com.au
Posts:
6741
August 25, 2014
g
1
upvotes

Sounds like you're getting into custom build territory and not something this tool would handle by default.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
August 25, 2014

Hi Jason,

I've been playing around with ShopifyFD and the Custom Fields for Shopify, separately and together as a combo, and I've noticed that if I browse around to different parts within the dashboard then both tools disappear completely. This occurs when I'm using only one tool at a time and also when I'm using the two tools together. Is this a problem that most people have been running into lately? Any solution in the near future? 

Thanks!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
August 25, 2014
g
1
upvotes

The bookmarklet and extension (when clicked) add extra script into the HMTL. If a page link or action in the dashboard forces a full html reload the scripts are lost. No way around that, and no plans on my end to try and stop that behavior. The full page reload would be for good reason, so you'll have to deal with reactivating the tool(s).

New versions of the script will hang around for as long as they can so make sure you're up to date.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Dan King Member
Posts:
12
August 28, 2014
g
1
upvotes

Hi Guys, 

Can somebody clarify how you display the metafields on a page rather than a product, if this is possible?

obviously the below is for the product page, but i wish to use on the front page.

{{ product.metafields.c_f.video_url }}

im guessing its not as simple as

{{ page.metafields.c_f.video_url }}

cheers in advance

Jason Shopify Expert freakdesign.com.au
Posts:
6741
August 28, 2014

im guessing its not as simple as

Assuming you've actually added the metafield to the page, it is that simple.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
September 06, 2014
g
3
upvotes

Just updated the script to re-enable custom fields on customer pages. Was broken, now it's not - huzzah!

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
7
September 11, 2014
g
1
upvotes

Woo hoo thanks Jason! :)

Posts:
2
Last edited October 07, 2014

Hi Jason,

My web developer added custom fields to our retail e-comm store for us. There's three custom field places for DETAILS, ABOUT THE BRAND, SHIPPING & RETURNS. My question is, is there a way to only have to type this once? I am having to type: details, about the brand, shipping & returns for each and every product. We have over a 1,000. Any help would be great, as I am new to custom fields. Thank you.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 07, 2014
g
1
upvotes

 My question is, is there a way to only have to type this once? I am having to type: details, about the brand, shipping & returns for each and every product. 

If the details are exactly the same on every product you don't really need a metafield on each one. That's just making life harder for yourself. If that's the case, talk to your developer about adding those three items as theme settings (or other repeatable methods) instead.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
2
October 07, 2014
g
1
upvotes

Great, thanks so much for your quick response. I'll be in touch with my developer. 

Posts:
6
October 13, 2014

Hi Jason,

As i have mentioned the Custom Field error on Customer page on this ShopifyFD thread,
Will that be related to the update you make on here?

Jason, thanks for all your work first. It's an awesome tool. 

Activating Shopify FD on customer page results in error:
ShopifyFD error: setup_customers: target HTML not found.

I assume the error comes from the recent update on shopify dashboard too.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 13, 2014
g
1
upvotes

This is fixed. It's not pretty, but I'll worry about that later.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
October 24, 2014
g
1
upvotes

I found a way to add simple rich text ability to my custom meta fields.

Run this in the console after loading your custom meta fields or add this to your bookmarklet:

//replace custom meta textareas with simple rich text editors
jQuery("textarea[data-namespace=c_f]").each(function(index, value) {
	var objField = jQuery(value);
	var val = objField.val();
	var id = this.name;
	
	//create editable div to replace textarea
	var objRTE = jQuery('<div class="simpleRTE autocomplete-field"></div>').html(val);
	objRTE.attr("style", "min-height: 72px; line-height: 20px; padding: 4px; overflow: auto;");
	objRTE.attr("id", "cf_"+id);
	objRTE.attr("contentEditable", true);
	objRTE.insertAfter(objField);

	//hide textarea
	objField.hide();

	//update textarea value after modifying or leaving editable div
	objRTE.keypress(function(event) {
		setTimeout(function(){
			$("textarea[name="+id+"]").val($("#cf_"+id).html());
		}, 100);
	});
	objRTE.blur(function(event) {
		setTimeout(function(){
			$("textarea[name="+id+"]").val($("#cf_"+id).html());
		}, 100);
	});
});

 

Norbert Member
Posts:
1
November 07, 2014
g
1
upvotes

Hi Jason,

Can you take a look at the manual installation for Custom Fields? I think there is an issue with the link syntax in terms of the quotes when saving as a bookmark. When I try to save as a bookmark in Safari and run it in the Shopify admin, it doesn't work and my console shows that it failed to load the resource. The ShopifyFD works fine though.

Here is the link I'm referring to: https://rawgit.com/freakdesign/shopify-custom-fields/master/installation.html
 

Thanks.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 08, 2014

Haven't looked at those links in a while - no doubt they're either wrong or just borked. I'll adjust those. Thanks for the heads up.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mfk Member
Posts:
52
November 10, 2014
g
1
upvotes

Does this work on dev shops? I've added the following metafield on the settings page with shopifyfd,

c_f

frame_size

[p][_t] Frame size

 

but it doesnt create a new metafield on the product admin page.

i've also tried deleting metafields and recreating them with different key and value but its still not showing..

Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 10, 2014
g
1
upvotes

It works on any dashboard - plus, dev, whatever. Sure you're using the latest version? Works fine here.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mfk Member
Posts:
52
November 10, 2014

tell me if i'm doing anything wrong.

1) log in to my shopify shop admin.

2) go to settings (shop.../admin/settings/general)

3) Click on the bookmarklet. ShopifyFD loaded.

4) Create metafield (see screenshot attached) and save with the button within the metafield editor.

5) Go to product > a specific product... i cant find any metafields here.  (even after a refresh and reloading shopifyfd) hmmm

Screen shot 2014 11 10 at 3.55.49 pm thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 10, 2014
g
2
upvotes

You haven't said anything about running the actual custom fields tool. ShopifyFD and Custom Fields are two different things. This thread is about Custom Fields.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mfk Member
Posts:
52
November 10, 2014
g
1
upvotes

Ah right. sorry about that. got it all mixed up. so i ran Custom Fields and it now shows. 

so if my client wants to edit the custom metafields, they would have to run the bookmarklet yes?

Posts:
1
November 21, 2014

Hey Jason,

First, thanks for the great tool. Second, is there a way to modify the sort order of custom fields in admin area?

Thanks

Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 22, 2014
g
1
upvotes

so if my client wants to edit the custom metafields, they would have to run the bookmarklet yes?

Yep.

is there a way to modify the sort order of custom fields in admin area?

No. It just spits them out in whatever order Shopify returns them in. I guess if you're pushing a lot of custom fields things might get a little harder to find the one you want. What sort options would you be wanting?

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
December 07, 2014

Mainly just dropping in to say thanks for the fantastic tool.  I've just started using Shopify and have been writing an import tool to migrate data from an old system into Shopify for a friend, but was wondering how to let the users actually edit the fields... seems crazy that there is no interface for doing this built into shopify, as the standard product metadata is pretty limited.

The only question I did have is whether there was any particular reason that the javascript in https://github.com/freakdesign/shopify-custom-fields is minified.  I can beautify it, edit it and reminimise it, but the diff that github gives you isn't going to be very helpful :D

I was going to add sorting options by adding weight markers, which would just be something like [1],[-1],[1000] or whatever.  Default weight (where not specified) would be zero, sorting would be in ascending order, multiple weight markers would be ignored.  The guy above asked for it, not sure whether it's useful to many people or not, but it would be nice to help out the development of such a useful tool.

Posts:
15
December 13, 2014
g
1
upvotes
Jason Shopify Expert freakdesign.com.au
Posts:
6741
December 14, 2014
g
1
upvotes

@Liam -- See this. It does not apply so much now since the major dashboard update is out, but that's the reason to date. I should pull my finger out and clean up the source and push it to git.

I am mindful about adding too many markers into the tool as it was only ever imagined to be a simple tool, with ShopifyFD being the complex one. There'll be some point adding a tonne of markers will just be unworkable. I'll add the ordering as a feature request.

@Mark -- I don't think posting into an unrelated thread is going to help you much.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
15
December 15, 2014

Hi sir @Jason. I just wondering, until now, still no one can't help me to fix that. I've posted an question but no one help me.

Posts:
1
December 18, 2014
g
1
upvotes

good

Jason Shopify Expert freakdesign.com.au
Posts:
6741
January 06, 2015
g
1
upvotes

Please note : I followed this document but Custom Fields not worked for me.

The doc is old but it should still give you the basics on how to use. What is the namespace and key that you created (as per page 4 of that pdf you linked to)?

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Commonmind Member
Posts:
1
January 13, 2015
g
1
upvotes

Hey Jason, 

Thanks for the amazing work on this project. I'm using ShopifyFD and Custom Fields in conjunction with one another. They work great together and so far I've successfully added custom fields to most of my product pages. 

Unfortunately, I have never been able to "Save with Custom Fields" and thus my clients don't have access to edit or change those fields on their own. Obviously, I'd prefer not directing them to download a browser plugin. Do you know what might be causing the issue?

Screenshot 2015 01 13 03.35.29 thumb
Wieger Jelsma Member
Posts:
3
January 13, 2015
g
1
upvotes

Thanks for this tool! But I'm having troubles though.

I can’t get custom namespaces added to the whitelist. I made a video to clearify. http://screencast.com/t/1CjzCp2ssLH5 The fields added to the ‘store’ namespace (which is whitelisted) don’t appear on the collections page. 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
January 13, 2015

Commonmind: Unfortunately, I have never been able to "Save with Custom Fields" and thus my clients don't have access to edit or change those fields on their own. 

Bit useless if you can't save them. I don't use the tool that often to know when quirks appear so thanks for the heads up. I'll check it out.

Wieger Jelsma: The fields added to the ‘store’ namespace (which is whitelisted) don’t appear on the collections page. 

Never tried adding spaces into the key name but from your vid it seems to work. Not something I'd generally recommend. Curious. Does the custom namespace field appear when the others are removed or does it refuse to show then as well? I'll check things out.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Wieger Jelsma Member
Posts:
3
Last edited January 13, 2015
g
1
upvotes

Hi Jason, Thanks for your quick reply.

When I remove the other fields the custom namespace appears. I now don't have any fields in the c_f namespace. I guess that's a workaround?

Actually, I don't know how to remove namespaces which I created for testing purposes. Any idea?

Thanks!

Edit: When I add another custom namespace (also to the whitelist) it doesn't appear. It seems that custom namespaces are limited to one?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
January 13, 2015
g
1
upvotes

I'm not convinced that it wasn't the spaces in the key name causing a bug as it should work with multiple namespaces. I'll test it out and see what's up.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited January 13, 2015

@Commonmind - I checked it out and it all seems aok here. Based on your screengrab I am wondering if this is more of a UI issue. You did notice that the button to save custom fields is no longer at the top of the page right? 

 

@Wieger Jelsma - I was able to replicate it and - as suspected - it's a bug caused by the spaces in the key. I've added that as an issue and get it fixed with the next update.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Wieger Jelsma Member
Posts:
3
January 13, 2015
g
1
upvotes

Ah ok. Thanks!

Posts:
2
January 22, 2015
g
1
upvotes

Jason, this is so very awesome. I thank you very much!

I cannot find any answers to this question in general, from Shopify, so I thought I would ask you: I would like my customers to be able to use the "Sort by" drop down menu on the Collection page using product data that is stored in these new custom product fields I've created. I have edited the sort-by.liquid but can't figure out how to get it to recognize the new custom fields I made.

For example, we publish books and the "Publication Date old to new/new to old" would be a great option to include in the "Sort by" menu; we have the Pub date data stored in a custom field -- how can we get Shopify to recognize that field for the Collection page "Sort by" menu?

Any tips or ideas? Thanks! Eliza

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited January 22, 2015

how can we get Shopify to recognize that field for the Collection page "Sort by" menu?

Since you can't natively order by a metafield that's not going to be that simple. You'll need to create your own custom javascript methods (or make an app) to order the collection. Books stores tend to have massive collections so a javascript solution may not be ideal. Why not use the publish date field built in to the admin instead? I assume that will work with the default date ordering.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
13
February 06, 2015

In general, short of sorting, is there a way to use the custom field to help identify or organize groups of products?  For example - can you:

1) Search for the value in a custom field, then export the found products to a .CSV?

or 2) does the custom field show up as a column in an exported .CSV, or can you get it to show up?

I am hoping to use this technique to keep product history log data.   Being able to make to-do lists based on various tasks, status, people and dates associate with products would be HUGE.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 07, 2015
g
1
upvotes
  1. This tool doesn't do that, but you could build something that does it for sure. Very possible.
  2. The standard Shopify CSV export does not include metafields and there's no way to magically include them. You'd be looking at creating your own tool or app.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5840
February 11, 2015
g
2
upvotes

Hey Jason, will you be implementing [p][_p]Label soon? :)

I'd need it for related products.

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Posts:
656
February 11, 2015

^^^ Yeah yeah YEAH! Yeah?

I'm a million different people
Posts:
1121
February 12, 2015
g
1
upvotes

What is "[p][_p]Label"? Do tell please!

 

http://www.StandoutDesigns.com ::: Solid Wood TV Furniture for Enthusiasts. Made in USA.
Posts:
5840
February 12, 2015
g
1
upvotes

Ha ha, it stands for:

  • Custom field to add only to products.
  • To let you select another product.

We have a collection picker now, but it looks like we do not yet have a product picker.

Caroline from http://11heavens.com ∴ mllegeorgesand AT gmail DOT com
Posts:
1121
February 12, 2015

Thanks! I think. ;-)

http://www.StandoutDesigns.com ::: Solid Wood TV Furniture for Enthusiasts. Made in USA.
Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 13, 2015

There's an update for CF planned to deal with upcoming dashboard changes. The product picker will probably end up appearing after that's done and dusted.

Would be nice if I was able to tap into the existing picker but it's tucked away in function I can't get to. Will have to DIY.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
12
Last edited February 15, 2015
g
1
upvotes

followed the instructions for adding a super text field to a product page. No magical new text box showed up on my product page dashboard.  Clearly I missing a few step?

 

so I add it manually to product.

{{ product.metafields.c_fsuper_textarea[p][_t]enter your text here.value }}

still no banana

Metafields thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 15, 2015

Looks like you're adding the metafields (with the markers) onto the product, rather than onto the shop. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mouhcine Member
Posts:
5
February 22, 2015
g
1
upvotes

Hello friends Do you want to purchase new games and original high quality and very low price this offer is very beautiful

mike Member
Posts:
1
February 25, 2015
g
1
upvotes

It looks like the redesigned product dashboard page breaks the plugin. I'm getting a "Custom Fields error : setup_custom_fields() : target html not found" error.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 25, 2015
g
1
upvotes

Mike - are you running on Shopify Plus? Shoot me an email and I'll give you a link to a temporary version that will cover you until the rollout is complete on all stores.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
March 10, 2015

The rollout of a new product page layout in the Admin has started to rollout. This change breaks the current version of Custom Fields. I've got a fix already prepped. so once the rollout is complete I'll upload the fix. If you are desperate and need something quicker just shoot me a message and I'll send you a link to the unreleased version.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
4
March 17, 2015

Hi,

I am trying to add Height/Width/Length metafields to variants.  I added those to shop level using [v] modifier but they don't show up at all in the variant editor table like the screenshot above (7 months ago).

Is it a problem with the Shopify updates to the products page? Or am I missing something?

Thank you.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited March 17, 2015
g
1
upvotes

@Alyssa
I've made a couple of bug fixes tonight so you might want to try again after clearing browser cache. If you then still have issues you might need to shoot over a screen capture of the product page so I know what version (of shopify product page) you're using. I can do some more testing from that point.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
4
March 17, 2015
g
1
upvotes

Hi Jason,

I tried using a bookmarklet which pulls the code directly from rawgithub as well as the Extension which pulls from Amazon S3.  Neither worked.  Here's a screen shot of the products page - looks like we're on Shopify Plus: http://screencast.com/t/pmTxpwicc

Thank you very much for your help so far.

 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
March 17, 2015

I've got a bunch of Plus clients and they are running the update aok. That said, you're a Plus user still on the old layout (which is really odd, since those accounts got the layout update first) so the newer versions of the tools are not going to work.

I've made a Legacy version of ShopifyFD for edge cases like this so I might need to do the same for Custom Fields too.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
March 19, 2015
g
1
upvotes

Here's a Legacy version of Custom Fields should anyone still need it:
https://freakdesign-us.s3.amazonaws.com/shopify/custom_fields/legacy/installation.html

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
40
April 10, 2015
g
1
upvotes

Hi,Jason:

Would you please help me the followings? My theme is Minimal. Here is my store:

www.forevershop.myshopify.com      (logo in: tina scott, pdw: tina1).

1. On my home page, in the Bestsellers and New Arrivals collection sections: Please make the product title width the same with the product image icon width (the icon image displaying in "Medium" size now. If I change to "small", then the displaying is too small. So, please open my "Summer Dresses" page to see (Dresses --> Summer Dresses). I like the image size displying on this page as well as the title of the product title.Can you make all my product thumb nail images in my Bestseller and New Arrival section display as the same size in the Summer Dresses page? 

2. Can you make only llow 2 lines display under the Bestsellers and New Arrival collection section. And also, add narrows on each section to allow buyer to click to see more Bestsellers, or New Arrivals.

3. Please help me to display the sku # into the product detail page, located above the "free shipping" image.

3. On the tool bar, please add " Sale Assistance: 713-334-3788 " (Please see the attached file "Request1_1 as a reference".)

4. On the right of the header, add a image or words " Free Shipping & Free Tax ". I will give you the image in next replay (Please see the attached file "Request1_1" as a reference.)

 

Thanks!

Jane

04/10/15

 

Request1 1 thumb
Posts:
40
April 10, 2015

Hi, Jason:

I am attaching the image of "Free Shipping & Free Tax" in here in order to let you help me

to add this image to the right side my header. 

Thanks!

Jane

04/10/15

 

Freeshipping freetax thumb
Posts:
1121
Last edited April 10, 2015
g
1
upvotes

Pardon me for jumping in here, as Jason can speak for himself, but (1) post is off-topic in that the discussion of this thread is about Jason's util to add fields to the admin, and (2) the forum is a place where people discuss how to do things, and learn from the exchange of info with others. Forum members don't normally post credentials and invite people to make changes to their sites directly. You should really change your credentials and contact Jason directly about hiring him to make the actual changes if that's what you require. As it stands ANYONE can login.

 

http://www.StandoutDesigns.com ::: Solid Wood TV Furniture for Enthusiasts. Made in USA.
JCAndrea Shopify Partner
Posts:
22
April 13, 2015
g
1
upvotes

Beautiful little tool... I've read a lot of threads, but didn't find one that specifically states if you have a 'marker' for metafields that you only want to show up on the Customers page like you do for Products [p].

  • "[a]": limit display to articles only
  • "[c]": limit display to collections only
  • "[g]": limit display to pages only
  • "[p]": limit display to products only
  • "[_c]": mark as a collection field
  • "[_t]": mark as a textarea
  • "[_f]": mark as a file field
  • "[_i]": mark as an integer field
  • "[_g]": mark as a page field
  • "[_p]": mark as a product field
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited April 13, 2015

There's a "[cu]" marker for customers only that should do what you want. Don't think that one has been heavily used so be sure to shout if you spot an issue. 

The predefined list of markers is below (though not all are active)

[a] : articles 
[c] : collections 
[cu] : customers 
[g] : pages 
[o] : orders 
[p] : products 
[v] : variants 
[_c] : mark a collection type 
[_f] : mark a file type 
[_i] : mark an integer type 
[_g] : mark a page type 
[_p] : mark a product type 
[_t] : mark as a textarea type 
[_l] : mark as a linklist type 

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
JCAndrea Shopify Partner
Posts:
22
April 14, 2015

Awesome... works great so far! I should have just tried [cu] but oh well. Thanks again!

Posts:
5
Last edited May 06, 2015

Hi all,

I'm having a lot of difficulty using custom fields on the Collections pages.  For some reason my field data is sometimes not being displayed on the page at all (or appearing in the source code).  Often, it will appear for one collection page, but not a second.

Here's what I've done:

1.  Create a new custom field with namespace c_f and key CollectionDescription2[c][_t] with shopifyFD

2.  Under my collection pages "sprays" and "greases", used the Custom Fields plugin to add data to each of these

3.  In my collections template, I added this code: 

{% assign collectiondesc2 = collection.metafields.c_f['CollectionDescription2[c][_t]'] %}
{{ collectiondesc2 }}

 

Now the weird part - in some instances, the collectiondesc2 variable will output fine on the "sprays" page, but then not on the "greases" page, both of which are collections.  Sometimes they both disappear.  I've tried on multiple browsers and have confirmed with others that they just can't see it.  In most cases it seems to be only 1 that will show.  When it doesn't appear view>source also does not show anything.

What in the world is going on here?  Any tips to investigate this?

I can share a URL/templates/etc if anyone wants to look

 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 06, 2015

I'm having a lot of difficulty using custom fields on the Collections pages.  For some reason my field data is sometimes not being displayed on the page at all (or appearing in the source code).  Often, it will appear for one collection page, but not a second.

The big question is do the values show correctly in the admin?. If they do you know it's either your code, or something amiss with Shopify cache. Less likely to be cache as I see most additions appearing straight away.

As a sidenote, you don't need to put the markers in the key anymore and can be placed within the value of the shop level metafield instead.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5
Last edited May 06, 2015

The keys appear properly in the admin panel for both pages, but only one ever shows up on the front end. 

I moved that code to the very top of the collections.liquid template so there really shouldn't be any weirdness.  It's just bizarre that only one of the pages works.

Also, placing the tag in various parts of the template doesn't seem to matter (at the top, before %endpaginate, etc).  The oddest thing right now is that both pages are working in Chrome for me, but if I switch to firefox or safari it will only show on one page.

Posts:
5
May 06, 2015

Update:

I just changed to putting the markers ( [c][_t]) in the value instead of the key, and that solved my problems.

I've confirmed with another shopify developer, Jeff L, that this issue exists when you try to include the markers in the key.  The values just magically appear and disappear.

You might want to log a bug for this, or at least warn people that the markers are no longer properly supported in the key area.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited May 06, 2015

You might want to log a bug for this, or at least warn people that the markers are no longer properly supported in the key area.

It's not a bug with the tool if it's proven to successfully save and retreive the metafields correctly in the Admin (with the markers in the key). I'll do some tests here and see if I can replicate the issue in liquid. If I can, I'll give Shopify a nudge about it and see if something has changed on that front.

The project is on github so you're welcome to make bug reports there should you come across anything. Feedback is a rare thing, so the more the merrier: https://github.com/freakdesign/shopify-custom-fields

[edit] I did a quick test on multiple collections and saw no issue. 

	{{ collection.metafields.c_f | json }}
	output: {"collectionDescription2[c][_t]":"test"}


	{{ collection.metafields.c_f["collectionDescription2[c][_t]"] }}
	output: test


	{% assign string = "collectionDescription2[c][_t]" %}
	{{ collection.metafields.c_f[string] }}
	output: test

If someone want's to give me code that can reproduce the issue I'd be happy to run it through it's paces.
Sidenote: The only times I've seen a metafield not appear is when an object is hidden.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Kyle Tully Member
Posts:
13
May 16, 2015

Since the new Shopify admin changes I can't seem to get the customfields edit page to load on /admin/settings/general

Anyone else having this issue?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 17, 2015

A quick update on my previous post. The issue is on Shopify side and the dev crew are looking into the handling of strings when referencing objects like so: 

collection.metafields.c_f["collectionDescription2[c][_t]"]

@Kyle: Since the new Shopify admin changes I can't seem to get the customfields edit page to load on /admin/settings/general

Custom Fields tool never loaded anything on that page. Sure not confusing this for ShopifyFD or something else?

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Kyle Tully Member
Posts:
13
May 17, 2015

Custom Fields tool never loaded anything on that page. Sure not confusing this for ShopifyFD or something else?

Page 4 of the guide says it:

https://freakdesign-us.s3.amazonaws.com/shopify/custom_fields/freakdesign-custom-fields-for-shopify-guide.pdf

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited May 17, 2015

Page 2:

Whilst the wording could be clearer I am 100% sure that CF has never had the ability to edit / show metafields on that link you referenced.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Kyle Tully Member
Posts:
13
May 17, 2015

Ah I missed that, thanks!

J. Mings Member
Posts:
1
May 20, 2015

How would you reference a custom field in another app?

I'm using itDuzzit to connect Shopify to Salesforce. I can pull in a customer's first name using [[Shopify:Customer First Name]] or the order number with [[Shopify:Order Name]].

I'd like to bring in a field named c_f.product_shortname[p]

Jason Shopify Expert freakdesign.com.au
Posts:
6741
May 20, 2015

The Custom Fields tool is just saving metafields. If the app can grab metafields it should be able to grab ones created here. Can't answer if "itDuzzit" is capable of such things or not -- you'll need to talk the app developer.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
2
June 08, 2015

I would also love an ability to at least bulk export these custom fields. I'm using them so my client can store information like "how much were raw materials" and "how long is this piece", and she really wants to be able to import/export this along with the rest of her catalog data. I understand there's no way to get it into the built-in Shopify import/export feature (because Shopify seems to have basically dropped all development support of metafields), but something at least close would be great. So if you're considering future development paths on your end, please count me as another vote for export capability!

Posts:
1121
June 08, 2015
http://www.StandoutDesigns.com ::: Solid Wood TV Furniture for Enthusiasts. Made in USA.
Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 08, 2015

I would also love an ability to at least bulk export these custom fields.

I've got secondary tools that handle import and export but I've not built them into Custom Fields or ShopifyFD yet. It's on the list however.

Shopify seems to have basically dropped all development support of metafields

That's not true at all. The new bulk editing feature in rollout right now adds basic metafield editing. Metafields are finally getting some official additions to the Admin. What they are adding should compliment my tools quite nicely.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
2
June 09, 2015

Yeah, Metafields2 is what I was looking at too. Glad to have another recommendation for it, even if it does cost $$. That's probably what I'll end up with; just not looking forward to teaching my client how to use it! Custom fields is so much easier!

Posts:
1121
June 09, 2015

Yes, for import/export, it might be the way to go. The app's interface for regular managment is, to be kind, lacking. Jason's tool is far superior in that regard.

 

http://www.StandoutDesigns.com ::: Solid Wood TV Furniture for Enthusiasts. Made in USA.
Kyle Tully Member
Posts:
13
June 17, 2015

Is there a way to use a variable or select a value from a dropdown for metafield values?

e.g. I have a "delivery time" metafield for which I'd like to be able to select an option from 3 pre-determined values. That would keep it super simple for the shop manager and make updating a delivery time for a particular service a breeze. 

 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
June 18, 2015

Not in the current version. A future update has more control over the custom field settings and will allow for customisation via a JSON settings metafield. This metafield will largely replace the need to add multiple shop level metafield for each custom field.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Cam Shopify Expert elkfox.com
Posts:
144
June 18, 2015

Shall we start calling you Json now? ><

Designer, Developer, Director, Producer | Head fox at Elkfox | Owner at Green Hosting™ | Compiler of the 'Shopify Theme Framework'
Kyle Tully Member
Posts:
13
June 18, 2015

OK cool, appreciate all the work you put into this.

greg-gkr Member
Posts:
11
July 02, 2015

When using ShopifyFD I can see the metafield I added to an order, but custom fields isn't picking up on it :s

From what I read in the above comments, Custom Fields works with Orders...am I wrong? If not, any idea what might be preventing Custom Fields from showing my estimated shipping date?

 

 

Shopifyfd orders thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
July 02, 2015

@grek-gkr - Can you show me the metafield(s) you created on the Store (not the order) as part of the custom fields setup?

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
greg-gkr Member
Posts:
11
Last edited July 02, 2015

Thanks Jason! I went to /admin/settings/general, turned on ShopifyFD and added the custom field to the store and it worked!! Originally I was doing it on the specific order.

 

namespace: custom_fields

key: [o]estimated_shipping_date

 

Thanks again! Really hope Shopify adds this to their core product

Jason Shopify Expert freakdesign.com.au
Posts:
6741
July 02, 2015

No probs. Common mistake to make, and a sign that I really need to make the docs a hell of lot clearer. One day!

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
greg-gkr Member
Posts:
11
July 02, 2015

One day! - LOL, I'm a dev...I hear ya ;p

Posts:
9
July 06, 2015

Hi Jason, managed to get things up and running.

Just wondering if you can have one or many values per key? For example, multiple PDF downloads, or multiple videos?

I've made it work with ShopifyFD (see attached for how I've made it work):

{% for pdf in product.metafields.pdf %}
            {{ pdf | last }}
{% endfor %}

But I'd like to make it work with Custom Fields. Let me know!

Meta thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited July 06, 2015

Just wondering if you can have one or many values per key? For example, multiple PDF downloads, or multiple videos?

A key is unique to each namespace. You could have a value that you turn into multiples in liquid. That has nothing to do with this tool but for example:

{% comment %}
  Assumes a value of "somefile.pdf,some-other-file.pdf"
{% endcomment %}

{% if product.metafields.foo.bar %}
  {% assign metafieldValue = product.metafields.foo.bar | split:',' %}
  {% for filename in metafieldValue %}
    filename is:{{ filename | strip }}<br>
  {% endfor %}
{% endif %

[edit] Typos!

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
9
July 06, 2015

That'll do the trick! Thanks Jason.

CarlowSEO Shopify Expert www.carlowseo.com
Posts:
489
Last edited July 30, 2015

Maybe answered already but can I use this AND the Custom Fields app for the customer side to store "Customer" metafields, but not have them appear on a product page?

Right now I can create the field, have the end user edit them, spit the info out everywhere I want but if I look at a product page in the admin I still see customer ein field.... I think it is missing a filter to only show these fields on a customer page (like [p])

EDIT -----------------

HELPS TO READ - Use [cu]

Trevor www.carlowseo.com
Kyle Tully Member
Posts:
13
July 30, 2015

Anyone know if you can access metafield info from the search.results?

I've tried item.metafields.c_f.whatever with no luck.

Posts:
1121
July 30, 2015

How about trying to use the item.handle to retrieve a product object, then use that object to get at the metafields?

 

http://www.StandoutDesigns.com ::: Solid Wood TV Furniture for Enthusiasts. Made in USA.
Posts:
42
August 06, 2015

Hi Jason,

This all looks great except I cant find anywhere that actually says how to use it.  Here is what I've cobbled together.

I want to add a Model Name to my variants in addition to the already existing SKU

In Settings, with ShopifyFD, I've added a Metafield with the namespace "c_f", the key "Model" and the value of "[v]" for varient.

Then I go to a product, launch the Custom Fields tool and when I click the Custom Field button next to the variant, it says "No custom fields found. For fields to appear here they must use the [v] marker."

What am I missing so far? I havent  gotten to the point of how to add the metafield data to my product page.

Thanks

Jason Shopify Expert freakdesign.com.au
Posts:
6741
August 07, 2015

Hey Ben,

My documentation efforts are less than rubbish - no secret there!

In Settings, with ShopifyFD, I've added a Metafield with the namespace "c_f", the key "Model" and the value of "[v]" for varient.

Where did you create this metafield? It should be added to the shop (at /admin/settings/general).

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
42
August 10, 2015
Yes. I created it there. What's next?
Posts:
2
August 25, 2015

Hi,

Can anyone help me with the below please....

I'm having a real problem trying to get one of my images to appear on my slideshow.

I have 5 images on my slideshow and only 4 are appearing as i changed the 5th. 

It appears in the preview of the admin section of my website but when i save changes it does not show on the live site.

The image is saved as a .png file

Any help will be really appreciated

Thanks

 

Jack 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited August 25, 2015

@Jack P - This thead is for the Custom Field tool - try making a new thread for the slideshow issue.

[edit] I see you have made another new thread

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Taz416 Member
Posts:
1
September 05, 2015

Great tool. A donation has been sent. ;-)

Am I missing something obvious? I was hoping for a checkbox option instead of a text input.

Can this be done?

Thanks

Jason Shopify Expert freakdesign.com.au
Posts:
6741
September 05, 2015

Am I missing something obvious? I was hoping for a checkbox option instead of a text input.

It's simple text input. A checkbox could be simulated by checking for "0" vs "1" for example, but I get that's not terribly user friendly. The checkbox request has come up before so it's something that I'd likely add into the new version. I can see the appeal in having it.

I've added it to the list.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
2
September 09, 2015

Thanks Jason  !

Twinkle Twinkle Little Star ABC SONGs kids songs - Little Star https://www.youtube.com/watch?v=_ise8MWTg5s
Posts:
1
September 25, 2015

Hi Jason,

First of all, thank you for developing such an amazing tool. :) Is there any way, I can limit custom fields to particular page? Small example would be helpful.

Thank you. :)

Jason Shopify Expert freakdesign.com.au
Posts:
6741
September 28, 2015

No. The fields can be limited to type (such as collection, page, etc) but not to a specific page. It's an interesting idea nevertheless.

If you need that level of fine control you may just find it easier to use ShopifyFD instead and just add the metafield as you need.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
10
October 03, 2015

Amazing tool!  Tip given!

Any change of putting the field edit boxes on the Variant edit page itself, instead of in the product listing? I have products will 100 variants, and it gets pretty messy.  Currently in both Safari and Chrome you can't "fold up" after you have "unfolded" the edit boxes for a variant.  I prefer to work on the dedicated variant edit page, which nicely lists all the variants on the left side of the page.  It would seem a wonderful and natural place to put the field edit boxes into the dedicated variant edit page.  Possible?

sean orfila Shopify Partner grizzlypoppy.com
Posts:
76
Last edited October 04, 2015

Apologies if this has been discussed. I setup a few custom metafields using your extension on a dev shop, when I move the theme file to the live admin, I need to re-create the fields in the live environment, yes?

EDIT: I just answered my own question - I belive it is YES. (If not, I'd love to hear about it)

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 04, 2015

Any change of putting the field edit boxes on the Variant edit page itself, instead of in the product listing?

Sure it possible but that's not how it works right now. Be open to adding such things if it was something that was a popular need.

 

when I move the theme file to the live admin, I need to re-create the fields in the live environmen

Metafields are not saved to the theme. The are saved to the resource (page, product, article, etc). So if you have setup the metafields in a dev store and are copying the theme to a different account you'll need to recreate the metafields.

If however, you're just talking about making a theme live in the same account, you'll be fine.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
sean orfila Shopify Partner grizzlypoppy.com
Posts:
76
Last edited October 07, 2015

Jason, your app is a God-send!! 

Our site has lots of collections. I'm seeing that the collection picker drop-down stops scrolling at about "M" and stops. Is there a limit to the collections available in the drop down?

Our simple work-a-round is to enter the collection handle, so the picker still works. Just looking to streamline a bit. 

 

 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 08, 2015

Our site has lots of collections. I'm seeing that the collection picker drop-down stops scrolling at about "M" and stops. Is there a limit to the collections available in the drop down?

The picker only grabs the first "page" of results - being 250 items. I assume you have more than 250 collections? I don't hear of people going beyond the 250 very often, but it's something that can be updated in the tool. Drawback is that it makes things a little bit slower in the loading process.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
October 09, 2015

Custom Fields no longer seems to be working for me. I've tried it on two computers, one running Mac OS X 10.11.0 and one running Max OS X 10.10.5, both using Safari, and no luck on either. Previously, it has worked like a charm for months.

Did something break in the last day on Shopify's end or with the javascript?

Any help would be much appreciated!

John

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 10, 2015

I've not pushed any updates in the last few days here so I'll fire up safari and see if that browser is causing issues. Apprecaite the heads up.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
Last edited October 10, 2015

I checked in Chrome as well. I don't think the javascript bookmarklet worked but the extension definitely still works. So at least I have a fallback!

Thanks for looking in to this!

John

Posts:
1
October 19, 2015

That's all because off shopify restrictions in http header forbiding any bad request except ones to google and some other websites.

Here is a quick way to bypass it:

Make a bookmarklet like 

javascript:(function()%7Bvar gaJs = document.createElement( 'script');
gaJs.type =  'text%2Fjavascript ';
gaJs.text =  '';
document.getElementsByTagName( 'head')%5B0%5D.appendChild(gaJs);%7D)();

where gaJs.text equals to Custom Fields js file converted to an inline string using something like http://www.howtocreate.co.uk/tutorials/jsexamples/syntax/prepareInline.html

I had to do it this way instead of using Chrome plugin because of CF restriction on the amount of fields shown from DB, so I have a little bit modified CF script.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 19, 2015

No need to do that. Shopify allows files directly from amazon s3 so I just need to adjust the bookmarklet url. It's a quick fix and I'll probably update the website later today.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
3
October 23, 2015

Jason,

Just checking, have you updated your bookmarklet URL? Custom Fields still isn't working for me and I just wanted to verify if you've made the change or not.

Thanks!

John

Jason Shopify Expert freakdesign.com.au
Posts:
6741
October 24, 2015

Yep, The bookmarklet code is updated (though any reference on github may be out of date). Drop me a line or DM on twitter if you're still stuck.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
11
November 12, 2015

Jason, can a metafield be displayed as a calendar date picker?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 12, 2015

It's technically possibly, but there's no code in place to make that happen. It's not the first time I've had some talk about that so it's my my radar to add ;)

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jordy Shopify Partner www.seidoshop.com
Posts:
87
Last edited November 18, 2015

Hi, 

We're still trying to find out a way to use that efficiently, but the potential is huge. 
FD and Custom fields are just awesome ! 

We still have some trouble finding the right way to name each fields to stay consistent site widethough :)

If we work out a way to use it as a standard feature, I promise we'll donate ! It worth the money. 

3 questions that will influence how we will use it : 

1. Any update on the RTE feature ? We're considering using it for product short description to display on collection pages (we already have that, but it's hardcoded with conditionnal liquid... ) 
We're gonna start with pure html, so, we're good anyway. But the RTE would be a bit more user friendly for our content managers. 

2. Any chance the chrome app would stay active when opening multiple tabs / reloading tabs ? That's, by far, the most frustrating thing with this tool. It would be some time saving to have it automaticaly loaded when 'opening in a new' tab !

3. Anway to conditionnaly display some fields depending on product type (or something else) ? Because the way we want to use suppose to have about 30 custom fields for products when only 3 or 4 applies to a specific product. It generate quite a lot of 'noise' for our content manager (it's manageable though, just a question).

Again, a huge THANK YOU for this tool. It's THE best tool for store customization. 

Keep up the amazing work. 

★Shopify tweaker★
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited November 18, 2015

Hey Jordy ;) 

Lots of "no" in this one sadly.

  1. The shopify scripts that drive their own RTE are not able to be re-used so whilst I could build in my own, it's not really something I want to do for the few users that need it. Something better left for custom builds of the tools.
  2. No. It's a simple browser extension that doesn't autoload. If the page is reloaded for any reason the script will be lost (since the code is no longer in the page). There are ways to force it to always be in the page but that would change the permission on the extension. Right now it requires zero permissions, which is cool.
  3. If you're getting down to need to filter what fields show per product you might be better off using ShopifyFD and just add as needed. I get that this is not as simple to enter in content since you need to add the namespace and key, but it would remove noise.

Appreciate the feedback, will definitly do what I can to resolve these.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jordy Shopify Partner www.seidoshop.com
Posts:
87
Last edited November 19, 2015

Thanks for the feedback. 

No problem. The RTE thing is kind of tricky, and hidding fiedls sounds complicated as well anyway (I mean, it would be a pain to set up each field for each product anyway... the only solution for that would be an app... but it's another story). 

Regarding the loading issue, I hear you and I appreciate your way. 
Do you think we could inject the code (both FD and CF) with a greasemoney script ? (we already have a bunch of stuff runing on the monkey, tricky with shopify, but we managed our way in).  

I'll put our IT guy on this, I guess it worth a try. 

Thanks again for the tools, amazing !

Edit : works like a charm with grease/tempermonkey - we're good !

★Shopify tweaker★
Posts:
3
November 27, 2015

Sorry if this has been answered already, I've been searching in the forum and I can't find the answer.

I am stuck adding the store level metafield. I know the guide says "You will need something to help create the metafields within Shopify. This document references the ShopifyFD tool, but you are able to use whatever metafield editor you choose." I haven't installed ShopifyFD, what I have installed is http://metafieldseditor.herokuapp.com/ and also custom fields. To be able to create the store field metafield, do I need to install ShopifyFD first? Is there any other free metafield editor that will allow me to create an store level metafield? If I do need to install ShopifyFD, is it compatible with the metafields editor that I already have in place?

Thanks so much, I am a little bit scared of installing ShopifyFD if it is not required to have custom fields work properly.

Posts:
3
November 27, 2015

What I mean is if ShopifyFD is the only free tool that will allow me to add a store level metafield. I am following the example in the Custom fields guide since what I need is exactly that, to add urls to the products to show videos and to have affiliate links.

Posts:
11
November 27, 2015

Hi Jason, silly question.

I have two custom fields on an Order.  I'm trying to put the liquid into an Order Printer template.

What am I doing wrong?

{{ order.metafields.c_f.Delivery_date }}
{{ order.metafields.c_f.Delivery_instructions }}

Jason Shopify Expert freakdesign.com.au
Posts:
6741
November 28, 2015
g
1
upvotes

@Silvia: I can't be sure if ShopifyFD is the only free tool that can save metafields to the shop. It's certainly possible that's the case. There's nothing stopping you from using ShopifyFD for adding just those initial metafields and jumping back to your app of choice for everything else. 

You're not installing ShopifyFD or Custom Fields to the store - only to be browser. Additionally neither of the tools run without a users direct action so there's not a lot of risk in added them to Chrome (or using in other browsers as a bookmarklet). A simple reload of a page will purge the scripts from th page.

@Jordan: Last time I checked metafields are not something you can grab on the order printer templates.

 

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
11
November 29, 2015

Jason -- I'm editing the liquid of the template.  Is there a reason why I couldn't grab it?

Jordy Shopify Partner www.seidoshop.com
Posts:
87
November 29, 2015

Yeah, I confirm, metafields still not available in order printer. 
It's just not in the app, so you can't pull any metafields from orderprinter. 

It's a shame, and we are even considering to develop our own order printer app... mainly to have access to metafields when printing orders. 

I mean, you can set up orders metafields, but you can't access them, so, unless you have your own app, it's useless.  In our case, it's a bit different, we'd like to pull products/variants metafields in order to be able to flag some products/variants for our embroidery/engraving/packaging staff... 

Jason, I must tip you for your tools ! We finaly moved all our settings in metafields, and it works wonderful. Wouldn't you support euros, dollars, or yens on your paypal account ? It's a shame to give paypal the conversion fees instead of you ^^

 

★Shopify tweaker★
Jordy Shopify Partner www.seidoshop.com
Posts:
87
Last edited November 29, 2015

Oh, by the way, what you can do if you need to create order statuses or stuff like that, you can simply add order hidden (display:none;) attributes in your cart template. 
Here : https://docs.shopify.com/manual/configuration/store-customization/page-specific/cart-page/ask-customer-for-more-information

You can even fill them with javascript if you want (let's say you have a metafield on the product page that determine its production time. You pull that in javascript and fill in the hidden attribute. You can then give the production time / shipping date directly in the order confirmation email, and have that displayed on your order printer templates. It saves you one email to the customer to indicate him your estimated shipping date). 

Then you can fill in with what you want, and you have access in customers templates as well as order printer and it's editable on shopify back end.

That's what we use for order production time, online tracking issues, etc. You can even access them in the customer contact email template, so even if it's a bit messy, you can set up templates that will save you a lot of time if you have to contact your customers at different steps of your order managment process. Just note that when you update an attribute in the order page (back end), you'll have to reload the page if you want the template email to take the change into account (it wasn't the case with shopify 1, but the new version that reloads in page without actually reloading the page, there are some glitches like this. One of my main complaint about shopify 2 actually). 

★Shopify tweaker★
Posts:
11
November 29, 2015

No, it's a different, much simpler need.  My client is a flower shop that needs to collect Delivery Information on the POS or phone orders (taken through the Create an Order pane).  There's no additional field anywhere to input this.  I thought that metafields were going to solve my problem, but we need to output the delivery info onto the packing invoice via Order Printer.  I'm left scratching my head what else I can do.

Jordy Shopify Partner www.seidoshop.com
Posts:
87
Last edited November 29, 2015

I don't know the POS system, we don't use it. It's really basic and needs far more work before it can be really usefull in my opinion. 

Assuming that orders taken with POS are displayed the same way on your admin panel (it will work with the order creation system for sure), and if you only need an order date, you can use tags like that :
tags = shippingDate_15/10/10, then in liquid, you break it to only keep the date, and you can display it. 

If you need to pull more details, like a string of words, it's not impossible with tags, but it would get really messy, and I don't see how you could do that...  Unless maybe with order notes, if POS accept notes... 

Unless I'm mistaken, shopify custom field won't work on POS, so you will need to input those additionnal information using a computer on shopify back end. 
This way, you might want to give a try to greasemonkey (or tampermoney on chrome) and try to pass the metafield from the order to order printer and populate a field in order printer with your script. (Not sure that's possible, we're using the monkey to tweak the back end, but I doubt you can pass through the information when the page reloads to display the order printer packing slip. Maybe by creating a cookie...). 

It's macgyverization though. Not sure you want to do that for a customer, as it will require quite a lot of maintenance over time. 

The only other solution is to code a custom app. Which is probably not in the budget.

★Shopify tweaker★
Posts:
2
November 29, 2015

Thank you.

http://whattogetmygirlfriendforchristmas.com/category/best-christmas-gifts/
Posts:
3
November 30, 2015

Thanks so much, I´ll do that!

 

Silvia

Posts:
11
November 30, 2015

Hi Jordy, thanks for this.  You say "if you only need an order date, you can use tags like that :
tags = shippingDate_15/10/10, then in liquid, you break it to only keep the date, and you can display it. "

How would I do this?  Can I bring tags into Order Printer?  I don't see an option to do this...

Jordy Shopify Partner www.seidoshop.com
Posts:
87
Last edited December 04, 2015
g
1
upvotes

Hi Jordan, 

I'm sorry, I didn't get notified of your email... 

Here you are : 

{% assign shippingday = 0 %} {% comment %}Days required for shipping {% endcomment %}
	{% for item in cart.items %}
      {% unless shippingday == -1 %}
          {% for tag in item.product.tags %}
            {% if tag contains "ShippingDate_var" %}
              {% assign shippingday = -1 %}
              {% break %}
            {% endif %}
            {% if tag contains "ShippingDate" %}
              {% assign tmpdate = tag | remove: "ShippingDate_" | plus: 0 %} {% comment %}plus 0 transform the string in integer so you can do maths on it{% endcomment %}
              {% if tmpdate > shippingday %}
                {% assign shippingday = tmpdate %}
              {% endif %}
            {% endif %}
          {% endfor %}
        {% endunless %}
	{% endfor %}

We used to use this in the shopping cart. 
So, the code will look a little different in order printer, since you will have to loop the order content, not the cart content. But the idea is the same. 
Also, you probably won't need the "ShippingDate_var" part, as we used it to display a message saying the shipping date is variable. 

Tags must be added to each order on the order managment page. And you can pull them in order printer.

 

By the way, I do have a question for Jason. 

At the moment, there is no filter for shop level metafield. Could that be implemented ?
We're using FD, we don't really need it, but I think it would be useful for devs that only gives custom field to their customers when they need to apply a value to the whole shop (for example, we are using a shop level metafield to set up our holidays. So, when we make calculations on order production times, we can include the holiday period in it). 

Thanks ! 
 

★Shopify tweaker★
Posts:
2
December 15, 2015

How to add or create custome field for store ? Any Suggestion. Attached screenshot.

Can you share any tutorial on adding custom fields for beginners.

 

 

Screen shot 2015 12 15 at 12.47.22 pm thumb
Jason Shopify Expert freakdesign.com.au
Posts:
6741
December 15, 2015

^ Would be happy to ;)

It will however need to wait until I've for a few free moments to knock something out. It's been on my todo list for a while so it's certainly not forgotten.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
44
December 30, 2015

Wouldn't custom fields be an excellent opportunity/solution to integrate mulit-language-support?

Posts:
2
January 22, 2016

How can I loop through the metafields and pull all the values from a page.

For example, I added single metafield values to two pages. I want to loop through them and pull all of these values to homepage.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
January 23, 2016

If you need specific help with metafields, rather than the custom fields tool it will be bet that you create a new thread. That said, the metafield for a page could be grabbed like so:

{{ pages.a-page-handle.metafields.your-namespace.your-key }}

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jason Shopify Expert freakdesign.com.au
Posts:
6741
February 21, 2016

A minor update was released recently with a few more custom field types. These are:

  • Date - [_d]
  • Colour - [_co]
  • Number - [n]

The docs are yet to be updated, but these could be handy. Very few browsers support the HTML5 colour picker so for now this will be a Chrome (or Opera) only feature.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jordy Shopify Partner www.seidoshop.com
Posts:
87
February 21, 2016

A date type! Awesome Jason, thank you very much :)

★Shopify tweaker★
Posts:
2
12 months ago

Can any body tell me how i can reduce the font size at product page using venture theme? 
The product Title is very much big which seams odd . Please help 

Posts:
1
11 months ago

Hi Jason, 

I'm sure you've been asked this a milion times, but I'm looking for a way to import metafield data.  You mentioned you have code for your own use.  Are you able to share this?  Or is there a file where metafields are stored that we can edit manually?

Thanks!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
11 months ago

Hey Rahul,

There is another browser tool I am working on that does allow import and export functionality but it's not something ready for prime time yet. Check out some of the apps in the App Store as some of those may offer that feature. You could also look at using the API directly if you've got those dev skils on hand.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

Hi Jason, 

I admit that I would love that tool as well. 
We're working on a bunch of python code to do that... but it's quite messy and very time consuming. 
(One shopify dev side weakness is the lack of duplicating tools actually... Being able to duplicate a store easily would be really useful). 

Anyway, another question for you if you don't mind : Any idea when you will bring back the shipping fee function ? 

Took me a whole day to reset up the fees on one of our stores, I'm kind of waiting for the option to be back in FD to do the other stores... Just to have an idea if it's like for very soon, or a few months.

Again, thank you very much for everything. FD and CF are just the best "backend" dev tools available for Shopify.

Jordy

★Shopify tweaker★
Jason Shopify Expert freakdesign.com.au
Posts:
6741
11 months ago

@Jordy - Shipping rates copy and paste is back in ShopiyFD, though it will skip carrier based rates (for now). Unless of course something has exploded that needs my attention.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

@Jason, thank you for the very fast answer. 

My bad actually, my question is messed up. I was thinking about the function that copie all the rates (to paste them in another website).

Or did I just dreamt this function existed ? I'm not even sure now... 

★Shopify tweaker★
Posts:
2
11 months ago

Hi Jason - love the ShopifyFD and Custom Fields apps... saved me a ton of work. I'm sure you've been asked this a million times, but will the [_p] option be availible any time soon? I'd really love to be able to relate products to one another like this!

cheers

Scott

Posts:
7
11 months ago
g
2
upvotes

Jason,

The new datepicker is fantastic and very usefull for my client situation. I wish, however, that the value it saved was in Shopify's standard timecode format, so that I could filter it like any other date in shopify (using Xporter).

By standard shopify timecode format, I mean this (ISO 8601):

2016-03-23T15:25:17-05:00

If I could get my hands on the source, unminified js, I could do this myself. If you have an interest in protecting your code as your intellectual property, I can agree to not use the source for anything else, and to not release it to anyone else.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
11 months ago

The datepicker is nothing fancy to say the least - just a plain ol HTML5 date field. There's not going to be formatting control here unless you're throwing more JS into the mix. If you want to build that in - got for it. As for an unmified version - shoot me an email.

This version of Custom Fields is about to be superseded in any case - there's a new version in production that's cutting down on dependencies and making the code a whole lot less of a brain dump, and a lot more practical for user contribs.

@Scott - The product picker will be included in the new version.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
2
Last edited 11 months ago

@Jason - good to hear it! May I ask when that release will be? I'm working on a project with a March 31st deadline... its no problem if its after that (I've built what I need using [_t] and some filtering of handles), but is nice to know there's something coming soon...

cheers for all your good work!

S

Posts:
7
Last edited 11 months ago

Gentlemen/women,

Jason has offered to provide the source code, such that I could help maintain, or fork another version to maintain, and add features to this very clever hack.

But before I take his code, I wanted to present to the community an alternative option to this tool I am considering instead of supporting his open source solution. And because I have no desire to play out opportunistic capitalism, I present this as an open question for the community to help decide, and put let my intentions be known..

To the point, I could make an embedded app providing basically the same features and more, available on the app store. My reasons for considering this are a few:

1. Jason's current, very clever and useful, bookmarklet is a hack, and is subject to break if / when Shopify upgrades it's front-end. When the last upgrade happened, I think it was down for a day before it got fixed. But as a freely available hack, there isn't the assurance that someone is paid to keep it up. Jason did not offer it as a recommended client-facing solution, so I don't bomb the github issues section or this forum with complaints if it were to break. Neither would I ask him to support something he is not paid to do, if it wasn't his free choice to do so.

2. I am using this with a client, client-facing, because the tool is so abundantly useful. I think everyone on this forum is probably aware of the potential that custom-fields provides, and have directions they want to take it.. If I built a reasonably priced app alternative, with my own code, not stealing any of his, this is something I could professionally support. Taking custom fields into the realm of a stable, client-facing solution. 

3. Using an embedded app would allow for simple settings configuration, where developers could specify all sorts of validation features. You could set a predefined list of options for the client to choose from, etc.

4. The only drawback is that to trigger it, it would to be chosen from the [...] menu on the top right of any resource page your trying to use them with. Using Embedded App SDK, it would maintain the shopify admin interface, and the content of the page could be designed to look like something akin to the product variant subpage, with breadcrumbs and other things to return to editing the primary product page. Jason's CustomField browser extension or bookmarklet automatically re-appear on the front page themselves after it is clicked once. A feeling of integration into the dashboard I could not match with the Embedded App SDK, so that is a definite downside.

If this seems worthwhile, then I would start building it very soon, again, not stealing any of Jason's code (it would be in ROR rather than JS anyway). Or, I could simply keep working with Jason's hack, and if he still is OK with offering the source code, it could try to help maintain, and add features to it.

All thoughts are open.

Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

I am not sure I understand exactly the project, but there are already a few apps on the app store (some of them are free) that already do that... 
A better one would be nice, but a good app suppose a lot of work, and it would probably target a very few number of people (those who know how to use metafields can use Jason's tool or an app for free, and the other won't bother tweaking metafields if they don't know what they can do with them). 

Another note is that, even for a paid app, the user can't be sure it will still be around in a year or two. 
I've seen plenty of app disappear the last few years, because companies/people behind them just stop what they were doing. 
This is why here, we rely on no app. We don't use a single app we couldn't replace with something else (or be back to a less convenient way of doing the same thing).  Imagine you have a product builder, you build all your shop around it, and what when the server is down ? What when the company maintaining it decide to stop the app or goes bankrupt ?

My opinion is that apps are good for enhancing existing functionalities, but shouldn't be used to trick Shopify in a way that cannot be done/maintained with existing shopify tools (or with a fair number alternative apps that does the exact same thing, like for metafields). 

Jason's tool is, by far, the easiest to use. I'm even surprised that there are not more people developing js snippets to enhance Shopify dashboard (we do, we have a few very custom stuff we use to reorganize some parts of the admin panel to improve our workflow, it's too custom and not maintained well enough to be share with the community though).  

Anyway, unless you have a fairly good/new idea to improve existing apps, I don't see the point in creating a new one.

★Shopify tweaker★
Cam Shopify Expert elkfox.com
Posts:
144
Last edited 11 months ago

Sorry to be so brutally honest, but that sounds like a terrible idea to me. There are already apps for that, and if you look at the information re submitting new apps, you will find it clearly stated that no more metafields apps will be accepted.

The strength of the bookmarklet method is very clear, and a very different thing to offering an app. If you want to make something that is paid, do something like make a browser fork that has the metafields functionality built in that you could sell to both developers and store owners so that they can work with their metafields in a more solid and focussed way. Or maybe I will ;)

-- EDIT --

...or even just a cross-browser hosted applet that shipped in the form of native browser plugins. I would pay a small fee for that. If you don't make it, I may well decide to.

Designer, Developer, Director, Producer | Head fox at Elkfox | Owner at Green Hosting™ | Compiler of the 'Shopify Theme Framework'
CarlowSEO Shopify Expert www.carlowseo.com
Posts:
489
11 months ago

I would have to agree. the benefit of the app is not just what it provides in terms of features but the ease of use. Store owners (parden my honestty) are generally lazy. They do not want to do much else.

An even better solution (Seeing the benefit of this app and this thread is still open after 2 years... goes to show Shopify that this feature is needed... Look at plugins across many other solutions... you can easily insert custom fields onto the screen... where the user edits the content... Perhaps the real solution is to push shopify to solve the shortcomming they have ignored for years...

So if you are going to sell an app... it better put the fields right in the users face.. not a separate screen... not a button... but a real enhancement to editing products.

Trevor www.carlowseo.com
Posts:
7
11 months ago

Let me put this in a different way. I want to extend Custom Fields to include more validation. As @CarlowSEO suggested, Shopify should implement a solid custom field feature, but they haven't. In Wordpress, the ability to define custom post types means you can tailor a dashboard to a clients needs. Jason created this. I am using this amazing tool for a very large ecommerce store where employees are entering locations in a warehouse by hand, and if they type them incorrectly, then things go sour.  After Jason suggested offering the source code, I had the thought, maybe I should start from scratch instead of adding features to his. Yes, there are plenty of Metafield apps out there, both paid and free, but everything I have tried leaves the Shopify dashboard entirely, has no validation or ability to set values by datepicker, checkbox, product chooser, etc. So I have the option, which I am putting to the community. I can add pre-defined selectboxes, I can create validation to ensure only letters, or numbers, or email addresses, etc. are entered by a dumb lazy client. I can do this to Jason's tool, and offer it up, maybe help support it, as an open-source style thing. Or I can build an embedded app. The pros of an embedded app is that they are not subject to breaking whenever Shopify updates their front-end. They work within a framework Shopify has defined for extending functionality. The one con of an embedded app is that they cannot be on the main product screen. But they can be a click away, maintaining Shopify's dashboard, and have link-backs to the main product page as if it were a sub-page like product variants. All brutal honesty accepted, but the question is, how do you want your custom field?

Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

Creating an app doing that for a customer that needs it, yes sure. 

But having your app on the app store is another story. You would need a set up panel that allows the user to set up his own validations/fields etc. 
Unfortunately, 99% of Shopify merchant are not able to do that, it's too complicated, unless you get a very well designed and very simple set up config.
And even then, how many merchants will be interested by the functionalities AND able to use the tool ? 

We are currently working on our end on something that will work as an external app to manage orders, discounts, customer account (pretty much everything but the product/collections and theme). It will create a lot of stuff, with customers tools for internal use (order states for example) and store enhancement (order states displayed on the customer account for example). 
We asked ourselves if that kind of tool could be sold as an app, but obviously not. It's too complicated and too specific. 

What would be interesting is a company offering custom back end tool AND adapted theme so both work together to offer a far more powerful Shopify back AND front end. But that's a very different business model that what is traditionnaly done by shopify partners.

★Shopify tweaker★
Cam Shopify Expert elkfox.com
Posts:
144
11 months ago

@Jordy Interestingly, we have been playing around with that for a while (mixing front end and back end). While it's a fun expereiment, I feel it is a little too un-Shopify. It blurs the line a little too much. We will be releasing something for a very specific purpose that has elements that work that way. But going into detail about that would be off-topic.

Designer, Developer, Director, Producer | Head fox at Elkfox | Owner at Green Hosting™ | Compiler of the 'Shopify Theme Framework'
Posts:
996
11 months ago

@Colin Brogan 

I am considering instead of supporting his open source solution

Don't, enough generic metafield editors are on the app store.

Cam pointed out shopify is not accepting new ones, but i too thought that was specifically metatag editors not metafields.

 The sheer amount of polish,elegance,and innovation you'd have to acheive to get a reversal on that decision, if it is metafields now too, is the type of estimate that ruins companies with big R&D budgets.

Either way to sum up: market saturation.

Come in from the angle that will always be there; marketing it as a bespoke product tailored to the customers needs. All the metaprogramming in the world will not account for a specific use case's validation concerns that also doesn't require the end-user to speak native regex.

 

Jason's tool is, by far, the easiest to use. I'm even surprised that there are not more people developing js snippets to enhance Shopify dashboard (we do, we have a few very custom stuff we use to reorganize some parts of the admin panel to improve our workflow, it's too custom and not maintained well enough to be share with the community though).  

That last sentence-fragment is the solution to the 2nd sentences start. Code rot is a very real cost and open source maturity is not easy.

4. The only drawback is that to trigger it, it would to be chosen from the [...] menu

That is not a downside that is DOA. Fix that from the beginning or no point.

 

 

 

 

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Posts:
7
11 months ago

@Jordy

I see your point. Having metafields that manipulate some aspect of the website or store data is already specialized enough to exclude the majority of Shopify merchants. Then a subset of those people might want client-friendly interfaces on those metafields, limiting the pool further. I suppose the community of those interested in custom fields is small. Regardless, I am not trying to make a big buck. Jason is already offering this for free. I have a client that is paying me to provide these needs, and if I am able to help progress the development of custom fields in a way parrallel to Wordpress's custom post types, I'd like to share it. Furthermore, the simple, well-designed settings panel to define the validation is doable on my end, for sure. Or, my other thought is to extend Jason's markup. For instance [_s?cotton=Cotton&wool=Wool&pu_leather=Faux Leather] could show a selectbox with 3 client-friendly visible options "Cotton", "Wool", and "Faux Leather", where the actually stored metafield value is something more machine-code friendly ("cotton","wool","pu_leather). That is only the tip of the iceburg of what could be done. Is this share worthy? Or maybe I should give Jason his thread back, and stop peddling my own ideas.

Posts:
996
11 months ago

@Jordy 

I am not sure I understand exactly the project, but there are already a few apps on the app store (some of them are free) that already do that.

It lets custom fields be placed directly on pages like /products for example store owner can edit "metafield-related-product" right in the page no redirects etc., generally with develper preseting it all. 

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Cam Shopify Expert elkfox.com
Posts:
144
Last edited 11 months ago

I may well be wrong about the "metafields" vs "metatags" thing. It looks like that clause has been removed from the brand-spanking-new info post-new-announcements anyway. But what you are talking about doesn't seem much different from this, or any of the many other metafield editors that already exist.

Designer, Developer, Director, Producer | Head fox at Elkfox | Owner at Green Hosting™ | Compiler of the 'Shopify Theme Framework'
Jason Shopify Expert freakdesign.com.au
Posts:
6741
11 months ago
g
1
upvotes

Just as an FYI and to be clear - I wouldn't be looking to have contribs to the current version of CF. It's one thing if someone wants to take the source code and build some private custom app for their own specific needs, but I'd not want to see that built upon or merged into a new tool. If you want to craft a new version to throw into the wild - don't build it from this source.

A new version is already in development (along with ShopifyFD) that will supersede this one. It will be a much better base for user contribs, and be geared for future / upcoming admin updates.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
996
11 months ago

 @Colin Brogan

but the question is, how do you want your custom field?

in-situ

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

@Paul: I got that. What I don't see is how different would be Colin's project from either CF or other apps. 

@Cam: It depends on what you did (and I'd really like to know, I'm quite curious), but I really feel that intricating metafields with back and front end devs is a very good way to create really handy custom tools. 
A lot of apps are injecting js like code into pages to modify them after it loaded (and they do that because they don't want to have to set up their app on every shop), but it's dirty, not seo friendly, completely reliant on the app server, slow, etc. 
By using metafield, you can achieve the same thing, faster (using shopify servers power instead of browsers), more seo-friendly, and, of course, stable
For example, we now use Jason's FD and CF to set up a "production time" metafield on each product. We pull those meta on the front end to display the production time (we have a lot of features, like increment if we put +3 instead of 3 in the metafield) and a shipping estimation date (that takes shop holidays, week ends, national holidays into account). Then we save this date in an order attribute so it's pass with the order to the back end. 
From there, we are currently developping an app to manage more easily (Jason CF is good, but having bulk updates would be easier) the production times on our end, then another app (order managment) that amongst a lot of other things, flag orders that are late or about to be late (using the attributes as a reference date, then adding metafields to the order to sort it). 

So yes, you can push things very far with metafields, but it's sometimes really necessary. It allows to set up very easily a few features that shopify should have (because most non shopify stores have it): 
> Production time / shipping date
> Discount per product/collection handler (with auto tagging products, including discount end date, etc.)
> Order managment with order statuses (including late orders, returns, etc. - All that displayed withing the front end customer account, as in Amazon for example). 
> etc. 

 

@Jason : sorry for polluting your thread.... :/

★Shopify tweaker★
Posts:
996
Last edited 11 months ago

@Jason

A new version .... will supersede this one. It will be a much better base for user contribs, and be geared for future / upcoming admin updates.

any hint on license type? 

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Posts:
7
Last edited 11 months ago

@Cam

But what you are talking about doesn't seem much different from this

Wow, that is exactly it. You just saved me from a wasted endeavor

@Jason

Sorry, Jason. I think I took some liberties in assumption here. I will work around what you already have for my own private use.

Suzy Shopify Partner
Posts:
7
11 months ago
g
1
upvotes

Hi Jason,  thank you for this fabulous app.

I have added custom fields on the store settings page using ShopiyFD, for products using the [p] marker and variants using the [v] marker.  All were working wonderfully until the last day or so.

Whilst the product specific custom fields are still loading in the product admin screen using the Shopify Custom Fields Chrome extension, the variant specific custom fields are no longer loading.  Can you tell me if a recent update has disabled the [v] marker or maybe just broken it?  

I have added the markers to the 'Value' field as per your instructions doc and have used 'custom_fields' rather than 'c_f' for the Namespace.  Do I now need to load the variant [v] marker in a different field to make it work?

I would be grateful for any advice on how to get the variant custom fields loading again.

Posts:
3
11 months ago

Having the same issue as Suzy here. Has Shopify rolled out changes that have affected the extension?

Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

Same here, with both an old version of the script and the chrome app. 
We noticed a few other changes in the admin very recently so it's very likely a change in Shopify.

★Shopify tweaker★
Posts:
996
11 months ago

What would help here is testing suite against the admin to know of changes as they happen, i've only slightly looked into this. So if anyone knows of a project doing that speak up that'll help with projects like this in keeping pace with unannounced changes to shopify's admin.

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

That's quite an issue with Shopify, many changes are unannouced and breaks a lot of things. 

We were considering having a test suite for a while, but since changes are not released platform wide but in multiple steps (in an order we don't really understand... sometimes our old shops gets the new features first, sometimes it's the new ones...), it's a lot of work for a tool that wouldn't be very reliable.

★Shopify tweaker★
Posts:
656
11 months ago

Shopify use a process of continuous integration and deploy changes many times daily. Keeping up is nigh impossible unless you are equally badass. Jason has done an incredible job thus far and they have recongized his talents. We should be so worthy!

I'm a million different people
Posts:
656
11 months ago

At Shopify, Shipit deploys over 200 projects (including itself) at the press of a button - something we do several hundred times daily.

I'm a million different people
Jordy Shopify Partner www.seidoshop.com
Posts:
87
11 months ago

I don't believe they work without versioning, and I really think that for a plateform that relies that much on third party apps/developpers/designers, they should have a change log updated in real time for certain type of changes. That wouldn't help preventing something from breaking, but that would help to locate precisely what change broke it. And they also should annunce some major changes a little before the update. 

Nothing to do with Jason's amazing work. (He's faster than most of us at fixing things when Shopify breaks everything anyway ^^)

★Shopify tweaker★
Posts:
996
11 months ago

 many changes are unannouced 

A call for an ecosystem|platform changelog has been around for awhile, but has never gotten enough steam.

having a test suite for a while, but since changes are not released platform wide but in multiple steps

Overkill but something started,besides seaff admin, just to know when the admin changes, ex: ".header .header__secondary-actions:first", obsoleting a hook; gives breathing room and speeds debugging. After that others will get inspired for the api,pos,etc.; But all ecompassing suite no no.

several hundred times daily.

That includes everything from typos to line pruning, across all channels (pos,api,gateways,etc) which is the biggest factor in the non-existance of a global changelog, not to mention the silent a/b testing.

they should have a change log updated in real time for certain type of changes

 But until they do i decided to chew this a bit more: '[RFC] - Shopify admin changes testing tool' post in the partners forum.

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Jason Shopify Expert freakdesign.com.au
Posts:
6741
11 months ago

@Suzy: This should be fixed:
https://github.com/freakdesign/shopify-custom-fields/issues/30

@Colin - no problem at all. As long as you've got a solution, I'm happy.

@Jordy - Shoot me an email with your bulk metafield requirements. I might have something you could test with.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Suzy Shopify Partner
Posts:
7
11 months ago

Hi Jason,

Many thanks for the quick reply.  That seems to have fixed it.

Looking forward to the [_p] marker being implemented for the product picker.  That will save a lot of time copying product handles.

Joey English Member
Posts:
5
10 months ago

Hey Jason, thanks for remaining active in this thread. Been using ShopifyFD/Custom Fields for quite some time now to great effect. Unfortunately on a recent project, we're finding that Custom Fields aren't loading when creating new products, and that you have to actually save the product first before it loads on page reload. This also happens frequently when editing a product (the custom fields do not display at all, no matter how many times the tool is loaded, or the page is refreshed). Any thoughts on what might be causing this?

Joey English Member
Posts:
5
10 months ago

Also, as a separate aside here, is it possible to export custom field data in any way? Say for, 500+ products?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited 10 months ago

Hey Joey,

This is intentional, and not a bug. Metafields are saved to the resource (product, collection, page, etc) itself. This means the resource must be available before we push metafields to it. If we're using products as an example, you would first need to save the product for the first time to create it, then the tools will be able to do their thing. Until then, there's no actual product to save anything to.

Hopefully that makes some sense, and I'm not just rambling!

As for the follow up question - there's not export built into either tool (but I do have working code that does this). I am curious however. What format are you hoping to export it to? How would an export help you?

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Joey English Member
Posts:
5
Last edited 10 months ago

Thanks for the reply, Jason. 

My theory is that I never recognized this before because I'm almost always working on a pre-existing site as I rarely take on new site builds due to my resource limitations (i.e., my day job as a CTO hampers my ability to take on larger projects). 

Re: the export, I don't think I'm communicating this need well. What I would like to do is export a full data dump, with the custom fields as their own columns; this would, ostensibly, help us manage our product inventory and easily merge in data from vendors that are using those custom fields. For instance, on a Wedding Band, I've set up several fields for size, thickness, polish type, metal type, etc. These are not variants, hence we're using custom fields to enter the data and display that data to the user. But when we do a product import (of 500+ items), we have to manually go into each product and add these details, which you can imagine is extremely time-consuming. Hopefully this makes more sense? 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited 10 months ago

The Product CSV file that I assume you're using for import does support metafields - but only very specific ones. These don't appy to this conversation.

To automate a bulk update you'd still need to use the API (or an app / tool) to add or update those metafields. If you are regularly updating metafields you really might want to look at the API and build out a custom tool.

https://docs.shopify.com/api/reference/metafield

Also check the store just in case there's an app that can help.

Shopify's product bulk editor also has some support for metafields so this might give you some basic spreadsheet style editing for faster updates.
https://www.shopify.com/partners/blog/53573123-secrets-of-the-shopify-bulk-editor

The Custom Fields extension has no current import and export feature. It's unlikely that I'll add it to this version, but there'd be more chance for v2 since it's a bit more flexible in the setup. I've got code that does export product data with metafields to a json file (used in another extension) so I suppose if the need for an export feature was high, I could merge those two together.

 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Joey English Member
Posts:
5
10 months ago

Thanks, Jason. I assumed that was the logical next step as I hadn't found a better solution elsewhere. Appreciate the replies, and the amazing work you've done. Here's to v2!

Posts:
5
10 months ago

I'm curious to hear what everyone's thoughts are on a new app we developed that serves the same purpose. https://apps.shopify.com/custom-fields-2

There are legitimate pros and cons to the approach in this thread compared to our new Custom Fields app.

New App Pros: It's easier for a store owner to create new fields of various types like file uploads, images, checkboxes, radios, whatever. Keeps itself updated to changes you make and fields you add, requires only a single line include statement or can be used for theme customizations.

New App Cons: paid app, administered from a separate site, no chrome extension.

Hopefully this doesn't ruffle any feathers posting here, I'm genuinely curious what people's thoughts are on it.  

 

Posts:
656
Last edited 10 months ago

There are other apps that provide similar:
https://apps.shopify.com/copycat

— I use both.

I'm a million different people
Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited 10 months ago

The new version of Custom Fields has a far greater wealth of field type control and how they are set, but it won't ever have a file upload (unless a files API is released) and will likely still lean towards simple use. I'm also on the fence whether I add RTE support in as that adds a lot of fat to the script.

No ruffled feathers. Options are a good thing in metafield land. For more in depth conversions on your app you'll be better off making a new thread. This one is crazy long as it is without adding another talking point into the mix.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5
10 months ago

File upload is a sticky one. Not having that feature in a Chrome plugin makes sense to me. We wouldn't build it into it either if projects were reversed. Images and files were one of the bigger features we added to the app. Storage is on Amazon S3 and uses the same image editor that Shopify does. It's an expense for us to store and serve everyone's files but we think it makes sense for our project.

Good call on making a new thread. I'll do that soon and cross link.

We've already started referring people to your plugin if their requirements are a better fit for it. At some point I'll probably do an impartial comparison matrix of different metafields apps and tools. I'm still finding options out there and researching what other apps and tools can/can't do. 

 

 

 

 

Blake Enloe Shopify Partner www.shopify.com
Posts:
62
10 months ago

Hey Jason,

If I have existing metafields on products, is there a way to update them via the standard item import csv? e.g. adding columns for each existing metafield field.

Thanks!

Blake

Shopify Plus Developer | Get in touch: blakewenloe@yahoo.com
Jason Shopify Expert freakdesign.com.au
Posts:
6741
10 months ago

No. You'll either need to use the API, an app (that uses the API), or manually via the Bulk Product Editor. I've considered adding some sort of bulk upload support into Custom Fields or ShopifyFD but the call for it has been super low. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
5
10 months ago

Blake, you can edit metafields in bulk using some URL trickery right on Shopify but it's clunky at best.  

Our Custom Fields app has the bulk update via CSV feature, but you'd have to migrate your data to the app's metafield namespace to use it (you could still use ShopifyFD after migrating though).  

Stender Member
Posts:
4
Last edited 9 months ago

Hey Jason - Awesome work.
I've been reading through the PDF for variables etc - but I can't find a variable for boolean values, is this not possible? since you can save as integer, it should be possible to create a checkbox with a boolean as well right? 

I am interested in, when creating a collection, you can go into that collection and set a boolean so the user can choose to use a custom grid or not on that specific collection. I could do this through settings, and adding the collections manually, but I want to future prove it, and not have 1000 checkboxes in the settings. 
And i think that checkboxes would open up a world of possibilities for developers.
(EDIT - I see now, that you have assigned yourself the assignment of checkboxes on GitHub - do you have an update for the status of it? is it something we can expect in the near future, or shoulld I begin to work with 0's and 1's?)

Hope you understand my question - 
Jesper J.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
9 months ago

Stick with the 0's and 1's. 

At the moment Custom Fields (along with ShopifyFD) are going through some architectural updates as they move into their v2. For CF, I'm currently working on a more comprehensive way to setup the fields in the first place. It will switch from using many setup metafields to using a single 'settings' metafield. What's important here is that it does include the boolean option. No timelines - since this is a sideproject - but that part exists in the code.

I'd consider adding something similar into the existing version if this was a must have. Just have to spend that free time wisely!

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Stender Member
Posts:
4
9 months ago

Thank you for the reply - I am sure that V2 will be awesome. Sounds like it will be more comprehensive as well as userfriendly - 
well it is not really a "must-have" in the current version, I just thought that it would be more userfriendly for store-owners, and I didn't wan't to start setting everything up with 0's and 1's if it was one the way. 

regarding V2 - how sure is it, that it will be completly compatible with V1? if we ever upgrade, and the arcitecture is getting a huge makeover, will we have to remake the current "custom fields"? or will you do like you did last time, and manipulate the namespace (custom_field -> c_f) -> (custom_field -> c_f -> settings)? 

Keep up the good work
- Jesper J

Jason Shopify Expert freakdesign.com.au
Posts:
6741
9 months ago
g
1
upvotes

It will be backwards compatible. If you add settings, it will ignore old fields from that point on. If there's not any settings but existing CF setup metafields, those will be converted to a temp json settings file for that session. This would let us add an option that would let a user upgrade to the new settings format. No need to worry about editing the json either as there'll be an editor UI provided. 

The actual metafields on the objects (products, pages, etc) won't be effected at all. 

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Stender Member
Posts:
4
9 months ago

Awesome - I will keep on working, they way I have been then - Thank you for the clarifications, and I am looking forward to be working more in depth with your plugins.

Posts:
996
9 months ago
g
1
upvotes

Stender  said

I am interested in, when creating a collection, you can go into that collection and set a boolean so the user can choose to use a custom grid or not on that specific collection. I could do this through settings, and adding the collections manually, but I want to future prove it, and not have 1000 checkboxes in the settings. 

What is wrong with using the built in alt. template functionality ?

 https://help.shopify.com/themes/customization/store/create-alternate-templates this is a standard approach for views, cuts code, doesn't add UI noise to the admin, and sets merchant education to only having to be via shopify docs.

An aside, Using booleans for feature flags, while convenient when making a MVP, in production tend to become maintenance problems, especially with how shopify handles "truth". Example setting a mf to 0(zero) or 'false' then using: {% if mf.c_f.usegridview %} will bite you, instead use explicit string matching to avoid any type of number|false-positive conditions and make code clearer.

And i think that checkboxes would open up a world of possibilities for developers.

Better to just be able to pass a template stored in a mf. FD,and others should avoid the slippery slope of discrete UI form elements, the current run of object|UI markers is pretty focused and the ones in development serve admin UI lackings(product picker).

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
Stender Member
Posts:
4
9 months ago

Well - You have just set me back a day of work, and I thank you for it.
I see your points, and have begun reversing, to do just so,
It accomplish excactly what I wanted.

"Sometimes your brains consists mainly of farts"

Thank you Paul.

Posts:
996
9 months ago

Sometimes your brains consists mainly of farts

nah, shopifys reductive nature just gives us a habit of over engineering things to fix perceived holes.

Remember this is controllable on the client-side to with the url param: ?view=template_suffix

Modification &amp; Repair of Themes&amp;settings, CSS,javascript,(coming soon apps) http://www.krop.com/paulnewton/ paull.newton+shopifyforum@gmail.com
joaomamede Member
Posts:
1
8 months ago

Is there any way of adding a kind of "repeatable" field.
Say I want to add an "n" number of images to a page/product, would that be possible without having to hardcode/set the exact number of custom fields?
 

Jordy Shopify Partner www.seidoshop.com
Posts:
87
Last edited 8 months ago

You don't need multiple fields, one is enough. 
Set it as a textarea so you have more space. 
Put a link on each line ending with a easily targatable character (we us ; ), and split it in liquid. 

Metafield content

url1.com;
url2.com;
url3.com;

Liquid

<!-- Create urls array by splitting metafields content--->
{% assign url = product.metafields.extraurls.urls| split: ";" %}
{% for ulr in urls %}
 {{ url }} <br>
{% endfor %}

Output

url1.com
url2.com
url3.com

 

You can remove, append, assign a value to each url, etc.
With some complex liquid, you can create quite a complex set of data. 

 

★Shopify tweaker★
Posts:
2
8 months ago

Thank you for the article very interesting and exciting, I will learn

Electrikfreak Shopify Partner
Posts:
4
8 months ago

Jason,

Thanks so much for this tool! Really great idea!!!

Really loking forward to the new version, Specially the product picker.

Do you know what day you will be realising the new version? 

Thanks!

 

 

Luis Martins Shopify Partner
Posts:
5
7 months ago

I've been using this up until recently without major problems but recently I can't get it to work anymore, including on previous sites where it was working.

Here's what Im noticing:

  • Custom Fields editor box won't load into Shop Preferences
  • When creating a custom field with any namespace, including the default c_f, those fields wont show up on any edit screen. I've tried with and without resctriction markers ([p], [c], etc.) but no luck.

Where there any recent updates to the browser extension that might explain this?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
7 months ago

Hey Luis,

  1. The Custom Field tool never loaded anything on the Shop Preferences page in the admin. Perhaps you're thinking of ShopifyFD
  2. No updates have been made to the tool in a while. Generally if there's things not loaded it's more to do with changes made on Shopify side for the Admin layout.

I tried loading the tool whilst editing a product and saw fields aok so would be curious to see the steps you're taking here.

If you've got a github accout, issues can be posted here:
https://github.com/freakdesign/shopify-custom-fields/issues/new

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mfk Member
Posts:
52
7 months ago

anyone knows if ill lose custom fields data if i push a development store (partners account) live to a paid account with a client?

been using this 'plugin' for a while, but its my first time using it on a development store.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
7 months ago
g
1
upvotes

Metafield data is saved as a resource on the object (like a product) so nothing in that respect changes when you upgrade the account. It all will be kept as is.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mfk Member
Posts:
52
7 months ago

missed your reply. thanks!

Posts:
6
6 months ago

Hey There!

Trying to get this set up for a client. I am creating a metafield with ShopifyFD, the example one per the custom fields help document. When I enable Custom Fields via the chrome extension, I am getting... "No custom fields found."

My metafield seems to be fine as I tested it by spitting out 
{{ product.metafields.c_f.video_url }}
into the product.liquid and it correctly spits out the string "Some instructions on what to do here..."

I'm wondering what to do here, perhaps I'm using the extension at a time when its in between updates, but perhaps I missed a step? (more likely) Thanks!

Jason Shopify Expert freakdesign.com.au
Posts:
6741
6 months ago

Hey ActualKeith,

See if this link helps clear up anything with the set up process.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
6
6 months ago

Jason thanks for responding so quick! Can't say i'm seeing the gifs on this link. I tried to whitelist a namesapce and tried the basic setup on a development store and still getting "No custom fields found." Any other ideas?

Jason Shopify Expert freakdesign.com.au
Posts:
6741
Last edited 6 months ago

Looks like the tool I used to capture the gifs was (or maybe still is) down. Bad time to check the link but it looks happier now.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
6
6 months ago

Works now! I was making the metafields with ShopifyFD on the product page instead of in settings/general so they were not shop level. Thanks so much!

Andrei Member
Posts:
3
6 months ago

Hi guys,

How insert a new field on collection template using these app?

Thanks

 

Jason Shopify Expert freakdesign.com.au
Posts:
6741
6 months ago

@Andrei -  Take a look at the Liquid docs for ways to show the value of a metafield within a template:
https://help.shopify.com/themes/liquid/objects/metafield

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
1
6 months ago

Dear Jason,

 

thanks for the amazing tool. This makes our job much much easier.

I was wondering if you have any update on the [p][_p] custom field?

I would love to use it for a complementary product on my product page!

 

Kind regards,

 

Andrea

mfk Member
Posts:
52
Last edited 4 months ago

Dear Jason

Im currently having issues trying to Load Custom Fields chrome extension on the 'edit product', 'edit pages' pages etc.

i can still run shopifyfd on the settings page to add or remove fields. but when i run Load Custom Fields on 'edit pages', i get a red error bar saying "Failed to preload required data".

if i run shopifyfd on 'edit pages', i cant see ANY of the fields on the dropdown that are visible in the settings page. weird.

i'm not exactly sure whats causing it? Its working fine on other stores im managing with custom fields. the only difference between this and other stores, is that on this store, i have limited access to some parts of the backend, ie, orders etc.

any help is greatly appreciated.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
4 months ago

Hey mfk,

I ran the tool on one of my test stores and it was able to show the fields without issue. You would see that error if the tool was unable to load data for collections. Do you have access to collections for your account?

If you can do a screen capture or recording that shows your steps that would be helpful. You can post that here:

https://github.com/freakdesign/shopify-custom-fields

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
mfk Member
Posts:
52
4 months ago

yeah for this particular store that im having problems with, i dont have access to products / collections. even though the fields im trying to edit here are for blog articles.

will let you know again once i try running the extension when i have access to products / collections.

thanks for your reply.

mfk Member
Posts:
52
Last edited 4 months ago

so i got the client to grant me access to products and collections, and now i'm able to run the extension and load the fields without any errors. so i guess limited account permissions was the reason. 

thanks for your help.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
4 months ago

Glad to hear it. I'll look into making the error message more useful in the next update.

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
matt Member
Posts:
1
Last edited 4 months ago

Just adding my interest in a Shop Level filter, like [s]. To clarify, this would allow you to create a shop level metafield that would only show up on /admin/settings/general, but not for collections, pages, products. (and mad props for this awesome extension from a new user!)

Posts:
20
Last edited 3 months ago

How do i get this working please?  I'm using the Firefox bookmark. I created a custom field on my shop settings page and i can see the custom fields option showing on a product admin page, between the description and the images. so how do i get it to show up on the actual product page on the internet. i've clicked on 'save custom fields' but nothing has changed.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
3 months ago
g
1
upvotes

@David - The Custom Fields and ShopifyFD Chrome Extensions simple help you add metafields to objects within Shopify. If you then need to show these values on the front end you'll need to modify you theme, so the code knows to show them.

Some resources:

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Posts:
16
2 months ago

Hey Jason,

I wanted to say an enormous thank you once again!

Is the 'product marker' tipped for release in a near future update?

All the very best,

Tom

JohnnyW-KM Member
Posts:
17
Last edited about 2 months ago

Did Custom Fields for Variants ever make its way into the General Tool? The documentation is a bit scarce, but I really need this feature somehow. (I need to enter a price per unit for each of the sizes of the product.)

I've tried [p][v] but nothing (except a "No custom fields found" message on the product page) appears when I do that. If I change it just to [p] it works fine on the product page. If I just do [v] nothing appears (except the afforementioned message on the product page).

Do I need to create a separate custom field for variants only? If so, where can I see it? Clicking "Edit" on a variant doesn't show anything, even with just [v] :(

Thanks for any help. Happy new year!

Update: Looks like I got it working. The bookmarklet can be a little buggy it seems, but if you refresh and re-enable, you can see the custom fields on the variant page. Apparently you DO need a separate custom field for variants. Now I just need to figure out how to pull in the variant data. product.metafields.c_f.base-unit-variant isn't working for me, for some reason.

Michaël G. Member
Posts:
54
Last edited 11 days ago

.

Jason Shopify Expert freakdesign.com.au
Posts:
6741
11 days ago

Since this entire thread is about the tool I made, it does seem a little bit cheeky to be promoting your app here. You should really just make a new post just for it. Interestingly the new version of Custom Fields (in beta) covers most of the limitations yours has - and is free - so you best get cracking on those updates!

★ Winning Partner of the Build a Business competition. ★ http://freakdesign.com.au
Michaël G. Member
Posts:
54
11 days ago

Hi !

Sorry, you're right, I misleaded the thread and thought it was about general custom fields in Shopify. I'll remove my message :).