Issue Tracker

The issue tracker is for reporting bugs in Elgg (the core and the plugins distributed with the core). They are not for support requests. If you are having problems running Elgg which are not answered by our documentation, we invite you to try asking the community.

Every item created with the bug tracker is read. The core developers will contact you if they need more information or if they need to test updated code. The amount of time between submission of a ticket and it being handled depends on a few factors but the most important is how important the core developers think the ticket is. You are able to leave comments on a ticket if you would like to get more information on when or how it will be dealt with. Please be patient as it is not possible to work on every ticket as soon as you would like.

The tracker is used for bug reports, enhancement suggestions, feature requests, and documentation requests.

Submitting a bug report

In order to file a report we request that you have done the following:

• Read the readme.txt, install.txt and the documentation available on docs.elgg.org.
• Have searched the issue tracker to see if your issue has already been reported.
• You can reliably replicate the issue or know under which circumstances the problem is likely to manifest.

Information to include

Your issue report should contain the following:

• A detailed description of your issue, including the page that generated the error and the steps required to recreate the issue.
• The version of elgg you're running, including the Git hash if appropriate.
• Affected browsers
• Any error messages.
• Any relevant messages from the Apache error log produced with debug mode switched on.
• Screen shots where appropriate

Please note that reports which do not give sufficient detail to diagnose the problem, can not be replicated or are dealing with customised code or third party plugins will be closed.