Top 10 WollMux Features Every Office Needs

WollMux Troubleshooting: Fix Common Template and Printing Issues

Quick checklist (start here)

1. WollMux version: Ensure WollMux and LibreOffice/OpenOffice are compatible and up to date.
2. Template location: Confirm templates (.ott/.odt) are stored in the configured WollMux template folder and accessible by the user.
3. Permissions: Verify file and folder permissions allow read access for the user and the application.
4. Template naming: Avoid special characters or leading/trailing spaces in template filenames.
5. Backup: Make a copy of working templates before editing.

Common problems and fixes

1. Templates not appearing in the menu

• Check WollMux configuration file (wollmux.cfg): ensure the template directory path is correct and uses absolute paths.
• Restart LibreOffice/OpenOffice after changing wollmux.cfg.
• Verify the template folder contains valid .ott/.odt files (open one directly in LibreOffice to confirm).
• If using network storage, test with a local copy to rule out network latency or mount issues.

2. Template fields not populating (mail merge/variables)

• Confirm field names in the template match the keys provided by WollMux (case-sensitive).
• Ensure the data source (CSV, LDAP, database) is reachable and configured in wollmux.cfg.
• For CSV: check delimiter, encoding (use UTF-8), and header row exactness.
• Run WollMux in verbose/log mode to see variable resolution errors (enable logging in wollmux.cfg).

3. Macros or scripts in templates fail

• Check LibreOffice macro security settings: set to a level that allows WollMux macros to run or sign macros.
• Ensure WollMux’s scripting interface is enabled in the application.
• Look for Java or UNO bridge errors in the LibreOffice log (sometimes Java runtime mismatch causes failures).

4. Printing produces blank pages or incorrect layout

• Verify page styles and printer settings in the template: use LibreOffice’s Page Styles (not manual page breaks) for consistent output.
• Test printing outside WollMux to confirm printer driver works.
• If printing to PDF produces different results, compare PDF export settings and embed fonts if needed.
• For duplex or tray issues, check printer driver options and set them explicitly in the print dialog.

5. Performance issues (slow opening or merging)

• Large data sources: filter or paginate input, or pre-generate smaller batches.
• Complex templates: simplify nested fields or heavy macros.
• Network templates/data: copy locally and test to isolate network latency.

How to collect useful error info

• Enable WollMux logging in wollmux.cfg and collect logs.
• Include LibreOffice logs (stderr/stdout) and Java console output if applicable.
• Note exact steps to reproduce, template file, sample data (anonymized), WollMux and LibreOffice versions, OS, and printer model.

Quick recovery steps

1. Revert to a known-good template copy.
2. Disable recent macros/changes and retest.
3. Move templates locally and reconfigure path.
4. Reinstall WollMux if configuration seems corrupted.

When to seek help

• Provide logs and a minimal reproducible example (template + sample data).
• Ask for versions, OS, and whether templates are local or on a network share.

If you want, I can:

• suggest exact wollmux.cfg settings for your setup, or
• review a small template or log excerpt (paste it here) and point out likely causes.