Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


The problem was at least indentified, is the unoxmlmi.dll.
Like a previous post, a interim solution was replace the unoxmlmi.dll from 
OpenOffice 3.3 version in LO 3.3.1

https://bugs.freedesktop.org/show_bug.cgi?id=33701




________________________________
De: Eli <j.eli.r@verizon.net>
Para: users@libreoffice.org
Enviado: sáb,26 febrero, 2011 16:57
Asunto: Re: Re: [libreoffice-users] [LO 3.3.1] Crash upon update extension -- 
EMULATE FIREFOX!

In my experience this problem has existed for years in OOo.

In OOo, I select Help \ Check for update, and OOo *always* reports "update 
failed". This happens even when there is a newer stable release on the download 
page. In LibO 3.3.x Help \ Check for update tool is missing altogether -- I take 

this as an admission that it was buggy and will be fixed by the by.

In OOo, I select Tools \ Extension Manager \ Check for Updates. Half the time 
OOo reports "update failed". When it did show a list of updates, sometimes they 
came down, sometimes they did not. In LibO 3.3.x, Tools \ Extension Manager \ 
Check for updates *always* causes LibO to crash, with an offer to save the open 
documents. (Usually I update with no open documents -- why tempt evil gods?)

So the LibO developers have their work cut out on the whole update mess. If I 
can put my two cents in, I would prioritize it this way:

1. Make sure that update checking actually identifies whether updates are 
available. If so, offer to link to the update page for manual downloading and 
installing (which is better than crashing). If not, report that.

2. When that works dependably, the update checker should download the update 
package and offer to install manually.

3. Make an option in the Tools \ Options box for automatic notification of 
updates. The notice should provide you with a button to download and install. 
This way you will usually learn about an update the first time you open LibO 
after an update is posted.

4. The option in the Tools \ Options box should allow the option for downloading 

in the background. When the download is ready, A dialog should appear with a 
button to install the update.

5. At least for updates and minor upgrades, you should download just the changed 

files, Registry entries, settings, etc. This will greatly decrease your 
bandwidth requirements, saving money for TDF and time for us users.

Emulate the Firefox update system! Get someone from Mozilla to help.

These changes will help users keep their LibO up-to-date and bug-free. As you 
increase use of Java and VBA, it will help fight malware. It will also help to 
distinguish LibO from OOo.


      

-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.