From 5b68a7c3f05e8c506e5ebb0b5e72af0dc89b7988 Mon Sep 17 00:00:00 2001 From: Chris Burgess <chris@giantrobot.co.nz> Date: Thu, 7 Sep 2017 14:17:52 +1200 Subject: [PATCH] Document how to load new Settings metadata --- docs/framework/setting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/framework/setting.md b/docs/framework/setting.md index 06f5a151..5f0fa5bb 100644 --- a/docs/framework/setting.md +++ b/docs/framework/setting.md @@ -153,6 +153,7 @@ As with core settings, all settings declared in extensions should have appropria 1. Provide that the settings folder is declared [Multisite extension example](https://github.com/eileenmcnaughton/org.civicrm.multisite/blob/master/multisite.php#L268). 2. Declare settings as in the same standard as CiviCRM Core [Multisite extension example](https://github.com/eileenmcnaughton/org.civicrm.multisite/blob/master/settings/Multisite.setting.php). 3. Create Settings form, a [good example of generic metadata based setings form in an extension](https://github.com/eileenmcnaughton/nz.co.fuzion.civixero/blob/master/CRM/Civixero/Form/XeroSettings.php) - note that only the setting filter is non-generic +4. Use `cv api system.flush` or `Admin → System Settings → Cleanup Caches` to flush CiviCRM caches and register your new settings metadata. ## Adding Setting Config to Admin Forms. -- GitLab