How to report an issue or get helpReporting an issue can be difficult. It is not always obvious which information is important or what will help someone understand and reproduce the problem. You do not need to know what caused the issue. Just include as much relevant information as you can.
Many tasks in Multi Commander can be performed in several different ways, and the behavior can depend on your settings, filesystem, and installed extensions. The information below provides guidance on what to include when asking for help or reporting a problem.
Basic information Please include:
- Your Multi Commander version.
- Whether you are using the portable edition.
- Your Windows version.
- Whether the problem also occurred in an earlier version, if known.
Describe the problem Explain what you were trying to do, what happened, and what you expected to happen.
The best way to describe an issue is to provide clear steps that someone else can follow to reproduce it. Also mention how you started the operation, for example using a keyboard shortcut, menu, toolbar button, context
menu, or drag and drop.
If relevant, mention whether you use Commander-style or Explorer-style keyboard and mouse behavior.
Filesystem and copy/move problems For filesystem, copy, move, or delete problems, describe both the source and destination.
For example:
- Local disk
- network share or NAS
- External or USB drive
- FTP, SFTP, or SCP
- Archive file (Zip, 7Zip, RAR)
Also include any relevant copy/move settings, such as filters, presets, queues, overwrite options, AutoSort, automatic unpacking, or other plug-ins.
The approximate number, type, and size of the files can also be important, especially for performance problems.
Other useful details Depending on the problem, it may help to include:
- Multi-Rename rules and options.
- - File Viewer mode and text encoding.
- The active view mode or layout for interface problems.
- Windows display scaling for visual or layout problems.
- The complete error message.
- A screenshot showing the problem.
Application Log Check the Application Log to see whether it contains any warnings or errors related to the problem.
Press Ctrl+L to show or hide the Application Log. The log level can be changed in Core Settings to include more detailed information.
Include the
relevant log entries in your report when possible. Please remove passwords, server addresses, private paths, usernames, or other sensitive information before posting logs or screenshots publicly.
Example Issue TemplateHere is an example issue-report template. You do not need to follow it exactly; it is simply a guide to the information that may be helpful. The more relevant details you provide from the start, the easier it will be to understand, reproduce, and resolve the issue
Multi Commander version:
Portable edition (yes/no):
Windows version:
What were you trying to do?
How was the action started?
(keyboard shortcut, menu, button, drag and drop, etc.)
Source location/device:
Destination location/device:
Relevant options, filters, presets, or plug-ins:
File type, number of files, and approximate size:
Steps to reproduce:
1.
2.
3.
Expected result:
What happened instead?
Does it happen every time?
Did it work in an earlier version?
Error message:
Relevant Application Log entries:
Additional information:
Recent Posts