Issue 68719 - basic macros do not run after (temporarily) switching a document to read-only mode
Summary: basic macros do not run after (temporarily) switching a document to read-only...
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 680m181
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-17 15:24 UTC by Frank Schönheit
Modified: 2013-07-30 02:40 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
document to reproduce the bug case (64.88 KB, application/vnd.oasis.opendocument.text)
2006-08-17 15:25 UTC, Frank Schönheit 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2006-08-17 15:24:48 UTC 
- open the attache document
  (it's a nearly empty incarnation of the OpenOffice.org Specification
  Template from http://specs.openoffice.org/)
- switch the document to read-only mode
=> your're asked whether you want to allow macros from this document
   (why? I already confirmed or rejected this while initially loading it)
=> An error message box is shown, saying
   "A Scripting Framework error occured while running the Basic script
   vnd.sun.star.script:Standard.Module1.Initialize?language=Basic&
   location=document.

   Message: BasicProviderImpl::getScript: no script!"
- confirm this error
- switch the document to edit mode
- from the "Specification Template" toolbar, click any icon
=> error message:
"com.sun.star.uno.RuntimeExceptionScriptProtocolHandler::createScriptProvider(),"

Besides that all those error messages are in no way helpful to determine what's
going on (honestly, this is bothering the user with techno babble), it seems
that switching to read-only somehow broke the document's ability to execute
Basic macros.

Closing and re-opening the document works around this problem.
Comment 1 Frank Schönheit 2006-08-17 15:25:24 UTC 
Created attachment 38596 [details]
document to reproduce the bug case
Comment 2 thorsten.martens 2006-08-30 09:59:49 UTC 
TM->JSK: Please have a look.
Comment 3 joerg.skottke 2008-06-17 11:01:30 UTC 
I can only confirm what i believe is the first issue in this issue:

Reproduction:
- Download and store the specification template (http://specs.openoffice.org) 
- Make sure the office allows macro execution (Low or medium level)
- Load the template from disk
- Confirm macro execution
- Save the file again under a random name
- Click the "Edit file" button
-> Macro security warning is displayed.

To AS: Can you please have a look or redistribute to someone
Comment 4 Rob Weir 2013-07-30 02:40:47 UTC 
Reset assignee on issues not touched by assignee in more than 1000 days.