The --noprofile option may be used when the shell is started to inhibit this behavior.The Update Profile page allows the logged in user to update his/her profile. If the user wants to update or change his/her profile in the registration form, user has to click on the "Update Profile" link on the web browser.
Based on my research it seems doable but I wanted to know if anyone has already done something like this before.
So as your controller is namespaced you have to add a \ before Input to reference the root namespace ( or put a use statement on top of your class) Generally on your development server you should enable debugging.
Yes, I know how to puzzle through the documentation and learn when each file is or isn't loaded.
What I'm wondering is if anyone has every put together comprehensive guidelines for how to decide which file to put a given type of customization in.
When a logged on user clicks on the Update Profile links the following update profile pages is displayed.