BUG? ispconfig_update.sh destroys GUI port setting

My ISPconfig under Ubuntu 14.04.x LTS was set to port 10000 for web access and was working well.

While trying to update it from 3.0.5.4p6 to 3.0.5.4p8 with ispconfig_update.sh, I noticed that the usual question regarding the web port was missing. Why? (As far as I remember, it's normally part of the dialog, showing the current setting as default.)

After completion of the update, I found all port specifications in /etc/apache2/sites-available/ispconfig.vhost set to 8080 without any prompt for confirmation. A bug? I can't imagine that such behavior is intended.
Re-editing all occurences in 000-ispconfig.conf back to 10000 and restarting Apache seems to correct the problem, but is this really enough, or are there more locations elsewhere which need to be changed?

The update script does not alter the port setting, it shows it during update and you can confirm or alter it during update. I updated already quite a few client systems with custom ports to p8 and on all systems the custom port was not altered.

The update script does not alter the port setting, it shows it during update and you can confirm or alter it during update.

Click to expand...

That's exactly what I knew from other installations and what I was expecting, but in this case, I swear that it didn't show this prompt, and the port has been reset to 8080 arbitrarily.
As it is a virtualbox machine, it took me only a click to return to an earlier snapshot, so I could run the update again just now. Here is the complete dialog (I was confirming the defaults at all prompts):

The initial if-condition does not only control the port cutomization, but also the prompt regarding the SSL certificate. At this point, I noticed that the latter was also missing in my update process! So the problem seems to depend on this if-condition. Due to insufficient insight, I can't draw more conclusions for now, but maybe this concretion is helpful.

I inspected also the log of the update process found in /var/log/ispconfig_install.log, but as far as I can see, there is nothing suspect. (I can't post the log here due to character count limitations.) I compared it also with another server's update log and didn't find noticeable differences. (This other server [Debian 6.0 LTS] behaved completely normal during update, it showed also the port and certificate prompts and respected my settings.)

Haha! The webserver box is (intendedly!) not checked on this system. But obviously, this setting is not meant to disable the web access to ISPconfig itself. (At least, it doen't.) Consequently, it should also not impact the GUI port setting in such a "destructive" way during update. I tend to consider this as a bug.
Im my opinion, both prompts (port / certificate generation) should always be shown during update, regardless of the "webserver" setting inside, as both are also regarding the ISPconfig web access itself.

By the way, I found another small (but harmless) "flaw" in /usr/local/ispconfig/server/scripts/update_from_tgz.sh: it contains the lines

...but the second rm command can't work as intended, as it seems to be executed from a just-erased directory and won't reach the ISPConfig-3-stable.tar.gz which is in /tmp. A cd /tmp should be inserted before the rm commands.