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

135 lines
3.8 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": {
Fix 'dbHash' not found closes #1685 - changed dbHash initialization from db direct access to api access - added dbHash to default-settings.json - added dbHash to tests
2013-12-16 14:16:06 +04:00
"defaultValue": null
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
},
🎨 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": {
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
"defaultValue": null
},
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": {
Support for custom notifications (#7077) closes #5071 - Send application/json requests to UpdateCheck service. New UpdateCheck service accepts JSON request - If UpdateCheck service respponse has messages[] array, iterate over the array and create custom notifications intended for current version - Save custom notification if its not already in the store AND its uuid is not in seenNotifications array - When a custom notification is dismissed, store its uuid in seenNotifications array - setup test fixtures to trigger tests properly - api_notification_spec test to ensure custom notification can be added to store and added to seenNotifications when dismissed - update_check_spec test to ensure custom notification can be displayed for a specific Ghost version - added test to ensure messages meant for other versions don't create notifications
2016-07-22 16:02:10 +03:00
"defaultValue": "[]"
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": {
"defaultValue": null
Updating settings types - issue #573, issue #632
2013-09-14 22:04:41 +04:00
}
},
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
"blog": {
"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
}
}
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
"description": {
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": "The professional publishing platform",
"validations": {
"isLength": {
"max": 200
}
}
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
"logo": {
Changed casper.ghost.org to static.ghost.org references (#10109) no issue Assets moved from gh-pages to https://github.com/tryghost/static and hostname changed, redirects already in place. Can be tested on https://demo.ghost.io (image should all work fine, try visiting one directly to verify redirect works)
2018-11-07 17:50:38 +03:00
"defaultValue": "https://static.ghost.org/v1.0.0/images/ghost-logo.svg"
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": {
Changed casper.ghost.org to static.ghost.org references (#10109) no issue Assets moved from gh-pages to https://github.com/tryghost/static and hostname changed, redirects already in place. Can be tested on https://demo.ghost.io (image should all work fine, try visiting one directly to verify redirect works)
2018-11-07 17:50:38 +03:00
"defaultValue": "https://static.ghost.org/v1.0.0/images/blog-cover.jpg"
✨ 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": {
✨ 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
"defaultValue": ""
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
},
🎨 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
"default_locale": {
"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
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
}
},
🎨 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_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
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
}
},
🎨 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
"force_i18n": {
Renaming default to defaultValue as default is reserved
2013-09-15 01:39:31 +04:00
"defaultValue": "true",
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 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
"isIn": [["true", "false"]]
Restructure default-settings.json and add validations to important settings.
2013-09-02 05:49:08 +04:00
}
Add Customisable Permalinks
2013-11-21 22:44:18 +04:00
},
"permalinks": {
"defaultValue": "/:slug/",
"validations": {
Update validator to 3.4.0 Closes #1379 - Convert to new api usage for both server-side and client-side - Provide way require a negative response for boolean methods in default-settings.json - Add field validation functional tests - Settings (General) - Title length validation - Description length validation - postsPerPage, numeric, min, max - Settings (User) - Bio Length validation - Location length validation - Url validation - Login - Email validation - Editor - Title required validation
2014-02-28 10:51:52 +04:00
"matches": "^(\/:?[a-z0-9_-]+){1,5}\/$",
✨ Multiple authors (#9426) no issue This PR adds the server side logic for multiple authors. This adds the ability to add multiple authors per post. We keep and support single authors (maybe till the next major - this is still in discussion) ### key notes - `authors` are not fetched by default, only if we need them - the migration script iterates over all posts and figures out if an author_id is valid and exists (in master we can add invalid author_id's) and then adds the relation (falls back to owner if invalid) - ~~i had to push a fork of bookshelf to npm because we currently can't bump bookshelf + the two bugs i discovered are anyway not yet merged (https://github.com/kirrg001/bookshelf/commits/master)~~ replaced by new bookshelf release - the implementation of single & multiple authors lives in a single place (introduction of a new concept: model relation) - if you destroy an author, we keep the behaviour for now -> remove all posts where the primary author id matches. furthermore, remove all relations in posts_authors (e.g. secondary author) - we make re-use of the `excludeAttrs` concept which was invented in the contributors PR (to protect editing authors as author/contributor role) -> i've added a clear todo that we need a logic to make a diff of the target relation -> both for tags and authors - `authors` helper available (same as `tags` helper) - `primary_author` computed field available - `primary_author` functionality available (same as `primary_tag` e.g. permalinks, prev/next helper etc)
2018-03-27 17:16:15 +03:00
"matches": "(:id|:slug|:year|:month|:day|:author|:primary_tag|:primary_author)",
Add Customisable Permalinks
2013-11-21 22:44:18 +04:00
"notContains": "/ghost/"
}
adds code injection admin frontend implementation, handlebar helpers + settings escaping handlebars
2014-07-31 23:36:20 +04:00
},
⚡❓ Make AMP optional (#7830) closes #7769 Because Google AMP is bitching around and shows errors in Googles' webmaster tools for missing post images and blog icons, we decided to make AMP optional. It will be enabled by default, but can be disabled in general settings. Once disabled, the `amp` route doesn't work anymore. This PR contains the back end changes for Ghost-alpha: - Adds `amp` to settings table incl default setting `true` - Adds `amp` value to our settings cache - Changes the route handling of AMP app to check for the `amp` setting first. - Adds tests to check the route handling and ghost_head output - Includes changes to `post-lookup.js` as done by @kirrg001 in #7842
2017-01-17 18:40:06 +03:00
"amp": {
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" : "true",
"validations": {
"isIn": [["true", "false"]]
}
⚡❓ Make AMP optional (#7830) closes #7769 Because Google AMP is bitching around and shows errors in Googles' webmaster tools for missing post images and blog icons, we decided to make AMP optional. It will be enabled by default, but can be disabled in general settings. Once disabled, the `amp` route doesn't work anymore. This PR contains the back end changes for Ghost-alpha: - Adds `amp` to settings table incl default setting `true` - Adds `amp` value to our settings cache - Changes the route handling of AMP app to check for the `amp` setting first. - Adds tests to check the route handling and ghost_head output - Includes changes to `post-lookup.js` as done by @kirrg001 in #7842
2017-01-17 18:40:06 +03:00
},
adds code injection admin frontend implementation, handlebar helpers + settings escaping handlebars
2014-07-31 23:36:20 +04:00
"ghost_head": {
"defaultValue" : ""
},
"ghost_foot": {
"defaultValue" : ""
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": {
🎨 Changed fixture data and default settings (#9778) closes #9774, refs #9742 - added new fixture posts for Ghost 2.0 - added migration file to remove old fixture posts - only remove them if they are owned by the Ghost author and if they are tagged with getting-started - added new fixture posts if you had all (!) old fixture posts - ensure on rollback we remove the new fixture posts again - updated default settings
2018-08-10 14:55:03 +03:00
"defaultValue" : "ghost"
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": {
🎨 Changed fixture data and default settings (#9778) closes #9774, refs #9742 - added new fixture posts for Ghost 2.0 - added migration file to remove old fixture posts - only remove them if they are owned by the Ghost author and if they are tagged with getting-started - added new fixture posts if you had all (!) old fixture posts - ensure on rollback we remove the new fixture posts again - updated default settings
2018-08-10 14:55:03 +03:00
"defaultValue" : "tryghost"
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
},
Start of labs issue #4409
2014-12-14 20:56:04 +03:00
"labs": {
💡 Disabled v0.1 Public API by default (#10372) refs #10364
2019-01-15 13:09:34 +03:00
"defaultValue": "{}"
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 docs links to best equivalents (#10386) * Updated docs links to best equivalents - Our documentation has been overhauled, this updates the all the old links sprinkled through Ghost * Update integrity hash
2019-01-17 09:57:37 +03:00
"defaultValue": "[{\"label\":\"Home\", \"url\":\"/\"},{\"label\":\"Tag\", \"url\":\"/tag/getting-started/\"}, {\"label\":\"Author\", \"url\":\"/author/ghost/\"},{\"label\":\"Help\", \"url\":\"https://docs.ghost.org\"}]"
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
},
"slack": {
Added Slack username option. (#10285) refs #9735.
2018-12-14 14:57:32 +03:00
"defaultValue": "[{\"url\":\"\", \"username\":\"Ghost\"}]"
Add `configuration/private` endpoint and settings for Unsplash (#8895) refs #8859 - adds new `configuration/private` endpoint for exposing config that should not be accessible without authentication - adds `unsplashAPI` to private config - adds empty `unsplash` config to default settings
2017-08-15 17:59:16 +03:00
},
"unsplash": {
🎨 Enabled Unsplash by default refs https://github.com/TryGhost/Ghost/issues/8859 There are four cases: - unsplash setting is empty (default), admin can enable the app by default (hardcoded isActive:true) - unsplash settings are set, unsplash is disabled, admin detects that app was disabled on purpose - unsplash setting is set, unsplash is enabled and has a key, app is enabled, old key get's ignored and overridden on the next save - unsplash setting is set, unsplash is enabled and has no key, app is enabled
2017-09-19 12:56:45 +03:00
"defaultValue": "{\"isActive\": true}"
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": {
Renaming default to defaultValue as default is reserved
2013-09-15 01:39:31 +04:00
"defaultValue": "casper"
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"]]
}
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": {
"defaultValue": ""
✨ 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": {
"defaultValue": null
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": {
"members_public_key": {
"defaultValue": null
},
"members_private_key": {
"defaultValue": null
},
"members_session_secret": {
"defaultValue": null
Refactored members auth flow with dynamic settings no issue - Updated members auth flow UI - Updated members settings and routing to be dynamic
2019-02-26 06:09:16 +03:00
},
"members_subscription_settings": {
"defaultValue": "{\"isPaid\":false,\"paymentProcessors\":[{\"adapter\":\"stripe\",\"config\":{\"secret_token\":\"\",\"public_token\":\"\",\"product\":{\"name\":\"Ghost Subscription\"},\"plans\":[{\"name\":\"Monthly\",\"currency\":\"usd\",\"interval\":\"month\",\"amount\":\"\"},{\"name\":\"Yearly\",\"currency\":\"usd\",\"interval\":\"year\",\"amount\":\"\"}]}}]}"
Added members related db changes and models refs #10213
2018-12-10 12:20:54 +03:00
}
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