Settings and geocoder field_type problemCreated 5 years ago by vargvinter
I want to create settings for my custom module. I can't put geocoder field type.
return [ 'center' => [ 'type' => 'anomaly.field_type.geocoder', 'required' => true, 'config' => [ "zoom" => 13, "height" => 400 ], ], ];
There is problem on settings update:
Array to string conversion (SQL: insert into `default_settings_settings` (`key`, `value`, `created_at`, `created_by_id`, `sort_order`) values (acme.module.foobar::center, new york, 2017-12-12 13:28:18, 1, 25))
Thank you @ryanthompson for response.
Fast question: When do you plan to release new version of Pyro and what features are you planning to implement? Any changelog anywhere?
Well that's kind of a trick question. Updates are much more fluid then Pyro vThis to vThat. I update addons individually and post those all up in https://pyrocms.com/posts under releases. Then I update Pyro's base repo to include those.. I've only updated the engine once so far and pry won't need to for a while cause Laravel's LTD.. but there are a crap ton of features coming out through addons soon - wrapping up a large handful of things that are all kinda related.
Updates for addons will include change logs in docs from here on out as well. And new features will be posted / social media'd about as well as doc'd so you'll know if you are anywhere near Pyro on even a semi-regular basis.
The Geocoder FT uses multiple columns and so it's not supported by the Settings / Preferences / Configuration module yet. You could use a variables type concept though.
I have an idea on how to support these fields but haven't had a chance to work on it / flesh it out yet.