To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104452


User mav changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------
                 Summary|Let macros be deactivated |Let macros be deactivated 
                        |after crash-recovery and a|after repairing of corrupt
                        |fter repairing of corrupte|ed documents.
                        |d documents.              |
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Mon Aug 31 11:51:42 +0000 
2009 -------
The crash-recovery change is a little bit problematic, the problem is that the
system-recovery ( documents recovery after system shut-down ) the same
implementation. So the change should be done later very carefully to avoid
side-effects. I have opened a separated issue 104651 for this and have set the
tarted for OOo3.x for now.

This issue is now only about repairing of corrupted documents. The repaired
documents have the macros disabled now.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to