From Jules at Zend.To Thu Jan 2 10:15:30 2014 From: Jules at Zend.To (Jules) Date: Thu, 02 Jan 2014 10:15:30 +0000 Subject: [ZendTo] Re: [Updating/Upgrading virtual appliance + documentation hint] In-Reply-To: <52B44A8C.1070505@pcfreak.de> References: <52B44A8C.1070505@pcfreak.de> Message-ID: <52C53C42.80203@Zend.To> On 20/12/2013 13:47, Der PCFreak wrote: > Hi all, > > I setup ZendTo based on the downloadable virtual appliance based on CentOS > > ZendTo-CentOS6-x64-4.11-6.ova > > My installation is now fully configured and online. > > My question is, can I upgrade the entire system with yum so that I have > everything up-to-date > without breaking functionality. Yes, you can. Nothing in /opt/zendto/config/* /opt/zendto/templates/*.tpl /opt/zendto/www/css/local.css will be overwritten when you do a "yum upgrade". So you can customise the user interface as much as you like, without causing any issues when you apply updates. Jules. > > I want to do a > > yum check-update > yum update > > and if possible > > yum upgrade > > Any help with my approach. > > Also I have some information, that might be useful for other users of > the appliance and should in my opinion be added to the online documentation. > > When deploying the ova template to an ESX server, you have to delete the > file > > /etc/udev/rules.d/70-persistent-net.rules > > and reboot to make the system detect the (new) network cards. > > Nice and powerful product. - Thanks! > > Kind regards > > PCFreak > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://mailman.ecs.soton.ac.uk/mailman/listinfo/zendto > > Jules > > -- > Julian Field MEng MBCS CITP CEng > > 'It's okay to live without all the answers' - Charlie Eppes, 2011 > > www.Zend.To > Twitter: @JulesFM > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654 From Jules at Zend.To Thu Jan 2 11:15:28 2014 From: Jules at Zend.To (Jules) Date: Thu, 02 Jan 2014 11:15:28 +0000 Subject: [ZendTo] Re: FW: Issue with Chrome browser - "Leave this Page" In-Reply-To: <52B065EC.7030901@Zend.To> References: <694F0A1F4B1C6D4BABA561C7D9A476C60E3D2931@MAILEX1.nbi.ac.uk> <52B065EC.7030901@Zend.To> Message-ID: <52C54A50.4020006@Zend.To> I've got a quick fix for this. Unfortunately it means you can navigate away from (and hence abort) a running upload, but it stops the Chrome warning, so is better than nothing. You want to edit /opt/zendto/templates/new_dropoff.tpl Find the start of the "submitform" function, and add the last line of this little code snippet: