tootlab-mastodon/app/views/settings/shared/_links.html.haml

%ul.no-list
  - if controller_name != 'profiles'
    %li= link_to t('settings.edit_profile'), settings_profile_path
  - if controller_name != 'preferences'
    %li= link_to t('settings.preferences'), settings_preferences_path
  - if controller_name != 'registrations'
    %li= link_to t('auth.change_password'), edit_user_registration_path
  - if controller_name != 'two_factor_authentications'
    %li= link_to t('settings.two_factor_authentication'), settings_two_factor_authentication_path
  %li= link_to t('settings.back'), root_path
E-mail preferences page 2016-10-13 20:28:49 -04:00			`%ul.no-list`
			`- if controller_name != 'profiles'`
Adding some localizations 2016-11-15 17:02:57 -05:00			`%li= link_to t('settings.edit_profile'), settings_profile_path`
E-mail preferences page 2016-10-13 20:28:49 -04:00			`- if controller_name != 'preferences'`
Adding some localizations 2016-11-15 17:02:57 -05:00			`%li= link_to t('settings.preferences'), settings_preferences_path`
E-mail preferences page 2016-10-13 20:28:49 -04:00			`- if controller_name != 'registrations'`
Adding some localizations 2016-11-15 17:02:57 -05:00			`%li= link_to t('auth.change_password'), edit_user_registration_path`
2FA controller cleanup (#2296) * Add spec coverage for settings/two_factor_auth area * extract setup method for qr code * Move otp required check to before action * Merge method only used once * Remove duplicate view * Consolidate creation of @codes for backup * Move settings/2fq#recovery_codes to settings/recovery_codes#create * Rename settings/two_factor_auth#disable to #destroy * Add coverage for the otp required path on 2fa#show * Clean up the recovery codes list styles * Move settings/two_factor_auth to settings/two_factor_authentication * Reorganize the settings two factor auth area Updated to use a flow like: - settings/two_factor_authentication goes to a #show view which has a button either enable or disable 2fa on the account - the disable button turns off the otp requirement for the user - the enable button cycles the user secret and redirects to a confirmation page - the confirmation page is a #new view which shows the QR code for user - that page posts to #create which verifies the code, and creates the recovery codes - that create action shares a view with a recovery codes controller which can be used separately to reset codes if needed 2017-04-21 22:23:17 -04:00			`- if controller_name != 'two_factor_authentications'`
			`%li= link_to t('settings.two_factor_authentication'), settings_two_factor_authentication_path`
Added optional two-factor authentication 2017-01-27 14:28:46 -05:00			`%li= link_to t('settings.back'), root_path`