The e107 community has a long history of users helping each other out. Providing support, reporting bugs, requesting new features, submitting pull requests, and checking up on upcoming milestones, there's lots of ways to get involved in the development of e107.
Having trouble getting e107 up and running? Something not working the way you think it should? Unfortunately we don't have time to maintain a full e107 support community ourselves, but there are a few ways to get help.
- If you think you have found a bug, then please see the section below on Reporting Bugs.
- If you need help with how to use e107 or a development question (such as how to create a theme or plugin) - please see our docs,
- You can also seek assistance at the e107help.org Questions and Answers site where you can get friendly community support from other users,
- If you are using the e107 Legacy software, you may sometimes find answers to your question on our Legacy forum archives.
- For real-time technical chat, and community support, please visit us on Gitter
- For other comments, please use our official community presences on Facebook, and Twitter as well as unofficial community presences on Google+ and Reddit.
Found a problem with e107 v2 Bootstrap? Feel free to submit an issue on the GitHub project. But please keep the following in mind:
- Don't expect the problem to be resolved instantly. The project is made possible by volunteers who also have to manage full-time jobs, family time, and many other things that get in the way.
- Please search to see if your bug was already reported.
- Provide as many details as possible. eg. "It doesn't work" is not so helpful when trying to trace problems.
- After doing everything above, feel free to submit an issue.
If you are using Legacy Software e107 v1, we have set up a place to submit bug issues but please be aware that these will be handled on a lower priority basis as v2 Bootstrap bugs.
Developers are always welcome to support the community in addressing raised issues through pull-requests (see below).
Found a security issue with e107 v2 Bootstrap? Despite our best efforts, sometimes these do crop up. We're committed to resolving these as quickly as possible. So if you spot a security issue, please contact us directly at security[at]e107.org so that we can deal with these away from the eyes of unscrupulous hackers that may seek to exploit these issues and disrupt users' websites.
Got a new feature you'd like to see included in e107? Please use our Github issues page to submit your idea. Here are some things to keep in mind:
- Please search to see if your feature request already exists, and if so, give it a "+1" in the comments
- Understand that we may not get to the feature request right away, and that some features may be best suited to a 3rd-party plugin, rather than the core system of e107.
Submitting Pull Requests
Found a way to solve a bug in e107? Here are a few things to remember:
- Please submit all pull requests on Github.
- Please focus on existing unresolved issues and leave a comment that you're working on it.
- Place the issue number in your description when you make your commit. eg. "Fixes #123 - Icons missing"
- Use a separate branch for each issue you work on.
Want to keep up with what's planned for e107? Check out our milestones on the GitHub project.
Send Your Thanks
Hopefully you think e107 is awesome. We've put hundreds (if not thousands) of hours into the project and have made it completely available to the open source community. If you'd like, here are a couple of ways you can show your appreciation for all the hard work:
- Follow us on Github, Facebook and Twitter.
- Consider becoming a developer and participating in the ongoing development.
- Write inspirational articles, record videos, tell others how you're using e107 and inspire others to adopt e107
- Make a donation to help speed along development.