With previous versions of OpenOffice.org, you could put custom Python scripts in a directory called ~/.ooo<ver>/user/Scripts/python/, and they would show up in the macro dialogs. Since installing version 3.0, this no longer seems to be the case. Reproducible: Always Steps to Reproduce: 1. Note the instructions at <http://wiki.services.openoffice.org/wiki/Python_as_a_macro_language>. On Gentoo with previous versions of Ooo, the user prefs directory was ~/.ooo-2.0/, with Ooo 3 it's ~/.ooo3/. 2. In each case, note that the user prefs directory contains a directory called "user". 3. Within this "user" directory, create a subdirectory called "Scripts" (capital-S), and within that, a subdirectory called "python". 4. Copy a script, e.g. the dynamicDialog.py example linked from the above Ooo wiki page, into this "python" directory. 5. Launch Ooo Writer, and go to the "Tools->Macros" submenu, and look in either the "Run Macro..." or "Organize Macros->Python..." dialogs. In Ooo 2.x, if you expand the "My Macros" list item, you will see "dynamicDialog" appear, with the name of a macro that you can run. In Ooo 3.0.0, this does not appear.
Perhaps this posting is related? http://user.services.openoffice.org/en/forum/viewtopic.php?f=45&p=50658
(In reply to comment #1) > Perhaps this posting is related? Doesn't look like it. That seems to be reporting problems running Python scripts in general. If I copy my own Python script to /usr/lib/openoffice/basis3.0/share/Scripts/python/, it shows up in the macro dialogs and runs just fine. Ooo is just not looking in my user Scripts directory.
Did you try to redo you user install? (with a clean .ooo3, note that you would have to delete .ooo-2.0 beforehand too).
upstream bug: http://www.openoffice.org/issues/show_bug.cgi?id=93994
(In reply to comment #4) > upstream bug: > http://www.openoffice.org/issues/show_bug.cgi?id=93994 > The patch provided by upstream fixed the problem for me.
A fix for this is already incorporated in the latest ooo-build patchset (which we have in portage since some time now). If you still have that problem, rebuild OOo and it should be gone
