Custom Field Default Value

Okay, Alex, I tried with a test field (less preconceptions than when using a “real” field) and you’re right!

Using your test data, I DO see a 16 when DISPLAYING value in front end.

When seeing the field during editing, however, the radiobutton for 16 is not “filled in.”

This is intended?

Ah, but what about existing places, where you add a new, defaulted set of values in a radiobutton?

So, you are saying, if I add your radiobutton sample of custom fields to existing listings, the radiobutton will be blacked in, as well as showing on, say, the Details page?

Okay, I repeated exactly your example — and it worked exactly as your said.

(I actually tried before, but thought there was problem because I used the single quote when I put in the string of values, thinking I had done it wrong in the past — and it looked a little odd :})

But…I have a thought. Maybe (and I honest cannot say because I don’t have a mental timeline on this) — possibly I changed the value of a listing in the radiobuttons.

And I THEN set a default?

That might not set value for everybody because in the database there WAS an EXISTING value for the field? And wouldn’t overwrite the existing value with the default. (That would make sense.)

Anyway. One of my radiobuttons doesn’t have a black-dot in front of the default, one does.

Not a killer, I was just trying to understand how it worked.

When field displays in NON-editing form, it DOES show the default value. Really, that’s all I need. I just didn’t understand what I had done differently between the two fields!

Alex, sorry I bothered you — and thank you for your perserverance! I will make sure I set a default in the future BEFORE I put in even a testing value.

Maybe this will help someone in the future.