Apache OpenOffice (AOO) Bugzilla – Issue 43922
Application macro Libraries are missing
Last modified: 2005-03-22 14:13:54 UTC
I did a clean install on the OOo 2.0 beta. To do this, I had to manually delete the Program files and the personal application data directory for the 1.9.79 installation. I also manually cleaned the registry to avoid any residual affects. Default paths for macros C:\Program Files\OpenOffice.org 1.9.79\share\basic C:\Documents and Settings\pitonyaka\Application Data\OpenOffice.org1.9.79\user\basic When this is finished, I do NOT have access to the shared based application level macros. They are installed and in the correct location, but I can not access them. They do not show up in the macro organizer and I can not load the macro libraries and use them. I can go to the command line and modify things in the directories, I do not have this problem with 1.1.4, and I do not have this problem on Linux. Ironically, when I appended them as a read-only link in My macros, they show up as an application level library. Very strange...
Andreas to u, also might be an idea to become project owner for this project ;-)
Is this reproducable? I often do installations of new StarOffice builds - that should be the same for OpenOffice regarding Library installation - and never had a similar problem. And why did you have to do all the cleaning up manually instead of unin- stalling the office "officially"? This makes the scenario rather difficult to reproduce. :-)
> Is this reproducable? This happens EVERY time for me with Windows XP at work. > I often do installations of new StarOffice builds > that should be the same for OpenOffice regarding Library installation > and never had a similar problem. This is the first time that I noticed it, but I did not notice it until I decided to load the "tools" library and it just was not there. > And why did you have to do all the cleaning up manually instead > of uninstalling the office "officially"? > This makes the scenario rather difficult to reproduce. :-) Well, I store my user libraries in a non-default location because I do not really like the default location with windows (even if it does dammage the configuration files every time that I exit OOo.... I hope the bug is fixed for 2.0.1 :-)) Well, I wanted to make certain that the problem was not related to this. 1. I uninstalled OOo and then I re-installed. The problem was there. And, it remembered that I was using my non-default location for libraries.... 2. I uninstalled OOo, deleted the program directory, and then I re-installed. The problem was there. And, it remembered that I was using my non-default location for libraries.... 3. I uninstalled OOo, deleted the program directory, cleaned the registry, realized that I had not removed the application data so I removed that, and then I re-installed. The problem was there. And, it did NOT remembered that I was using my non-default location for libraries.... I just wanted to make certain that it was a completely clean install that had the problem. The trick is that EVERY install had the problem. I also wanted to make certain that the problem was NOT my non-standard setup because that would significantly change the priority of the bug. You know, "Oh, Andy does things differently, he can wait until 2.0.1" If, however, it has a problem with a standard setup, then the bug is much more serious. People who do non-default things are more likely to be able to work around the issues introduced with their strange setups. Now I know that the problem is not related to what I have done. The important thing, from my perspective, is that when I added a link into "My own libraries", then they showed up as program level macros. Very strange, but usable. I take it that you have not seen this problem with a windows installation.
This really sounds strange. What I still don't understand: How do you manage to avoid the standard location for user macros? One problem I know about - I think there's even an issue for it - is that the Basic pathes in Options / Paths are not really valid any more, because now macrofied URLs are used in the Basic library description files. So if you changed anything there... I also don't use the standard location for user macros but I do it by changing the location of the complete user installation. This can be done by changing the UserInstallation variable in Office/Program/bootstrap.ini. E.g. I always use UserInstallation=$ORIGIN/../UserInst to locate the User installation inside the Office directory. So I can remove the complete installation includeing the user installation by just deleting one folder which is very nice for developing, where I have to install a lot of different versions. :-)
>How do you manage to avoid the standard location for user macros? I change the "Basic" path under options. Everything works great except that when you are done it ALWAYS writes the macro configuration to point at the original location. I listed this as a bug already. It seems silly to me that I can change these values, but it does not work. Very few people probably do this sort of thing. >the Basic pathes in Options / Paths are not really valid any more, I noticed :-( > I do it by changing the location of the complete user installation. I did not know that you could do this..... Perhaps I should do it this way. Of course, I have determined that the problems that I have are not related to this, but I am very happy to find out that there is a better way around my particular issues :-) Thanks for the tip!
Options / Paths has to be overworked anyway. This task can be closed.
Closed