View Issue Details

IDProjectCategoryView StatusLast Update
0002831Composrinstallerpublic2016-10-17 16:03
Reportercupper3Assigned ToChris Graham 
SeverityFeature-request 
Status closedResolutionfixed 
Product Version 
Fixed in Version 
Summary0002831: Potential issue with upgrade to RC 18
DescriptionI have upgraded to RC 18, however, there appeared a glitch with the upgrade that never occured before.

All 316 files installed, and got the check mark. However, even after waiting for a considerable time (5-6 minutes), the "Done" never appeared. I pressed 'continue' any ways, and everything appears to be working fine. You may want to see if you can replicate this, as obviously I can not now.
TagsNo tags attached.
Time estimation (hours)
Sponsorship open

Relationships

has duplicate 0002892 closedChris Graham Done message when upgrading 
has duplicate 0002907 closedChris Graham Upgrader Instruction isn't true. 

Activities

Patrick Schmalstig

2016-09-19 05:54

administrator   ~0004338

Confirmed on wwsu1069.org during its upgrade process

Chris Graham

2016-09-20 16:53

administrator   ~0004341

Last edited: 2016-09-20 16:56

View 2 revisions

Hi, so it always showed the loading bar graphic at the top, and kept refreshing, even after all files were checked?

Chris Graham

2016-09-20 17:13

administrator   ~0004342

Ok. It actually worked fine, and did say Done!, but I checked and I removed it duplicating at top (above files) and bottom. But I should have removed it from Top, not from Bottom. Fixed.

cupper3

2016-10-15 01:51

reporter   ~0004429

Same issue occurred again in RC 19 update. No "Done" after all files are checkmarked.

cupper3

2016-10-15 01:51

reporter  

Patrick Schmalstig

2016-10-15 23:42

administrator   ~0004430

Confirmed on wwsu1069.org . Again, done! appears at the top and not the bottom. However, it may be because 10RC19 has the fix, but obviously the fix is not applied until after the upgrader completes.

Chris Graham

2016-10-17 16:03

administrator   ~0004434

"However, it may be because 10RC19 has the fix, but obviously the fix is not applied until after the upgrader completes." correct

Issue History

Date Modified Username Field Change
2016-09-19 05:43 cupper3 New Issue
2016-09-19 05:54 Patrick Schmalstig Note Added: 0004338
2016-09-20 16:53 Chris Graham Note Added: 0004341
2016-09-20 16:56 Chris Graham Note Edited: 0004341 View Revisions
2016-09-20 17:13 Chris Graham Note Added: 0004342
2016-09-20 17:13 Chris Graham Status non-assigned => resolved
2016-09-20 17:13 Chris Graham Resolution open => fixed
2016-09-20 17:13 Chris Graham Assigned To => Chris Graham
2016-10-15 01:51 cupper3 Note Added: 0004429
2016-10-15 01:51 cupper3 Status resolved => @20@
2016-10-15 01:51 cupper3 Resolution fixed => reopened
2016-10-15 01:51 cupper3 File Added: Screenshot 2016-10-14 at 11.18.30 AM.png
2016-10-15 23:42 Patrick Schmalstig Note Added: 0004430
2016-10-17 16:03 Chris Graham Note Added: 0004434
2016-10-17 16:03 Chris Graham Status @20@ => closed
2016-10-17 16:03 Chris Graham Resolution reopened => fixed
2016-10-20 23:55 Chris Graham Relationship added has duplicate 0002892
2016-10-29 17:00 Chris Graham Relationship added has duplicate 0002907