Issue 106091 - Deleted macros causes security pop-up appear on document open
Summary: Deleted macros causes security pop-up appear on document open
Alias: None
Product: Calc
Classification: Application
Component: editing (show other issues)
Version: OOo 3.1.1
Hardware: PC Windows XP
: P2 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
Depends on:
Reported: 2009-10-20 13:54 UTC by cryonyx
Modified: 2012-03-01 13:01 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---
1983-01-06: 3.4_release_blocker?


Note You need to log in before you can comment on or make changes to this issue.
Description cryonyx 2009-10-20 13:54:06 UTC
- On opening document (Calc) appears pop-up window "This document contains
macros... Therefore some functionality may not be available"

*Steps to reproduce*
# Set high security level
# Add javascript macros
# Save the document
# Go to Tools->Macros->Organize macros... and delete the macros from the document
# Save the document
# Open the document
# Get the pop-up window with the warning

*Reason for problem*
- In the saved document with deleted macros still remains folder
"Scripts\javascript", which causes the security subsystem to throw the warning
- Deleting the folder solves the problem

Please fix: the macros is to be deleted completely with no garbage left.

Comment 1 dobsche2 2009-10-25 10:20:40 UTC
confirmed with ooo 3.1.1 on winxp
Comment 2 Michael Osipov 2011-05-18 13:33:41 UTC
Just ran into this crap too. Same issue with BeanShell or any other script type.
As a workaround, do cryonyx steps plus delete all references to scripts in the mainfest.xml file.
Comment 3 Michael Osipov 2011-05-18 13:34:26 UTC
Forgot to mention: using OOo 3.3
Comment 4 bmarcelly 2011-05-19 07:10:46 UTC
After you have deleted the macro, you need to delete also the macro library. This is possible with the same user interface.

Remark : you could have created several macros in one library. So deleting a macro does not imply deleting its library.

This is general for all scripts, including Basic. It is working as designed.
Comment 5 jsc 2012-03-01 12:11:51 UTC
I set this issue to resolved and invalid. As bmarcelly has pointed out the library have to be deleted as well.