Closed
Bug 564515
Opened 15 years ago
Closed 15 years ago
migration wizard defaults to "do not sync" on fresh 2.0.0.24 profile
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(blocking-thunderbird3.1 rc1+, thunderbird3.1 rc1-fixed, blocking-thunderbird3.0 .5+, thunderbird3.0 .5-fixed)
People
(Reporter: dmosedale, Assigned: bwinton)
References
Details
Attachments
(3 files)
1.44 KB,
patch
|
asuth
:
review+
standard8
:
approval-thunderbird3.0.5+
|
Details | Diff | Splinter Review |
44.20 KB,
image/png
|
Details | |
136.51 KB,
image/jpeg
|
Details |
1. create a fresh profile using Thunderbird 2.0.0.24
2. configure an IMAP account (I've been using my .Mac account)
3. exit Thunderbird 2
4. start a recent 1.9.2 build on that same profile (I've been using a self-built build form yesterday).
5. click "Next" in the migration wizard
6. "Do not synchronize" is the radiobutton selected. "Synchronize" is what should be selected.
Assignee | ||
Comment 1•15 years ago
|
||
Yup, I think it's all pretty much contained in the patch.
Tested locally with a TB2 profile with a server's offline_download pref set to true, false, and left unset.
Later,
Blake.
Attachment #444544 -
Flags: review?(bugmail)
Assignee | ||
Updated•15 years ago
|
Whiteboard: [patch up, needs r asuth]
Assignee | ||
Comment 2•15 years ago
|
||
Oh, and since this is related to profile migration we do at startup, I think it'll be a royal pain to test with Mozmill, which is most of why I didn't add Mozmill tests for it. It should also be partially tested with bug 560741, although the relevant test there isn't failing for me, and I'm not quite sure why. (Possibly because we test to see whether it's an nsIImapIncomingServer in Mozmill, thus triggering the fixed attribute access.)
Thanks,
Blake.
Status: NEW → ASSIGNED
Updated•15 years ago
|
Attachment #444544 -
Flags: review?(bugmail) → review+
Assignee | ||
Updated•15 years ago
|
Whiteboard: [patch up, needs r asuth] → [patch up, needs landing]
Assignee | ||
Comment 3•15 years ago
|
||
Pushed as:
http://hg.mozilla.org/comm-central/rev/e40e64d6ab6a
http://hg.mozilla.org/releases/comm-1.9.2/rev/562372248daa
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
status-thunderbird3.1:
--- → rc1-fixed
Resolution: --- → FIXED
Whiteboard: [patch up, needs landing]
Assignee | ||
Comment 4•15 years ago
|
||
Comment on attachment 444544 [details] [diff] [review]
Initial cut at the patch.
This affects 3.0 as well, because it took the patch from bug 562589.
Attachment #444544 -
Flags: approval-thunderbird3.0.5?
Updated•15 years ago
|
blocking-thunderbird3.0: --- → .5+
Updated•15 years ago
|
Attachment #444544 -
Flags: approval-thunderbird3.0.5? → approval-thunderbird3.0.5+
Comment 5•15 years ago
|
||
Landed on 1.9.1 (3.0.5 relbranch as well):
http://hg.mozilla.org/releases/comm-1.9.1/rev/8b36b51680a6
http://hg.mozilla.org/releases/comm-1.9.1/rev/c4b1d9c9fb5f
status-thunderbird3.0:
--- → .5-fixed
![]() |
||
Comment 6•15 years ago
|
||
It now seems to be set to "synchronize" but I have _two_ migration assistants popping up in 3.0.5 build 2! (I only have 1 IMAP gmail account, nth10sd at gmail, and the default Local Folders from the TB 2.0.0.24 that I tested from)
Is this intended? (If it is, this can be verified)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
![]() |
||
Comment 7•15 years ago
|
||
Here's a screenshot with build 1. Double migration assistant seems to be another bug (I haven't yet searched) but seems that this very bug was indeed fixed. Verifying.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100510 Thunderbird/3.0.5
![]() |
||
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → 3.0
You need to log in
before you can comment on or make changes to this bug.
Description
•