-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Settings (Desktop/Mobile/Everything) #3
Milestone
Comments
ghost
assigned ErisDS
May 7, 2013
This is done. New issues for anything specific. |
ErisDS
pushed a commit
that referenced
this issue
Mar 30, 2014
[Translations: /pt-BR] Portuguese translation for Ghost documentation
cobbspur
pushed a commit
to cobbspur/Ghost
that referenced
this issue
May 18, 2015
kirrg001
added a commit
to kirrg001/Ghost
that referenced
this issue
Feb 15, 2018
no issue - `isNew` does not work in Ghost, because Ghost does not use auto increment id's - see bookshelf/bookshelf#1265 - see https://github.com/bookshelf/bookshelf/blob/0.10.3/src/base/model.js#L211 - we only had one occurance, which was anyway redundant - if you add a user, `hasChanged('password') is true - if you edit a user and the password has changed, `hasChanged('password')` is true as well NOTE #1: 1. We can't override `isNew` and throw an error, because bookshelf makes use of `isNew` as well, but it's a fallback if `options.method` is not set. 2. It's hard to re-implement `isNew` based on `options.method`, because then we need to ensure that this value is always set (requires a couple of changes) NOTE TryGhost#2: If we need to differentiate if a model is new or edited, we should manually check for `options.method === insert`. NOTE TryGhost#3: The unit tests are much faster compared to the model integration tests. I did a comparision with the same test assertion: - unit test takes 70ms - integration test takes 190ms
kirrg001
added a commit
that referenced
this issue
Feb 15, 2018
no issue - `isNew` does not work in Ghost, because Ghost does not use auto increment id's - see bookshelf/bookshelf#1265 - see https://github.com/bookshelf/bookshelf/blob/0.10.3/src/base/model.js#L211 - we only had one occurance, which was anyway redundant - if you add a user, `hasChanged('password') is true - if you edit a user and the password has changed, `hasChanged('password')` is true as well NOTE #1: 1. We can't override `isNew` and throw an error, because bookshelf makes use of `isNew` as well, but it's a fallback if `options.method` is not set. 2. It's hard to re-implement `isNew` based on `options.method`, because then we need to ensure that this value is always set (requires a couple of changes) NOTE #2: If we need to differentiate if a model is new or edited, we should manually check for `options.method === insert`. NOTE #3: The unit tests are much faster compared to the model integration tests. I did a comparision with the same test assertion: - unit test takes 70ms - integration test takes 190ms
khuevu
pushed a commit
to khuevu/Ghost
that referenced
this issue
Sep 17, 2019
khuevu
pushed a commit
to khuevu/Ghost
that referenced
this issue
Oct 8, 2019
Ph1eu
added a commit
to USTH-Coders-Club/Ghost
that referenced
this issue
Sep 14, 2022
daniellockyer
pushed a commit
that referenced
this issue
Jun 22, 2023
refs TryGhost/Product#1695 This allows theme developers to customise the output via the {{comments}} helper
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User story for settings management. This is the main screen - http://cl.ly/O6v7
Tablet workflow: Exactly the same, but smaller columns http://cl.ly/O6sC
Mobile workflow: Split into 2 pages, like other screens detailed http://cl.ly/O7TY
The text was updated successfully, but these errors were encountered: