You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The setup process has 'blog title' which is additional to the old signup process. This will need validating and wiring up to get saved on the server side.
On the server side, the blog.description should be automatically set to: "Thoughts, stories and ideas by [user.name]"
Everything else should work exactly as per the old signup screen, the user should be created and automatically logged in, the welcome email should be sent, etc.
Question: should the setup be posted to an admin route, or do we need to move this onto the API? I'd say leave it as an admin route for now.
Note: the routes mentioned assume the ember admin is now the default, but that doesn't have to be done first.
The text was updated successfully, but these errors were encountered:
fixesTryGhost#3072
- Change router to handle /ember/setup/
- Adjust doSignup to also handle setup
- Adjust tests and add new where necessary
- Add setup controller, setup validation, setup route
- Adjust casper emberSetup to handle new setup
I'm sorry, and I hate when this happens but I have missed this question:
Question: should the setup be posted to an admin route, or do we need to move this onto the API? I'd say leave it as an admin route for now.
Yes it should be moved to the API. By the time we have finished the ember admin the admin controller should ideally consist of only a single controller for the index page to load the Ember client. All other actions are going to target the API.
When all this work is finished it will be theoretically possible to serve the Ember admin from a simple web server and all necessary data is fetched from the API.
I'll open an issues for that. The change is mostly for consistency and not urgent.
Replacing the old issue: #1794
Question: should the setup be posted to an admin route, or do we need to move this onto the API? I'd say leave it as an admin route for now.
Note: the routes mentioned assume the ember admin is now the default, but that doesn't have to be done first.
The text was updated successfully, but these errors were encountered: