Hi,

Displaying this error message in frontend (esp. when it blocks the frontend) 
simply is a bug and now it's written in bugtrack:
https://bugs.oxid-esales.com/view.php?id=2356

Fix will be included in next Patch.

But, as best practices, during updates we suggest to put shop to "temporary 
offline" mode and, even better, test update on some copy of live eShop at first.


Best regards,
Dainius Bigelis


________________________________
From: [email protected] 
[[email protected]] on behalf of anzido GmbH 
[[email protected]]
Sent: Thursday, December 30, 2010 11:54 AM
To: OXID eSales AG, dev-general
Subject: Re: [oxid-dev-general] updateApp warning message [T-O8VKTSAZSO-37]

Hi Dainius,

I know that the updateApp usually deletes itself (or its contents) after the 
update. What I meant was the message that you see in the frontend while the 
updateApp is on the server.
We have some shops with so much traffic that I fear it will be irritating to 
the users to see the message in the frontend while I run the updateApp. 
Therefore I would rather have the message about the updateApp only in the admin 
backend and not in visible in the frontend.

>From my point of view the shop customers should not notice at all that an 
>update is being done on the server, except maybe that the shop is a bit slower 
>because some database tables are being updated... ;-)

Beste Grüße aus Dortmund!
Robert Rosendahl | Entwicklung u. Support

--
anzido GmbH
Kirchhörder Str. 12
44229 Dortmund
Tel.: 0231 - 60 71 079
Fax.: 0231 - 60 71 081
Mobil:0176 - 8325 1488
Email: [email protected]<mailto:[email protected]>
Web:   http://www.anzido.com<http://www.anzido.com/>

USt-ID: DE257982972
Geschäftsführung: Andreas Ziethen
Amtsgericht Dortmund HRB 20883


-----Ursprüngliche Daten-----
Datum: 29.12.2010 16:37:16
Von: Dainius Bigelis <[email protected]>
An: [email protected] <[email protected]>
Betreff: RE: [oxid-dev-general] updateApp warning message
Vorgang: T-O8VKTSAZSO-37

hi,

We found your message in dev-general about this case.
Could you please tell more about the case when you still get this error message 
in frontend?
- Between what versions you made an update?
- what rights/permissions are set on this dir during update?
- update went properly, just files left not deleted? (as we have implemented 
the deleting also)?

Because I cannot reproduce this localy (getting message only in Admin or just 
after update is done, in the same UpdateApp screen).
And in some of latest Shop versions we have fixed some bugs related to that... 
if there is still something left, would be good to polish that behavior...

Best regards,
Dainius Bigelis


_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to