[Moin-user] Problem with plugins after upgrading to 1.6.0

Jim Wight j.k.wight at ncl.ac.uk
Thu Jan 17 08:29:08 EST 2008

On Mon, 2008-01-14 at 16:44 +0000, Jim Wight wrote:
> I've converted one wiki (from 1.3.5) to use 1.6.0. Pages are being
> displayed OK apart from those accessing the plugin directory. Every
> access of a page containing a 3rd-party macro results in an error of the
> form:
>    No module named plugin.macro.XYZ
> I've copied a couple of the macros to a new wiki in the farm, where they
> work fine. 
> What could be giving rise to the problem in the converted wiki? 

The problem occurs at the line

  module = __import__(moduleName, globals(), {}, [name])

in importNameFromPlugin in wikiutil.py.

In a new wiki, where it works, importNameFromPlugin is called thrice
with moduleName equal to <wiki>.plugin.macro.XYZ and name equal to
'Dependencies', followed by three calls with name equal to 'execute'.

For the converted wiki, importNameFromPlugin fails on the very first of
the equivalent calls (with name equal to 'Dependencies') with
'ImportError: No module named plugin.macro.XYZ'.

MoinMoin is definitely reaching the macro directory, because if I remove
__init__.pyc it gets recompiled. Also, the correct list of macros is
assigned to 'modules' within __init__.py. 

I'm baffled as to why this isn't working.


More information about the Moin-user mailing list