Comment 9 for bug 878269

Revision history for this message
Tim Bentley (trb143) wrote :

1779 - I changed the alert code to fix the change of settings and refactor the CSS loading
1780 - Translation fixes
1781 - Live Preview changes and fixes.
1782 - Build script fixes for startup

All the plugins are throwing this error

2011-10-19 11:09:09,371 openlp.core.lib.pluginmanager DEBUG Importing alerts.alertsplugin from C:\Program Files (x86)\OpenLP\plugins\alerts\alertsplugin.py. Depth 6
2011-10-19 11:09:09,377 openlp.core.lib.pluginmanager ERROR Failed to import module alerts.alertsplugin on path C:\Program Files (x86)\OpenLP\plugins\alerts\alertsplugin.py for reason No module named openlp.core.lib.db
Traceback (most recent call last):
  File "D:\OpenLP_Code\trunk\build\pyi.win32\OpenLP\outPYZ1.pyz\openlp.core.lib.pluginmanager", line 95, in find_plugins
  File "D:\pyinstaller\PyInstaller\iu.py", line 424, in importHook
    mod = _self_doimport(nm, ctx, fqname)
  File "D:\pyinstaller\PyInstaller\iu.py", line 514, in doimport
    exec co in mod.__dict__
  File "C:\Program Files (x86)\OpenLP\plugins\alerts\alertsplugin.py", line 33, in <module>
    from openlp.core.lib.db import Manager
  File "D:\pyinstaller\PyInstaller\iu.py", line 443, in importHook
    raise ImportError, "No module named %s" % fqname
ImportError: No module named openlp.core.lib.db

Why is openlp.core.lib.db not loading? This has not changed for a few months

Is it possible to build each of the releases so we can see which one did the damage cos from the evidence it is not clear.