TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-12-21 01:41:46 +03:00
Code Issues Projects Releases Wiki Activity
e7f300d4d2
Ghost/core/server/data/schema/default-settings.json

508 lines
13 KiB
JSON
Raw Normal View History

Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
{
Updating settings types - issue #573, issue #632
2013-09-14 22:04:41 +04:00
"core": {
🎨 settings inconsistency (#8381) no issue - replace camelCase settings keys with underscore_case for consistency - discussed here https://github.com/TryGhost/Ghost-Admin/pull/661#discussion_r112939982
2017-04-24 20:41:00 +03:00
"db_hash": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Add update notifications closes #1464 - adds opt-out via updateCheck:false in config.js - update check is done on admin index, but doesn't interfere with rendering - adds update check module, which gets the usage data, makes the request and handles the response - adds two new settings to default-settings, one for next check time, and one for whether to show the notification - adds a new rejectError method to errorHandling - adds a new helper for displaying the notification Conflicts: core/server/helpers/index.js core/test/unit/server_helpers_index_spec.js
2014-01-03 19:50:03 +04:00
},
Added routes_hash setting (#12171) refs #11999 - The `routes_hash` setting will be used during the boot process to update the hash of currently loaded routes.yaml file in case it's different from last restart
2020-09-07 12:54:55 +03:00
"routes_hash": {
"defaultValue": null,
"type": "string"
},
🎨 settings inconsistency (#8381) no issue - replace camelCase settings keys with underscore_case for consistency - discussed here https://github.com/TryGhost/Ghost-Admin/pull/661#discussion_r112939982
2017-04-24 20:41:00 +03:00
"next_update_check": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "number"
Add update notifications closes #1464 - adds opt-out via updateCheck:false in config.js - update check is done on admin index, but doesn't interfere with rendering - adds update check module, which gets the usage data, makes the request and handles the response - adds two new settings to default-settings, one for next check time, and one for whether to show the notification - adds a new rejectError method to errorHandling - adds a new helper for displaying the notification Conflicts: core/server/helpers/index.js core/test/unit/server_helpers_index_spec.js
2014-01-03 19:50:03 +04:00
},
Update Notification improvements (#9123) closes #5071 - Remove hardcoded notification in admin controller - NOTE: update check notifications are no longer blocking the admin rendering - this is one of the most import changes - we remove the hardcoded release message - we also remove adding a notification manually in here, because this will work differently from now on -> you receive a notification (release or custom) in the update check module and this module adds the notification as is to our database - Change default core settings keys - remove displayUpdateNotification -> this was used to store the release version number send from the UCS -> based on this value, Ghost creates a notification container with self defined values -> not needed anymore - rename seenNotifications to notifications -> the new notifications key will hold both 1. the notification from the USC 2. the information about if a notification was seen or not - this key hold only one release notification - and n custom notifications - Update Check Module: Request to the USC depends on the privacy configuration - useUpdateCheck: true -> does a checkin in the USC (exposes data) - useUpdateCheck: false -> does only a GET query to the USC (does not expose any data) - make the request handling dynamic, so it depends on the flag - add an extra logic to be able to define a custom USC endpoint (helpful for testing) - add an extra logic to be able to force the request to the service (helpful for testing) - Update check module: re-work condition when a check should happen - only if the env is not correct - remove deprecated config.updateCheck - remove isPrivacyDisabled check (handled differently now, explained in last commit) - Update check module: remove `showUpdateNotification` and readability - showUpdateNotification was used in the admin controller to fetch the latest release version number from the db - no need to check against semver in general, the USC takes care of that (no need to double check) - improve readability of `nextUpdateCheck` condition - Update check module: refactor `updateCheckResponse` - remove db call to displayUpdateNotification, not used anymore - support receiving multiple custom notifications - support custom notification groups - the default group is `all` - this will always be consumed - groups can be extended via config e.g. `notificationGroups: ['migration']` - Update check module: refactor createCustomNotification helper - get rid of taking over notification duplication handling (this is not the task of the update check module) - ensure we have good fallback values for non present attributes in a notification - get rid of semver check (happens in the USC) - could be reconsidered later if LTS is gone - Refactor notification API - reason: get rid of in process notification store -> this was an object hold in process -> everything get's lost after restart -> not helpful anymore, because imagine the following case -> you get a notification -> you store it in process -> you mark this notification as seen -> you restart Ghost, you will receive the same notification on the next check again -> because we are no longer have a separate seen notifications object - use database settings key `notification` instead - refactor all api endpoints to support reading and storing into the `notifications` object - most important: notification deletion happens via a `seen` property (the notification get's physically deleted 3 month automatically) -> we have to remember a seen property, because otherwise you don't know which notification was already received/seen - Add listener to remove seen notifications automatically after 3 month - i just decided for 3 month (we can decrease?) - at the end it doesn't really matter, as long as the windows is not tooooo short - listen on updates for the notifications settings - check if notification was seen and is older than 3 month - ignore release notification - Updated our privacy document - Updated docs.ghost.org for privacy config behaviour - contains a migration script to remove old settings keys
2018-01-09 17:20:00 +03:00
"notifications": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "[]",
"type": "array"
Added session_secret setting to schema (#9953) closes #9952 - required by the express-session middleware
2018-10-05 14:25:51 +03:00
},
"session_secret": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Updated theme layer to use members-ssr (#10676) * Removed support for cookies in members auth middleware no-issue The members middleware will no longer be supporting cookies, the cookie will be handled by a new middleware specific for serverside rendering, more informations can be found here: https://paper.dropbox.com/doc/Members-Auth-II-4WP4vF6coMqDYbSMIajo5 * Removed members auth middleware from site app no-issue The site app no longer needs the members auth middleware as it doesn't support cookies, and will be replaced by ssr specific middleware. https://paper.dropbox.com/doc/Members-Auth-II-4WP4vF6coMqDYbSMIajo5 * Added comment for session_secret setting no-issue We are going to have multiple concepts of sessions, so adding a comment here to be specific that this is for the Ghost Admin client * Added theme_session_secret setting dynamic default no-issue Sessions for the theme layer will be signed, so we generate a random hex string to use as a signing key * Added getPublicConfig method * Replaced export of httpHandler with POJO apiInstance no-issue This is mainly to reduce the public api, so it's easier to document. * Renamed memberUserObject -> members no-issue Simplifies the interface, and is more inline with what we would want to export as an api library. * Removed use of require options inside members no-issue This was too tight of a coupling between Ghost and Members * Simplified apiInstance definition no-issue * Added getMember method to members api * Added MembersSSR instance to members service * Wired up routes for members ssr * Updated members auth middleware to use getPublicConfig * Removed publicKey static export from members service * Used real session secret no-issue * Added DELETE /members/ssr handler no-issue This allows users to log out of the theme layer * Fixed missing code property no-issue Ignition uses the statusCode property to forward status codes to call sites * Removed superfluous error middleware no-issue Before we used generic JWT middleware which would reject, now the middleware catches it's own error and doesn't error, thus this middleware is unecessary. * Removed console.logs no-issue * Updated token expirty to hardcoded 20 minutes no-issue This returns to our previous state of using short lived tokens, both for security and simplicity. * Removed hardcoded default member settings no-issue This is no longer needed, as defaults are in default-settings.json * Removed stripe from default payment processor no-issue * Exported `getSiteUrl` method from url utils no-issue This keeps inline with newer naming conventions * Updated how audience access control works no-issue Rather than being passed a function, members api now receives an object which describes which origins have access to which audiences, and how long those tokens should be allowed to work for. It also allows syntax for default tokens where audience === origin requesting it. This can be set to undefined or null to disable this functionality. { "http://site.com": { "http://site.com": { tokenLength: '5m' }, "http://othersite.com": { tokenLength: '1h' } }, "*": { tokenLength: '30m' } } * Updated members service to use access control feature no-issue This also cleans up a lot of unecessary variable definitions, and some other minor cleanups. * Added status code to auth pages html response no-issue This was missing, probably default but better to be explicit * Updated gateway to have membersApiUrl from config no-issue Previously we were parsing the url, this was not very safe as we can have Ghost hosted on a subdomain, and this would have failed. * Added issuer to public config for members no-issue This can be used to request SSR tokens in the client * Fixed path for gateway bundle no-issue * Updated settings model tests no-issue * Revert "Removed stripe from default payment processor" This reverts commit 1d88d9b6d73a10091070bcc1b7f5779d071c7845. * Revert "Removed hardcoded default member settings" This reverts commit 9d899048ba7d4b272b9ac65a95a52af66b30914a. * Installed @tryghost/members-ssr * Fixed tests for settings model
2019-04-16 17:50:25 +03:00
},
"theme_session_secret": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Implemented externally verifiable identity tokens no-issue This adds two new endpoints, one at /ghost/.well-known/jwks.json for exposing a public key, and one on the canary api /identities, which allows the Owner user to fetch a JWT. This token can then be used by external services to verify the domain * Added ghost_{public,private}_key settings This key can be used for generating tokens for communicating with external services on behalf of Ghost * Added .well-known directory to /ghost/.well-known We add a jwks.json file to the .well-known directory which exposes a public JWK which can be used to verify the signatures of JWT's created by Ghost This is added to the /ghost/ path so that it can live on the admin domain, rather than the frontend. This is because most of its uses/functions will be in relation to the admin domain. * Improved settings model tests This removes hardcoded positions in favour of testing that a particular event wasn't emitted which is less brittle and more precise about what's being tested * Fixed parent app unit tests for well-known This updates the parent app unit tests to check that the well-known route is mounted. We all change proxyquire to use `noCallThru` which ensures that the ubderlying modules are not required. This stops the initialisation logic in ./well-known erroring in tests https://github.com/thlorenz/proxyquire/issues/215 * Moved jwt signature to a separate 'token' propery This structure corresponds to other resources and allows to exptend with additional properties in future if needed
2020-01-20 14:45:58 +03:00
},
"ghost_public_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Implemented externally verifiable identity tokens no-issue This adds two new endpoints, one at /ghost/.well-known/jwks.json for exposing a public key, and one on the canary api /identities, which allows the Owner user to fetch a JWT. This token can then be used by external services to verify the domain * Added ghost_{public,private}_key settings This key can be used for generating tokens for communicating with external services on behalf of Ghost * Added .well-known directory to /ghost/.well-known We add a jwks.json file to the .well-known directory which exposes a public JWK which can be used to verify the signatures of JWT's created by Ghost This is added to the /ghost/ path so that it can live on the admin domain, rather than the frontend. This is because most of its uses/functions will be in relation to the admin domain. * Improved settings model tests This removes hardcoded positions in favour of testing that a particular event wasn't emitted which is less brittle and more precise about what's being tested * Fixed parent app unit tests for well-known This updates the parent app unit tests to check that the well-known route is mounted. We all change proxyquire to use `noCallThru` which ensures that the ubderlying modules are not required. This stops the initialisation logic in ./well-known erroring in tests https://github.com/thlorenz/proxyquire/issues/215 * Moved jwt signature to a separate 'token' propery This structure corresponds to other resources and allows to exptend with additional properties in future if needed
2020-01-20 14:45:58 +03:00
},
"ghost_private_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
},
"members_public_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
},
"members_private_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
},
"members_email_auth_secret": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Added new stripe webhook settings (#12028) no-issue They will be used to store webhook information so that we can persist it between boots and simplify the creation process of webhooks in members
2020-07-10 17:26:06 +03:00
},
"members_stripe_webhook_id": {
"defaultValue": null,
"type": "string"
},
"members_stripe_webhook_secret": {
"defaultValue": null,
"type": "string"
Updating settings types - issue #573, issue #632
2013-09-14 22:04:41 +04:00
}
},
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
"site": {
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
"title": {
Set soft limits for blog title and description (#9250) refs #8143 Add max length validations to settings: - `blog.title`: 150 chars - `blog.description`: 200 chars The `validateSettings` fn in our validations checks for existing `validations` properties in our `default-settings.json` file, similar to other tables in our `schema.js`.
2017-11-16 15:58:22 +03:00
"defaultValue": "Ghost",
"validations": {
"isLength": {
"max": 150
}
Added migration to populate settings.{group,flags} (#11954) refs https://github.com/TryGhost/Ghost/issues/10318 - maps old `settings.type` values to new `settings.type/group` values - uses an explicit map so that we don't lose information and can safely roll back even though we're modifying `settings.type` too - updates `settings.type` values too to keep code working while we switch to using `settings.group` - sets the `settings.group` value for all settings which are keeping the same group as their current type - adapts `settings.type` validations to match new groups - adds flags to specific settings, both in the migration for existing settings records and in default-settings.json for new settings records
2020-06-24 14:38:18 +03:00
},
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"flags": "PUBLIC",
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
"description": {
Updated default settings for 4.0 - With 4.0 we have a brand new version of Casper, new fixtures and new default settings - This all comes from the marketing and design teams to refresh the look and feel of Ghost Note on accent color: This commit changes the default accent colour again. The intention is that new sites should get #FF1A75 (pink) as their default. Any existing sites that do not have an accent colour set yet, should get #15171A (black) on upgrading to 4.0. These are different as they are different experinces. Fresh sites will be guided to pick a color, so a bright color is more visible and helps to see what can be done, whilst existing sites get a muted black, that should be a sensible fall back color.
2021-03-09 23:11:07 +03:00
"defaultValue": "Thoughts, stories and ideas",
Set soft limits for blog title and description (#9250) refs #8143 Add max length validations to settings: - `blog.title`: 150 chars - `blog.description`: 200 chars The `validateSettings` fn in our validations checks for existing `validations` properties in our `default-settings.json` file, similar to other tables in our `schema.js`.
2017-11-16 15:58:22 +03:00
"validations": {
"isLength": {
"max": 200
}
Added migration to populate settings.{group,flags} (#11954) refs https://github.com/TryGhost/Ghost/issues/10318 - maps old `settings.type` values to new `settings.type/group` values - uses an explicit map so that we don't lose information and can safely roll back even though we're modifying `settings.type` too - updates `settings.type` values too to keep code working while we switch to using `settings.group` - sets the `settings.group` value for all settings which are keeping the same group as their current type - adapts `settings.type` validations to match new groups - adds flags to specific settings, both in the migration for existing settings records and in default-settings.json for new settings records
2020-06-24 14:38:18 +03:00
},
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"flags": "PUBLIC",
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
"logo": {
Updated default settings for 4.0 - With 4.0 we have a brand new version of Casper, new fixtures and new default settings - This all comes from the marketing and design teams to refresh the look and feel of Ghost Note on accent color: This commit changes the default accent colour again. The intention is that new sites should get #FF1A75 (pink) as their default. Any existing sites that do not have an accent colour set yet, should get #15171A (black) on upgrading to 4.0. These are different as they are different experinces. Fresh sites will be guided to pick a color, so a bright color is more visible and helps to see what can be done, whilst existing sites get a muted black, that should be a sensible fall back color.
2021-03-09 23:11:07 +03:00
"defaultValue": "",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
🙀 Image field naming & new img_url helper (#8364) * 🙀 change database schema for images - rename user/post/tag images - contains all the required changes from the schema change * Refactor helper/meta data - rename cover to cover_image - also rename default settings to match the pattern - rename image to profile_image for user - rename image to feature_image for tags/posts * {{image}} >>> {{img_url}} - rename - change the functionality - attr is required - e.g. {{img_url feature_image}} * gscan 1.0.0 - update yarn.lock * Update casper reference: 1.0-changes - see https://github.com/TryGhost/Casper/commit/5487b4da8d2ad7c6a6d003a3a0ee1a860e0de34d
2017-04-24 20:21:47 +03:00
"cover_image": {
Updated default settings for 4.0 - With 4.0 we have a brand new version of Casper, new fixtures and new default settings - This all comes from the marketing and design teams to refresh the look and feel of Ghost Note on accent color: This commit changes the default accent colour again. The intention is that new sites should get #FF1A75 (pink) as their default. Any existing sites that do not have an accent colour set yet, should get #15171A (black) on upgrading to 4.0. These are different as they are different experinces. Fresh sites will be guided to pick a color, so a bright color is more visible and helps to see what can be done, whilst existing sites get a muted black, that should be a sensible fall back color.
2021-03-09 23:11:07 +03:00
"defaultValue": "https://static.ghost.org/v4.0.0/images/publication-cover.jpg",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "string"
✨ Find favicon in Ghost (#7713) refs #7688 Adds logic in theme settings api to either serve an uploaded favicon and give it the type `upload` or use the default settings `default`, which will serve the favicon from our shared directory. TODOs for #7688: - [X] Figure out, which favicon should be used (uploaded or default) -> this PR - [ ] Serve and redirect the favicon for any browser requests, incl. redirects - [ ] Upload favicon via `general/settings` and implement basic admin validations -> [WIP] TryGhost/Ghost-Admin#397 - [ ] Built server side validations
2017-01-23 12:13:52 +03:00
},
🐷 Rename 'favicon' to 'icon' (#7888) refs TryGhost/Ghost#7688 Just renames `favicon` to `icon` as our usage for it will not be for favicon purposes only.
2017-01-25 13:02:02 +03:00
"icon": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "",
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
"accent_color": {
Updated default settings for 4.0 - With 4.0 we have a brand new version of Casper, new fixtures and new default settings - This all comes from the marketing and design teams to refresh the look and feel of Ghost Note on accent color: This commit changes the default accent colour again. The intention is that new sites should get #FF1A75 (pink) as their default. Any existing sites that do not have an accent colour set yet, should get #15171A (black) on upgrading to 4.0. These are different as they are different experinces. Fresh sites will be guided to pick a color, so a bright color is more visible and helps to see what can be done, whilst existing sites get a muted black, that should be a sensible fall back color.
2021-03-09 23:11:07 +03:00
"defaultValue": "#FF1A75",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"flags": "PUBLIC",
Added default value to accent_color setting (#12743) refs TryGhost/Team#535 We want to ensure that a site will always have a default value of `'#15171A'` for the accent_color setting. Since the boot process changed we have three cases to account for: 1. Setting does not exist 2. Setting exists with no value 3. Setting exists with a value It is only in the case of 2. that we want the migration to update the database with a default value. In the case of 3. the site owner has already set a value, which we do not want to override. In the case of 1. the setting will be created (and populated with default value) from the default-settings.json file, by the populateDefaults method called from the settings service We also update the accent_color setting to include a non-empty validation, to ensure that the setting will always have a value, as sites before 4.x may have an empty accent_color, we must update the importer to set the default value if one is not present. Otherwise we would run into validation errors and even if we didn't would have an invalid database state.
2021-03-09 19:15:10 +03:00
"validations": {
"isEmpty": false
},
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "string"
✨ Added new brand blog setting (#11408) no issue Adds new `brand: {primary_color: ''}` blog setting behind dev flag for setting user-defined brand color in themes and emails.
2019-12-17 13:45:31 +03:00
},
Renamed settings keys from default_locale to lang refs #10318 refs https://github.com/TryGhost/Ghost/commit/2614565d5abf1982b61c7ef6e9360f2b9ddb0574 - Renames default_locale settings key as introduced in referenced migration
2020-06-22 13:27:05 +03:00
"lang": {
🎨 rename language to locale and use `en` as default locale (#8490) no issue - this PR references indirecty to https://github.com/TryGhost/Ghost/pull/8437 - i would like to have the settings change already in place before we release the beta - the i18n feature is able to change the locale of Ghost - most i18n libraries use locale - adding/changing settings doesn't require a migration file, but it can make the database a bit messy (because you can end up with default_locale and lang) - furthermore we agreed that the default locale for Ghost should be simply `en`, not `en_US` or `en_GB`
2017-05-31 18:05:49 +03:00
"defaultValue": "en",
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
"validations": {
🔑 Update Validator to 6.2.1 (#7823) no issue Uses new version of [validator](https://github.com/chriso/validator.js) which checks also for in URL embedded script tags.
2017-01-10 15:05:25 +03:00
"isEmpty": false
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
Renamed settings keys active_timezone to timezone refs https://github.com/TryGhost/Ghost/issues/10318 refs https://github.com/TryGhost/Ghost/commit/2614565d5abf1982b61c7ef6e9360f2b9ddb0574 - Renames to match referenced migration renames - Fixed API responses so they are consistent with newly renamed fields - Not returning lang and timezone keys from settings in API v2 ther rest should be returned in API v3/canary
2020-06-22 14:21:00 +03:00
"timezone": {
Adds UTC as select option to timezones select list no issue - adds '(GMT) UTC' as select option to available Timezones - changes default value for active Timezone to 'Etc/UTC'
2016-06-10 16:05:27 +03:00
"defaultValue": "Etc/UTC",
timezones: Always use the timezone of blog setting closes #6406 - adding timeZone Service to get the offset (=timezone reg. moment-timezone) overall available - new publishedAtOffset date as CP using timeZone service and moment-timezone to calculate offset incl. DST - removing timezone-obj transform as it became obsolete with moment-timezone - reading timezones from configuration/timezones api endpoint - adding a moment-utc transform to only work with utc times in backend - when switching the timezone in the select box, the user will be shown the local time of the selected timezone - added clock service to show actual time ticking below select box - default timezone is '(GMT) Greenwich Mean Time : Dublin, Edinburgh, London' - if no timezone is saved in the settings yet, the default value will be used - showing local time in 'Publish Date' when it's a draft and no actual publishedAt value exists - Removed the format 'DD MMM YY @ HH:mm (UTC Z)' which resolves to '01 Jan 16 @ 14:00 (UTC +02:00)' - Changing the date.js helper in core/server for moment-timezone - Fix timezone select: updates `selectedTimezone` to return the matching object from `availableTimezones` - Including timezones in test for date-helper - update to moment-timezone 0.5.1 - moving form-group of 'selectTimezone' further up so - Tests: - Set except for clock service in test env - adding fixtures to mirage - adding 'service.ajax' to navigation-test.js - adding 'service:ghostPaths' to navigation-test.js - Code improvements - Changing clockservice to ES6
2016-02-02 10:04:40 +03:00
"validations": {
improvement: validate timezones (#7143) no issue - add isTimezone to schema validation
2016-07-26 12:23:20 +03:00
"isTimezone": true,
🔑 Update Validator to 6.2.1 (#7823) no issue Uses new version of [validator](https://github.com/chriso/validator.js) which checks also for in URL embedded script tags.
2017-01-10 15:05:25 +03:00
"isEmpty": false
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
timezones: Always use the timezone of blog setting closes #6406 - adding timeZone Service to get the offset (=timezone reg. moment-timezone) overall available - new publishedAtOffset date as CP using timeZone service and moment-timezone to calculate offset incl. DST - removing timezone-obj transform as it became obsolete with moment-timezone - reading timezones from configuration/timezones api endpoint - adding a moment-utc transform to only work with utc times in backend - when switching the timezone in the select box, the user will be shown the local time of the selected timezone - added clock service to show actual time ticking below select box - default timezone is '(GMT) Greenwich Mean Time : Dublin, Edinburgh, London' - if no timezone is saved in the settings yet, the default value will be used - showing local time in 'Publish Date' when it's a draft and no actual publishedAt value exists - Removed the format 'DD MMM YY @ HH:mm (UTC Z)' which resolves to '01 Jan 16 @ 14:00 (UTC +02:00)' - Changing the date.js helper in core/server for moment-timezone - Fix timezone select: updates `selectedTimezone` to return the matching object from `availableTimezones` - Including timezones in test for date-helper - update to moment-timezone 0.5.1 - moving form-group of 'selectTimezone' further up so - Tests: - Set except for clock service in test env - adding fixtures to mirage - adding 'service.ajax' to navigation-test.js - adding 'service:ghostPaths' to navigation-test.js - Code improvements - Changing clockservice to ES6
2016-02-02 10:04:40 +03:00
},
Renamed ghost_head/ghost_foot to codeinjection_head/codeinjection_foot refs #10318 refs https://github.com/TryGhost/Ghost/commit/2614565d5abf1982b61c7ef6e9360f2b9ddb0574 - Renamed ghost_head/ghost_foot in settings to match the new names introduced in migrations - Above change lead to reshufling in the mappings in input/output serializers - Makes sure change is compatible with v2 API
2020-06-23 14:39:05 +03:00
"codeinjection_head": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "",
"type": "string"
adds code injection admin frontend implementation, handlebar helpers + settings escaping handlebars
2014-07-31 23:36:20 +04:00
},
Renamed ghost_head/ghost_foot to codeinjection_head/codeinjection_foot refs #10318 refs https://github.com/TryGhost/Ghost/commit/2614565d5abf1982b61c7ef6e9360f2b9ddb0574 - Renamed ghost_head/ghost_foot in settings to match the new names introduced in migrations - Above change lead to reshufling in the mappings in input/output serializers - Makes sure change is compatible with v2 API
2020-06-23 14:39:05 +03:00
"codeinjection_foot": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "",
"type": "string"
Start of labs issue #4409
2014-12-14 20:56:04 +03:00
},
Structured Data 3.0 closes #6534 - new input fields in general settings incl. validation - facebook and twitter as new models in settings.js - adds values for facebook and twitter to default-settings.js - adds blog helpers for facebook and twittter - rather than saving the whole URL, the Twitter username incl. '@' will be extracted from URL and saved in the settings. The User will still input the full URL. After saving the blog setting, the stored Twitter username will be parsed again as the full URL and available in the input field. A custom transform is used for this. - adding meta fields to be rendered in {{ghost_head}}: - '<meta property="article:publisher" content="https://www.facebook.com/page" />' and - '<meta name="twitter:site" content="@user"/>' - adds facebook and twitter to unit test for structured data - adds unit test for general settings - adds acceptance test for new input fields in general settings - adds a custom transform for twitter model to save only the username to the server - adds unit test for transform
2016-03-03 11:52:27 +03:00
"facebook": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "ghost",
"type": "string"
Structured Data 3.0 closes #6534 - new input fields in general settings incl. validation - facebook and twitter as new models in settings.js - adds values for facebook and twitter to default-settings.js - adds blog helpers for facebook and twittter - rather than saving the whole URL, the Twitter username incl. '@' will be extracted from URL and saved in the settings. The User will still input the full URL. After saving the blog setting, the stored Twitter username will be parsed again as the full URL and available in the input field. A custom transform is used for this. - adding meta fields to be rendered in {{ghost_head}}: - '<meta property="article:publisher" content="https://www.facebook.com/page" />' and - '<meta name="twitter:site" content="@user"/>' - adds facebook and twitter to unit test for structured data - adds unit test for general settings - adds acceptance test for new input fields in general settings - adds a custom transform for twitter model to save only the username to the server - adds unit test for transform
2016-03-03 11:52:27 +03:00
},
"twitter": {
Updated default settings for 4.0 - With 4.0 we have a brand new version of Casper, new fixtures and new default settings - This all comes from the marketing and design teams to refresh the look and feel of Ghost Note on accent color: This commit changes the default accent colour again. The intention is that new sites should get #FF1A75 (pink) as their default. Any existing sites that do not have an accent colour set yet, should get #15171A (black) on upgrading to 4.0. These are different as they are different experinces. Fresh sites will be guided to pick a color, so a bright color is more visible and helps to see what can be done, whilst existing sites get a muted black, that should be a sensible fall back color.
2021-03-09 23:11:07 +03:00
"defaultValue": "@ghost",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "string"
Structured Data 3.0 closes #6534 - new input fields in general settings incl. validation - facebook and twitter as new models in settings.js - adds values for facebook and twitter to default-settings.js - adds blog helpers for facebook and twittter - rather than saving the whole URL, the Twitter username incl. '@' will be extracted from URL and saved in the settings. The User will still input the full URL. After saving the blog setting, the stored Twitter username will be parsed again as the full URL and available in the input field. A custom transform is used for this. - adding meta fields to be rendered in {{ghost_head}}: - '<meta property="article:publisher" content="https://www.facebook.com/page" />' and - '<meta name="twitter:site" content="@user"/>' - adds facebook and twitter to unit test for structured data - adds unit test for general settings - adds acceptance test for new input fields in general settings - adds a custom transform for twitter model to save only the username to the server - adds unit test for transform
2016-03-03 11:52:27 +03:00
},
Navigation UI Ember Integration Closes #4537 - Adds Navigation to the Settings menu - Adds a `navigationUI` config flag (redirects if not an editor or author)
2015-01-11 22:55:52 +03:00
"navigation": {
Updated default settings for 4.0 - With 4.0 we have a brand new version of Casper, new fixtures and new default settings - This all comes from the marketing and design teams to refresh the look and feel of Ghost Note on accent color: This commit changes the default accent colour again. The intention is that new sites should get #FF1A75 (pink) as their default. Any existing sites that do not have an accent colour set yet, should get #15171A (black) on upgrading to 4.0. These are different as they are different experinces. Fresh sites will be guided to pick a color, so a bright color is more visible and helps to see what can be done, whilst existing sites get a muted black, that should be a sensible fall back color.
2021-03-09 23:11:07 +03:00
"defaultValue": "[{\"label\":\"Home\",\"url\":\"/\"},{\"label\":\"About\",\"url\":\"/about/\"},{\"label\":\"Collection\",\"url\":\"/tag/getting-started/\"},{\"label\":\"Author\",\"url\":\"/author/ghost/\"},{\"label\":\"Portal\",\"url\":\"/portal/\"}]",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "array"
Slack integration closes #6584 - Frontend Changes: - adds 'Apps' to Navigation Menu - adds 'Slack' as nested page to Apps - adds `apps.css` - adds `slack-integration` model and uses `slack-settings` custom transform to parse JSON file - adds validation for `slack` model - adds fixtures and `slack/test` API endpoint to Mirage - adds acceptance tests for `apps-test` and `slack-test` - adds unit tests for `slack-settings` and `slack-integration` - Backend Changes: - adds API endpoint `slack/test` to send Test Notification - adds default-values for slack model - sends payload to slack: - text: the url of the blogpost / test message - icon_url: url to ghost logo - username: Ghost - adds `slack/index.js` to send webhook to slack if - a new post is published (if slack webhook url is saved in settings) - user clicks on 'Send Test Notification' in UI - adds `slack.init()` to `server.index.js` to add event listener - adds unit test for `slack/index`
2016-03-29 11:40:44 +03:00
},
✨ Added support for secondary navigation (#11409) no issue - Secondary navigation means most nav concepts are supported, e.g. header & footer, or left & right - The UI is added separately, this PR adds supporting concepts: - make sure the default value is an empty array - add support in the API (v3 only) - add handling in the navigation helper
2019-12-04 07:12:02 +03:00
"secondary_navigation": {
Refined navigation default settings for 4.0 refs https://github.com/TryGhost/Ghost/commit/2bba9989db44bec474f26ba48f8f5f59539acaa6 - Note: this will require new fixtures so that the navigation links actually work - These updates are all in aid of getting the best possible default setup and onboarding experinence for new Ghost users
2021-03-10 12:59:54 +03:00
"defaultValue": "[{\"label\":\"Data & privacy\",\"url\":\"/privacy/\"},{\"label\":\"Contact\",\"url\":\"/contact/\"},{\"label\":\"Contribute →\",\"url\":\"/contribute/\"}]",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "array"
✨ Added support for secondary navigation (#11409) no issue - Secondary navigation means most nav concepts are supported, e.g. header & footer, or left & right - The UI is added separately, this PR adds supporting concepts: - make sure the default value is an empty array - add support in the API (v3 only) - add handling in the navigation helper
2019-12-04 07:12:02 +03:00
},
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
"meta_title": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 300
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"meta_description": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 500
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"og_image": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 2000
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"og_title": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 300
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"og_description": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 300
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"twitter_image": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 2000
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"twitter_title": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 300
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Added global site SEO fields in Admin API (#10923) refs #10921 - New SEO related fields will now be available as a part of Admin API /settings endpoint - The ordering of fields is taken from post's schema - Extended settings test suite with new SEO fields - Adjusted settings model unit test
2019-07-18 17:24:34 +03:00
},
"twitter_description": {
"defaultValue": null,
"validations": {
"isLength": {
"max": 300
}
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
}
},
Updating settings types - issue #573, issue #632
2013-09-14 22:04:41 +04:00
"theme": {
🎨 settings inconsistency (#8381) no issue - replace camelCase settings keys with underscore_case for consistency - discussed here https://github.com/TryGhost/Ghost-Admin/pull/661#discussion_r112939982
2017-04-24 20:41:00 +03:00
"active_theme": {
Added migration to populate settings.{group,flags} (#11954) refs https://github.com/TryGhost/Ghost/issues/10318 - maps old `settings.type` values to new `settings.type/group` values - uses an explicit map so that we don't lose information and can safely roll back even though we're modifying `settings.type` too - updates `settings.type` values too to keep code working while we switch to using `settings.group` - sets the `settings.group` value for all settings which are keeping the same group as their current type - adapts `settings.type` validations to match new groups - adds flags to specific settings, both in the migration for existing settings records and in default-settings.json for new settings records
2020-06-24 14:38:18 +03:00
"defaultValue": "casper",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"flags": "RO",
"type": "string"
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
}
},
Change type for private blog settings refs #5614 and #5503 - update private blog type, including update to settings.edit - switch order of populate settings & update fixtures + populate all settings Private blog settings should not be returned by public endpoints therefore they need a type which is not `blog` or `theme`. `core` doesn't suit either, as those settings don't usually have UI To resolve this, I created a new type `private` which can be used for any setting which has a UI but should not be public data
2015-08-24 14:43:26 +03:00
"private": {
🎨 settings inconsistency (#8381) no issue - replace camelCase settings keys with underscore_case for consistency - discussed here https://github.com/TryGhost/Ghost-Admin/pull/661#discussion_r112939982
2017-04-24 20:41:00 +03:00
"is_private": {
Updated settings validations refs #10582 - the db input formatter ensures we always forward "true" or "false" for boolean fields
2019-03-07 14:23:57 +03:00
"defaultValue": "false",
"validations": {
"isIn": [["true", "false"]]
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "boolean"
Change type for private blog settings refs #5614 and #5503 - update private blog type, including update to settings.edit - switch order of populate settings & update fixtures + populate all settings Private blog settings should not be returned by public endpoints therefore they need a type which is not `blog` or `theme`. `core` doesn't suit either, as those settings don't usually have UI To resolve this, I created a new type `private` which can be used for any setting which has a UI but should not be public data
2015-08-24 14:43:26 +03:00
},
"password": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "",
"type": "string"
✨ Private RSS feed (#9088) refs #9001 When a blog is in private mode there is now an unguessable URL that allows access to the RSS feed for internal use, commenting systems, etc. - add public hash for private blogging - auto generate on bootstrap if missing - global hash, we can re-use in the future - update private blogging middleware to detect the private RSS URL and rewrite it so that the normal rss route/code is used for display - if a normal `/rss/` route is accessed with a private session return a 404
2017-10-05 13:07:32 +03:00
},
"public_hash": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Change type for private blog settings refs #5614 and #5503 - update private blog type, including update to settings.edit - switch order of populate settings & update fixtures + populate all settings Private blog settings should not be returned by public endpoints therefore they need a type which is not `blog` or `theme`. `core` doesn't suit either, as those settings don't usually have UI To resolve this, I created a new type `private` which can be used for any setting which has a UI but should not be public data
2015-08-24 14:43:26 +03:00
}
Added members related db changes and models refs #10213
2018-12-10 12:20:54 +03:00
},
"members": {
Improve visibility's default handling (#11183) no issue - Moved default_content_visibility out of labs as we should be extra careful with what is exposed in the labs + it doesn't really belong there.
2019-10-02 12:08:10 +03:00
"default_content_visibility": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "public",
"type": "string"
Improve visibility's default handling (#11183) no issue - Moved default_content_visibility out of labs as we should be extra careful with what is exposed in the labs + it doesn't really belong there.
2019-10-02 12:08:10 +03:00
},
Migrated `members_allow_free_signup` setting to `members_signup_access` (#12886) refs https://github.com/TryGhost/Team/issues/579 Currently the members signup setting is explicitly yes/no to allowing free members signup, with the implication that when set to "no" members is still active but members have to be created via Stripe or the admin API. This change renames the setting and changes its type to allow more than a binary option. - migration to create/update the new setting based on the old value - free signup = "all", no free signup = "invite"; matches the current UI for this setting - rename setting everywhere it's used/tested against - modify `getAllowSelfSignup()` used to configure members packages to only return `true` when the new setting is set to `'all'` to match behaviour to the older setting - update importer to rename the setting when importing from an older Ghost version
2021-04-19 18:36:30 +03:00
"members_signup_access": {
"defaultValue": "all",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"validations": {
"isEmpty": false,
Migrated `members_allow_free_signup` setting to `members_signup_access` (#12886) refs https://github.com/TryGhost/Team/issues/579 Currently the members signup setting is explicitly yes/no to allowing free members signup, with the implication that when set to "no" members is still active but members have to be created via Stripe or the admin API. This change renames the setting and changes its type to allow more than a binary option. - migration to create/update the new setting based on the old value - free signup = "all", no free signup = "invite"; matches the current UI for this setting - rename setting everywhere it's used/tested against - modify `getAllowSelfSignup()` used to configure members packages to only return `true` when the new setting is set to `'all'` to match behaviour to the older setting - update importer to rename the setting when importing from an older Ghost version
2021-04-19 18:36:30 +03:00
"isIn": [["all", "invite", "none"]]
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
Migrated `members_allow_free_signup` setting to `members_signup_access` (#12886) refs https://github.com/TryGhost/Team/issues/579 Currently the members signup setting is explicitly yes/no to allowing free members signup, with the implication that when set to "no" members is still active but members have to be created via Stripe or the admin API. This change renames the setting and changes its type to allow more than a binary option. - migration to create/update the new setting based on the old value - free signup = "all", no free signup = "invite"; matches the current UI for this setting - rename setting everywhere it's used/tested against - modify `getAllowSelfSignup()` used to configure members packages to only return `true` when the new setting is set to `'all'` to match behaviour to the older setting - update importer to rename the setting when importing from an older Ghost version
2021-04-19 18:36:30 +03:00
"type": "string"
Added stripe_connect_integration default setting no-issue This will be used to store the keys and other information after a sucessful Stripe Connect OAuth flow.
2020-05-28 13:40:49 +03:00
},
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
"members_from_address": {
Added RO flag to members_from_address refs #10318 This was incorrectly missing before
2020-06-30 14:26:27 +03:00
"defaultValue": "noreply",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"flags": "RO",
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
Added migrations for support and reply email address setting (#12163) no issue - Added default settings for the two new setting fields - `members_support_address` and `members_reply_address` - Added migrations for setting group for new email settings - Migration sets current from address as new support address default - Added migration to set new support address same as from address - Updated tests for new settings - `members_support_address` - How members can reach for help with their account, public setting - `members_reply_address` - Where you receive responses to newsletters
2020-08-27 17:57:50 +03:00
"members_support_address": {
"defaultValue": "noreply",
"flags": "PUBLIC,RO",
"type": "string"
},
"members_reply_address": {
"defaultValue": "newsletter",
"validations": {
"isEmpty": false,
"isIn": [["newsletter", "support"]]
},
"type": "string"
},
Added new settings for members signup redirects (#12370) refs #12366 Adds two new settings for redirecting members after signup, based on if they're paid or free, defaulting to the current redirect of "/"
2020-11-17 20:17:54 +03:00
"members_free_signup_redirect": {
"defaultValue": "/",
"type": "string"
},
"members_paid_signup_redirect": {
"defaultValue": "/",
"type": "string"
},
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
"stripe_product_name": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "Ghost Subscription",
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_secret_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_publishable_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_plans": {
Updated stripe_plans & portal_plans settings refs https://github.com/TryGhost/Team/issues/586 We are no longer using the `stripe_plans` setting, instead we are using the `stripe_prices` database table. However, we must keep the setting as the migration from the setting to the database is not done as a standard migration, but in code. This means our code has to still read and pass the setting because we will never know if the migration in code has run yet. The `portal_plans` setting has been updated to only include 'free' by default, because the setting must include id's now rather than names.
2021-05-04 17:35:37 +03:00
"defaultValue": "[]",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "array"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_connect_publishable_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_connect_secret_key": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_connect_livemode": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "boolean"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_connect_display_name": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Cleaned up members & stripe settings (#11957) * Updated members default settings ref #10318 This pulls out the members_subscription_settings & stripe_connect_intgration settings into separate keys * Updated usage of members_from_address * Updated stripe_connect usage * Updated members config to use new settings * Updated members middleware to use isStripeConnected * Updated members service to reload correctly We reload the members-api instance when the related settings change, so this makes sure we're listening to the correct settings changes * Updated ghost_head helper to use new settings * Updated theme middleware to use new settings * Renamed members_allow_signup -> members_allow_free_signup * Fixed tests after settings refactor * Removed from direct key settings key * Fixed regression tests for settings api
2020-06-29 17:22:42 +03:00
},
"stripe_connect_account_id": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": null,
"type": "string"
Added settings for members 'free' price refs https://github.com/TryGhost/Team/issues/637 The "free" price - when Members signup without using Stripe, should have a name and description, so that it can be displayed in Portal in a similar way to paid price's. As there is only ever one, and it is not a fully fledged price, a setting makes more sense than a dedicated db table.
2021-05-04 17:43:18 +03:00
},
"members_free_price_name": {
"defaultValue": "Free",
"type": "string"
},
"members_free_price_description": {
Updated default description for free price refs https://github.com/TryGhost/Team/issues/671 When turning on custom products, existing sites should have default price descriptions that match existing values for prices. This change sets the default description for Free price to match existing hardcoded value.
2021-05-10 11:48:43 +03:00
"defaultValue": "Free Preview",
Added settings for members 'free' price refs https://github.com/TryGhost/Team/issues/637 The "free" price - when Members signup without using Stripe, should have a name and description, so that it can be displayed in Portal in a similar way to paid price's. As there is only ever one, and it is not a fully fledged price, a setting makes more sense than a dedicated db table.
2021-05-04 17:43:18 +03:00
"type": "string"
Added new top-level bulk email settings no issue
2019-11-13 06:48:26 +03:00
}
},
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"portal": {
Added new settings for members modal no issue - reverts commit 87c31444fd41d182f3add55f72e0e0fb9cdcc1ff but with modifications to settings naming - Adds new settings for members modal customization to default settings - `portal_button` controls the visibility of beacon in members modal - `portal_name` controls the visibility of name field in signup - `portal_plans` controls the visibility of plans allowed for member to signup with - Adds stripe connect check to determine if stripe is setup or not - Adds the 3 new settings to members site data - Updates to snake case naming for members site API data
2020-06-19 17:04:40 +03:00
"portal_name": {
"defaultValue": "true",
"validations": {
"isEmpty": false,
"isIn": [["true", "false"]]
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "boolean"
Added new settings for members modal no issue - reverts commit 87c31444fd41d182f3add55f72e0e0fb9cdcc1ff but with modifications to settings naming - Adds new settings for members modal customization to default settings - `portal_button` controls the visibility of beacon in members modal - `portal_name` controls the visibility of name field in signup - `portal_plans` controls the visibility of plans allowed for member to signup with - Adds stripe connect check to determine if stripe is setup or not - Adds the 3 new settings to members site data - Updates to snake case naming for members site API data
2020-06-19 17:04:40 +03:00
},
"portal_button": {
Revert "Updated default visibility for membersjs button" This reverts commit bf80ba924ff87eb59597c3f158d1cbfdfc2dd887. - New sites should have the portal enabled and shown by default when they enable members (behind dev flag currently)
2020-07-06 11:41:17 +03:00
"defaultValue": "true",
Added new settings for members modal no issue - reverts commit 87c31444fd41d182f3add55f72e0e0fb9cdcc1ff but with modifications to settings naming - Adds new settings for members modal customization to default settings - `portal_button` controls the visibility of beacon in members modal - `portal_name` controls the visibility of name field in signup - `portal_plans` controls the visibility of plans allowed for member to signup with - Adds stripe connect check to determine if stripe is setup or not - Adds the 3 new settings to members site data - Updates to snake case naming for members site API data
2020-06-19 17:04:40 +03:00
"validations": {
"isEmpty": false,
"isIn": [["true", "false"]]
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "boolean"
Added new settings for members modal no issue - reverts commit 87c31444fd41d182f3add55f72e0e0fb9cdcc1ff but with modifications to settings naming - Adds new settings for members modal customization to default settings - `portal_button` controls the visibility of beacon in members modal - `portal_name` controls the visibility of name field in signup - `portal_plans` controls the visibility of plans allowed for member to signup with - Adds stripe connect check to determine if stripe is setup or not - Adds the 3 new settings to members site data - Updates to snake case naming for members site API data
2020-06-19 17:04:40 +03:00
},
"portal_plans": {
Updated stripe_plans & portal_plans settings refs https://github.com/TryGhost/Team/issues/586 We are no longer using the `stripe_plans` setting, instead we are using the `stripe_prices` database table. However, we must keep the setting as the migration from the setting to the database is not done as a standard migration, but in code. This means our code has to still read and pass the setting because we will never know if the migration in code has run yet. The `portal_plans` setting has been updated to only include 'free' by default, because the setting must include id's now rather than names.
2021-05-04 17:35:37 +03:00
"defaultValue": "[\"free\"]",
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"type": "array"
Added new settings for portal button customization no issue - Adds new portal settings - `portal_button_style`, `portal_button_icon` and `portal_button_signup_text` - New settings allows customization of portal button - Updates tests to include new settings
2020-07-07 11:02:47 +03:00
},
"portal_button_style": {
"defaultValue": "icon-and-text",
"validations": {
"isEmpty": false,
"isIn": [["text-only", "icon-and-text", "icon-only"]]
},
"type": "string"
},
"portal_button_icon": {
"defaultValue": null,
"type": "string"
},
"portal_button_signup_text": {
"defaultValue": "Subscribe",
"type": "string"
Added new settings for members modal no issue - reverts commit 87c31444fd41d182f3add55f72e0e0fb9cdcc1ff but with modifications to settings naming - Adds new settings for members modal customization to default settings - `portal_button` controls the visibility of beacon in members modal - `portal_name` controls the visibility of name field in signup - `portal_plans` controls the visibility of plans allowed for member to signup with - Adds stripe connect check to determine if stripe is setup or not - Adds the 3 new settings to members site data - Updates to snake case naming for members site API data
2020-06-19 17:04:40 +03:00
}
},
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
"email": {
Added mailgun_{domain,api_key,base_url} settings (#11992) refs #10318 - Adds new default settings - Adds migration for populating settings with bulk_email_settings data - Fixes regression tests
2020-07-03 12:00:20 +03:00
"mailgun_domain": {
"defaultValue": null,
"type": "string"
},
"mailgun_api_key": {
"defaultValue": null,
"type": "string"
},
"mailgun_base_url": {
"defaultValue": null,
"type": "string"
Added "email_track_opens" setting (#12404) refs https://github.com/TryGhost/Ghost/issues/12390 - adds "email_track_opens" setting to the `email` group, defaulting to `true`
2020-11-23 21:36:12 +03:00
},
"email_track_opens": {
"defaultValue": "true",
"validations": {
"isEmpty": false,
"isIn": [["true", "false"]]
},
"type": "boolean"
Added members related db changes and models refs #10213
2018-12-10 12:20:54 +03:00
}
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
},
"amp": {
"amp": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "true",
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
"validations": {
"isIn": [["true", "false"]]
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
},
"type": "boolean"
Added amp_gtag_id setting migration & default refs #11980 This lays the ground for the rest of the work surrounding Google Analytics in AMP.
2020-07-10 16:19:45 +03:00
},
"amp_gtag_id": {
"defaultValue": null,
"type": "string"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
}
},
Added FirstPromoter Integration (#12540) no refs Adds new FirstPromoter settings similar to amp, which allows sites to take advantage of FirstPromoter to launch their own member referral program natively. - Adds new firstpromoter settings group - Adds `firstpromoter` setting to group - Adds `firstpromoter_id` setting to group for FirstPromoter referral tracking id - Updated tests
2021-01-15 16:35:15 +03:00
"firstpromoter": {
"firstpromoter": {
"defaultValue": "false",
"validations": {
"isIn": [
[
"true",
"false"
]
]
},
"type": "boolean"
},
"firstpromoter_id": {
"defaultValue": null,
"type": "string"
}
},
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
"slack": {
🏗 Updated "slack" setting into "slack_{url,username}" refs https://github.com/TryGhost/Ghost/issues/10318 - Object format used in previous "slack" setting was considered an anti-pattern. Flag structure of separate slack_url and slack_username values was extracted out of the "slack" JSON.
2020-07-14 11:12:43 +03:00
"slack_url": {
"defaultValue": "",
"type": "string"
},
"slack_username": {
"defaultValue": "Ghost",
"type": "string"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
}
},
"unsplash": {
"unsplash": {
🏗 Updated "unsplash" setting handling to match updated format refs https://github.com/TryGhost/Ghost/issues/10318 - JSON object format used in previous "unsplash" setting was considered an anti-pattern. Flat structure was extracted out of the "unsplash.isActive" JSON. - The naming convention uses `amp` as a precedent (https://github.com/TryGhost/Team/issues/331#issuecomment-658815017)
2020-07-14 11:16:50 +03:00
"defaultValue": "true",
"validations": {
"isEmpty": false,
"isIn": [["true", "false"]]
},
"type": "boolean"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
}
},
"views": {
"shared_views": {
Updated default settings and schema with updated types refs https://github.com/TryGhost/Ghost/issues/10318 - Updates default settings to contain correct type and validation for each setting - Updates `populateDefaults` to correctly insert type value for new settings - Updates settings schema to allow only select types - `array`, `number`, `boolean`, `string` - `object` is a temporary type allowed till we get rid of all JSON object settings
2020-06-30 15:02:43 +03:00
"defaultValue": "[]",
"type": "array"
Organised default settings into new groups (#11952) refs https://github.com/TryGhost/Ghost/issues/10318 - precursor to migrating from `settings.type` to `settings.group` - renames `blog` type to `site` - renames `bulk_email` type to `email` - moves settings out of `site` (previously `blog`) into more appropriate groups such as `core` or individual feature groups
2020-06-23 22:49:08 +03:00
}
✨ Added newsletter design settings (#12352) refs https://github.com/TryGhost/Ghost/issues/12355 - Adds new default settings for newsletter customisations - `newsletter_show_badge`, `newsletter_show_header` and `newsletter_body_font_category` - Adds migrations to update group for new settings - Add migration to update settings based on existing config value for newsletter settings - Passes new newsletter settings to newsletter template and updates design based on them - Fix tests
2020-11-11 15:56:11 +03:00
},
"newsletter": {
"newsletter_show_badge": {
Enabled newsletter badge by default no issue Updated newsletter badge to be shown by default which was previously set to be hidden. Users can still control the visibility via Email settings in Ghost-Admin
2020-11-16 13:25:05 +03:00
"defaultValue": "true",
✨ Added newsletter design settings (#12352) refs https://github.com/TryGhost/Ghost/issues/12355 - Adds new default settings for newsletter customisations - `newsletter_show_badge`, `newsletter_show_header` and `newsletter_body_font_category` - Adds migrations to update group for new settings - Add migration to update settings based on existing config value for newsletter settings - Passes new newsletter settings to newsletter template and updates design based on them - Fix tests
2020-11-11 15:56:11 +03:00
"validations": {
"isEmpty": false,
"isIn": [
[
"true",
"false"
]
]
},
"type": "boolean"
},
"newsletter_show_header": {
"defaultValue": "true",
"validations": {
"isEmpty": false,
"isIn": [
[
"true",
"false"
]
]
},
"type": "boolean"
},
"newsletter_body_font_category": {
"defaultValue": "sans_serif",
"validations": {
"isEmpty": false,
"isIn": [
[
"serif",
"sans_serif"
]
]
},
"type": "string"
Added setting for newsletter footer content (#12359) no-issue We want to give users to ability to customise the content of their newsletter, and the first step toward that is a setting in which we can store text or html to embed in the template
2020-11-13 16:18:47 +03:00
},
"newsletter_footer_content": {
"defaultValue": "",
"type": "string"
✨ Added newsletter design settings (#12352) refs https://github.com/TryGhost/Ghost/issues/12355 - Adds new default settings for newsletter customisations - `newsletter_show_badge`, `newsletter_show_header` and `newsletter_body_font_category` - Adds migrations to update group for new settings - Add migration to update settings based on existing config value for newsletter settings - Passes new newsletter settings to newsletter template and updates design based on them - Fix tests
2020-11-11 15:56:11 +03:00
}
Added settings keys to store OAuth related data (#12879) refs https://github.com/TryGhost/Team/issues/618 - The `oauth_client_id` and `oauth_client_secret` are placeholders to store OAuths related data. - The flag for `oauth_enabled` or anything along those lines was not added intentionally in favour of checking if the `oauth_client_id` & `oauth_client_secret` are null.
2021-04-16 11:02:21 +03:00
},
"oauth": {
"oauth_client_id" : {
"defaultValue": null,
"type": "string"
},
"oauth_client_secret" : {
"defaultValue": null,
"type": "string"
}
Added default email recipients settings (#12925) refs https://github.com/TryGhost/Team/issues/496 We want to give more control over the default selection of email recipients when publishing a post, to do that we need somewhere to store those settings. These settings are site-wide and intended for use by admins to control the default editor behaviour for all staff users. They _do not_ control API behaviour, if you want to send email when publishing via the API it's still necessary to explicitly opt in to that using the `?email_recipients_filter=` query param. - new `editor` settings group to indicate that these settings only affect the UI rather than the API - `editor_default_email_recipients` controls overall behaviour, string/enum with these allowed values: - `'disabled'`: no option to send email is shown in the editor's publishing dropdown - `'visibility'`: (default) selected member segment is dynamic and matches the post visibility filter - `'filter'`: specific member filter defined in `editor_default_email_recipients_filter` setting - `editor_default_email_recipients_filter` is an NQL string for selecting members, used when `editor_default_email_recipients` is set to `'filter'` - default value is `'all'` - the segment string can be any valid NQL filter with the additional special-case values of `'all'` and `'none'`
2021-05-07 11:30:57 +03:00
},
"editor": {
"editor_default_email_recipients": {
"defaultValue": "visibility",
"type": "string",
"validations": {
"isEmpty": false,
"isIn": [[
"disabled",
"visibility",
"filter"
]]
}
},
"editor_default_email_recipients_filter": {
"defaultValue": "all",
"type": "string"
}
Proper settings infrastructure, allowing new features without compromising old data. On server load, check for settings which have not been set, and apply a default value to the settings table from a JSON file.
2013-09-02 05:49:08 +04:00
}
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
}
Reference in New Issue Copy Permalink