When we upgrade to LO4.4.0.0 is done, it is so nice when the macro's are copied to the new version.
vib, Thank you again for taking the time to help us improve LibreOffice. Can you attach your file to the bug report? Remember that it will be visible to the whole world. When you answer, please set the bug status back to UNCONFIRMED. Terry.
And, of course, if the file has more than one macro, which is the one that fails? What should it do? How does it fail? Terry.
Created attachment 109869 [details] Issue macro link
(In reply to vlb from comment #3) > Created attachment 109869 [details] > Issue macro link When you open the file and go to sheet "invoer" cell T2:u4 there is a rose macro link. When you click on the macro link, there is a attantion there is no macro's.
Comment on attachment 109869 [details] Issue macro link For those conserving disk space or data transfers, I note that the .ods attachned to this bug is the same as the .ods attached to bug 86575 <https://bugs.freedesktop.org/attachment.cgi?id=109868>.
The error message from invocation of the macro is: A Scripting Framework error occurred while running the Basic script vnd.sun.star.script:Standard.Betonligger.ECBetonligger?language=Basic&location=application. Message: The following Basic script could not be found: library: 'Standard' module: 'Betonligger' method: 'ECBetonligger' location: 'application' It looks like you had your macro defined not in the workbook but in your user profile, i.e. within "My Macros & Dialogs" in the Macro Organizer. I shall leave it for somebody with more knowlege of Windows, LibreOffice betas, and user profiles to track down your macro definition. Meanwhile, vlb, this bug report claims to apply to all operating systems. Are you using more than one o/s? HTH, Terry.
Button leads to macro "Standard.Betonligger.ECBetonligger (application, Basic)", but in this file macro doesn't exist.Please provide info how to reproduce "lost of the macro from file". It's resaved in LO 4.4? Change the status back to 'UNCONFIRMED' after you've provided repro steps. Thanks! LO 4.3.3.2, linux: The following Basic script could not be found: library: 'Standard' module: 'Betonligger' method: 'ECBetonligger' location: 'application'
(In reply to Terrence Enger from comment #6) > It looks like you had your macro defined not in the workbook but in > your user profile, i.e. within "My Macros & Dialogs" in the Macro > Organizer. That's right, so i will know when the upgrade from 4.3.4 to 4.4.0 the macro's can by used correct. > > Meanwhile, vlb, this bug report claims to apply to all operating > systems. Are you using more than one o/s? > > HTH, > Terry. I use windows and Ubuntu The file isn't save in 4.4.0.
I can confirm with Version: 4.4.0.0.alpha2+ Build ID: d273a60bfdbf9bb7623bed38667ec0647753157c TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-11-20_03:05:21 I created macro in LO 4.3.3.2 and saved to My macros. In LO 4.4 I doesn't see this macro
Created attachment 109892 [details] printscreen from 4.4 and 4.3
raal, I remember something about Windows pre-release versions of LibreOffice being designed to install in parallel to the already-installed version. Does this separation of versions go as far as the user profile? If so, the observed behaviour is intended rather than being a bug. Could this be true? vlb, Thank you for confirming multiple operating systems. Terry.
(In reply to Terrence Enger from comment #11) > raal, > > I remember something about Windows pre-release versions of LibreOffice > being designed to install in parallel to the already-installed > version. Does this separation of versions go as far as the user > profile? If so, the observed behaviour is intended rather than being > a bug. Could this be true? > > vlb, > > Thank you for confirming multiple operating systems. > > Terry. Terry, you're right. Profiles are different. When I copied file with macros from old profile into dev profile, then I see macro. Setting back to unconfirmed, I think this is not a bug. Macro in My macros isn't possible to test with dev version. vlb, you can copy macros to dev profile. Path is ~/.config/libreoffice/4/user/basic/Standard ~/.config/libreofficedev/4/user/basic/Standard
vlb, I trust that raal's comment 12 gets you back on track. Further comments welcome. Meanwhile, I think that we should do something to help the next user who is hit by this problem. Can you point us to whatever you read recently about installing the beta or testing the beta or whatever? That is the place where we need to explain what is going on. So, I am changing this bug report: (*) Summary : confusion about user profiles with beta versions (*) Component : Documentation (*) Importance : medium, normal (*) Status : NEEDINFO (You know what to do.) I am leaving whiteboard needQAadvice just because I would like a second check on my judgement on this issue. Terry.
(In reply to raal from comment #12) > Terry, > you're right. Profiles are different. When I copied file with macros from > old profile into dev profile, then I see macro. Setting back to unconfirmed, > I think this is not a bug. Macro in My macros isn't possible to test with > dev version. > > vlb, > you can copy macros to dev profile. Path is > ~/.config/libreoffice/4/user/basic/Standard > ~/.config/libreofficedev/4/user/basic/Standard Thanks for the info. I have copyed the macro to ~/.config/libreofficedev/4/user/basic/Standard and than the macro worked correct in the Windows pre-release versions. I didn't know when i upgrade from 4.3.4 to 4.4.0 of the macro profile is copied to the new profile. I hope so.
(In reply to vlb from comment #14) > I didn't know when i upgrade from 4.3.4 to 4.4.0 of the macro profile is > copied to the new profile. I hope so. It does. The behaviour is by design ;) And visible when downloading files.
Whiteboard: Remove 'needQAAdvice' once bug is NEW/RESOLVED.