search

rbeckman-nextgen / test-mc3

0 stars 0 forks source link

In installer, if you select an installation directory other than default, that change is not reflected in default app data and logs paths #1755

Closed rbeckman-nextgen closed 4 years ago

rbeckman-nextgen commented 4 years ago

While walking through the setup wizard during installation of MC, on the page that asks you for the destination directory (i.e., the folder into which to install MC), change it to some other folder than the default. For example, instead of using the default "C:\Program Files\Mirth Connect", use "C:\Program Files\Mirth Connect 2.1 RC1". Click the Next button until you get to the page that asks for the paths for application data and the logs. By default, these fields are populated with "C:\Program Files\Mirth Connect\appdata" and "C:\Program Files\Mirth Connect\logs", respectively (in a Windows environment). In my opinion, these paths should, by default, reflect the path provided for the MC installation folder. So, in the example given above, they should instead be "C:\Program Files\Mirth Connect 2.1 RC1\appdata" and "C:\Program Files\Mirth Connect 2.1 RC1\logs".

Imported Issue. Original Details: Jira Issue Key: MIRTH-1791 Reporter: ericb Created: 2011-03-16T17:29:01.000-0700

rbeckman-nextgen commented 4 years ago

Tested this with 2.1.0.5374.b642 and was not able to reproduce.

Imported Comment. Original Details: Author: geraldb Created: 2011-03-17T10:24:15.000-0700

rbeckman-nextgen commented 4 years ago

I'll try to reproduce this in a different environment when I have the chance. But one thing I should note, that I didn't indicate in the original description, is that I already had 2.0.1 installed (in the default \Program Files\Mirth Connect\ folder), and I was installing 2.1 RC1 in addition to the previous version (hence, why I used the different folder). In other words, this was not a "clean" install, with no previous version of MC on the machine. So perhaps it was picking up some property from the existing install?

Imported Comment. Original Details: Author: ericb Created: 2011-03-17T10:50:06.000-0700

rbeckman-nextgen commented 4 years ago

Thanks for update, I was able to reproduce the issue. I installed 2.0.1 and then ran the 2.1 installer, and even when selecting the "install into a different directory" option, it still uses the previous install's directory. Could be a bug with the installer.

Imported Comment. Original Details: Author: geraldb Created: 2011-03-17T10:57:57.000-0700

rbeckman-nextgen commented 4 years ago

I heard a similar issue in the past with the installer. Someone installed 2.0 RC2 into "Mirth Connect 2.0 RC2" and then when trying to install the final release later, the installer automatically suggested "Mirth Connect 2.0 RC2" as the folder instead of "Mirth Connect". They were able to change it, but I'm not sure if the folder kept changing back in the next steps of the installer for the other directories.

Imported Comment. Original Details: Author: jacobb Created: 2011-03-17T14:36:37.000-0700

rbeckman-nextgen commented 4 years ago

Yep, I did some more tests and confirmed that it's a bug with install4j. I went ahead and opened a ticket with them.

Imported Comment. Original Details: Author: geraldb Created: 2011-03-17T14:41:58.000-0700

rbeckman-nextgen commented 4 years ago

Fixed using a suggestion from install4j support.

Imported Comment. Original Details: Author: geraldb Created: 2011-03-18T11:56:58.000-0700