Custom wizard isn't liking new field types

I’m re-building the pricemate workflow according to the new updated custom wizard plugin.

The issue I faced is, while creating a wizard, it won’t save a field if its not mentioned in the fieldProperties object in discourse/lib/wizard.js.es6

This will prevent the plugin from allowing external plugins to create new field types. A possible solution could be to ask the dev to pass those fieldProperties in the CustomWizard::Field.add_assets method.

The temporary workaround I used is to add the field to the json export of the wizard and import it.

1 Like

@fzngagan Thanks, I’ll take a look at this and also the NewPostManager issue tomorrow.

p.s. I’ve actually added events and locations fields directly into the fieldProperties schema for now. I’ll add generic support for custom fields a bit later.

1 Like