Newly added fields with a "def" should get that def for existing documents in the database, for field types where this is safe and sensible

Running 2.59.0.

I’ve been trying to get some default options loaded for my widgets. Seems like it’s either completely broken, the documentation is incorrect, or I am doing it wrong.

I have tried for pretty much all field types, but no matter what I do, it loads the first option in a select, it does not load a text in a string field etc.

I’m using def to set the default value against the value of the select or as a string if a string field.

I would like to dig into the source and try to find out why, but I’m pretty new around here, so I thought I would report it here first… maybe it’s not just me?

[boutell]

def should work, we will take a look.

On Sat, Jun 23, 2018, 5:42 AM Carsten [e-mail] wrote:

Very strange. I tested the select field with a virgin widget but after saving options for tests, I can confirm your behavior.

I managed to set def as value on the input string field. But unfortunately, Apostrophe does not use the value attribute. It places the values inside a shadow-root.

That is the end of my wisdom.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/apostrophecms/apostrophe/issues/1442#issuecomment-399658460, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB9fRTcZI7KfMcfmJaOd2k4Dtl857Bjks5t_g1vgaJpZM4U0rES .

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.