Description

When a plugin package like, for example, processor/ is missing in your data directory's plugin/ directory, the error message states simply 'No module named processor' but you have to guess where and why or look at the traceback, this isn't very user friendly. Same happens for action/ as well, but even subtler since action is only imported when you actually go to some ...?action= link which isn't the default when viewing a page! So if there's no action/ package you have a read-only wiki without attachments etc.

In fact, since processors are deprecated anyway, I think the directory should not be required at all. Same for other modules, I think.

Steps to reproduce

Remove the action, processor, ... directory from your data dir's plugin/ module, restart the wiki and try to use it.

Details

Workaround

Create all the necessary directories and a required __init__.py (contains a function to import the package modules).

Discussion

This is rare case. Most users (all?) do not have any reason to delete directories from the plugin package. However, if we let the user add and remove plugins, it makes sense to let also add and remove packages, or the whole plugin directory. Running without plugin should not break the wiki, it will simply prevent you from using plugins.

Plan

1. Make the error more specific, giving the full path to the missing directory.
2. Consider allowing no plugin directory - need to change several functions
3. Priority: low, does not effect common usage
4. Assigned to:
5. Status:

CategoryMoinMoinBugConfirmed