Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

Do we still need the AMO migration feature? #6123

Closed
shane-tomlinson opened this issue Apr 26, 2018 · 0 comments · Fixed by #6131
Closed

Do we still need the AMO migration feature? #6123

shane-tomlinson opened this issue Apr 26, 2018 · 0 comments · Fixed by #6131
Assignees

Comments

@shane-tomlinson
Copy link

Are AMO migrations still happening? I came across the text Looking for your Add-ons data? Sign up for a Firefox Account with your old Add-ons account email address in our templates today. If the feature's not being used, I'd like to kill it.

<div class="info nudge" id="amo-migration">{{#t}}Looking for your Add-ons data? Sign up for a Firefox Account with your old Add-ons account email address.{{/t}}</div>

@shane-tomlinson shane-tomlinson changed the title Do we still need the "AMO migration" feature? Do we still need the AMO migration feature? Apr 26, 2018
shane-tomlinson pushed a commit that referenced this issue Apr 27, 2018
`migration=amo` will not cause an error, but no special
help text is displayed either. The value is dropped on
the ground.

fixes #6123
@ghost ghost assigned shane-tomlinson Apr 27, 2018
@ghost ghost added the waffle:active label Apr 27, 2018
shane-tomlinson pushed a commit that referenced this issue Apr 30, 2018
`migration=amo` will not cause an error, but no special
help text is displayed either. The value is dropped on
the ground.

fixes #6123
vladikoff pushed a commit that referenced this issue Apr 30, 2018
…dikoff

`migration=amo` will not cause an error, but no special
help text is displayed either. The value is dropped on
the ground.

fixes #6123
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant