We're happy to announce the release of e107 v2.1.9!
This release contains some great improvements as well as bug fixes. We recommend everyone upgrade immediately.
It is now possible to override the chosen editor pref (WYSIWYG), using the e107::getForm()->bbarea() method by changing the $options array, e.g. $options['wysiwyg'] = 'tinymce4' (#3330)
Added option define('X-FRAME-SAMEORIGIN', false); in e107_config to allow for external websites including an e107 website through an iframe (#3101)
Fixes & improvements:
Fixed issue in update routine caused by an incorrect version number (#3302 #3311)
Added backwards compatibility fix to handle old data formatting better (#3305)
Fixed issue with multiple userclass selection in the Admin UI (#3249)
The CSS file ensuring backwards compatibility for non-boostrap or legacy themes (backcompat.css) is now correctly loaded
Fixed issue with LAN's not loading properly on contact.php page
Fixed issue with parsing the sign (#3307)
Fixed issue with 'To' textbox not showing in mail-out functionality (#3303)
Fixed issue with missing navigation text in Admin Area when using 'medium' width devices
Improved support for SVG icons (#1958)
Fixed several issues related to the displaying of comments (#2425 #2281 #2937)
Fixed issue so 'Items per page' option is now respected on custom pages (#3188)
Added default custom fields to Bootstrap 3 template (#3103)
Improved support for Cyrillic characters on registration and login (#2440)
Plugin Builder generated output improved with examples of custom filter and batch options.
Fixed an issue with the language packs not displaying in the Admin Area (#3059)
Added e_gsitemap addon to News and Download plugin (#2606)
Fixed an issue with error pages and redirection (#3179)
Added new event triggers and notifications for the Forum plugin: user_forum_topic_created_probationary, user_forum_topic_updated, user_forum_topic_moved, user_forum_topic_deleted, user_forum_topic_split, user_forum_post_created, user_forum_post_updated, user_forum_post_deleted, user_forum_post_report
Added BBcode template for Forum plugin (#3317)
New preferences in Forum plugin which allow to choose between BBcode or TinyMCE editor (#3318)
Fixed issues with Forum plugin URLs (#3171)
Fixed URL issue in Forum plugin when moving a forum topic (#3244)
Improved Forum parsing: forum titles are only shown using plain text (no HTML or BBcode) (#3245)
Fixed an issue in the forum plugin when marking a forum topic as 'read' (#3338)
Fixed issue in the featurebox plugin which caused debug information to show (#3290 #3074)
Fixed issue with incorrect 'update required' message showing for the featurebox plugin
Over the past months there has been a significant amount of people who have become more and more involved with e107. This is great news and highly appreciated!
In order to stimulate and facilitate collaboration among all volunteers, e107 tries to offer the best platforms given the restraints in resources such as time and money. As a first step, the organisation of the e107 translations has recently undergone some changes. More improvements to other areas will follow in due time.
Thanks to our volunteers in the community, great efforts have been made to publish language packs for the latest releases of e107. To further support and coordinate the development of language packs, a new Github organisation has been created: ‘e107translations’. This organisation houses the official translations of e107.
Translators are strongly encouraged to use this platform so all translations can be effectively managed and published. Each translation team has the freedom to decide how they would like to manage their specific translation and are not bound to use the Github organization for the development process. However, to be recognised as an official language pack, the final version of each language pack has to be uploaded to the Github repository.
To clarify, each translation team can choose how they want manage their own translation. This means that if you are using another way to create your language pack, you can continue to do so. Only the final version of a translation needs to be uploaded to the Github organisation.
In case you or your team are already using your own Github repository, it can be easily transferred directly into the e107translations organisation while maintaining all existing data as well as all ownership rights that you had previously. The change is purely meant to make sure all translations are stored in one place as this enhances coordination and facilitates collaboration among all translators and volunteers.
Using this platform has numerous advantages, including:
Coordination: each translation team has a coordinator assigned who is the contact person for a specific translation. Also, there will be one central place where the official translations can be downloaded. A list of teams and coordinators will be published as soon as possible.
Use of Github tools such as pull-requests, issue discussions and wiki’s which enables and encourages collaboration. Every individual is able to contribute to a translation by submitting pull-requests for instance. Additionally, team coordinators can use the wiki or issues to determine standards and to communicate with the users of a translation.
It allows for further integration of the translations into the core of e107. By using Github as a platform, next steps such as integrating automatic updates of translations into e107 can be achieved more easily.
What is needed and how can you contribute?
If you are currently translating e107 into a specific language and you already have translated previous versions, please get in touch with me (Moc).The best way to contact me is through Gitter but you can also send me an email on moc e107.org. This way we can exchange the necessary information and provide you with the appropriate permissions for the Github repository to allow you to manage the translation in however way you want to.
If you are interested in contributing to a particular translation which is currently not available or not finished, please contact the coordinator for the specific language that is being translated into. A full list of the all the teams can be found on the organisation's team's page. If you cannot find the coordinator, please contact me. If the team is using Github repositories, you can easily contribute by submitting so-called pull requests. More info on those can be found through the links which are added at the end of this post.
Once again, thank you community for providing the currently available translation of e107. Being able to use e107 in your own language stimulates the growth of e107 across borders and should be highly valued.
Feedback on the changes that were made is greatly appreciated. Please join in our Gitter chatroom to have a chat. This is also the place to go to if you have any questions about the new translation organisation structure.
To learn more about how Github works and to find more information on the translation standards of e107, please check the following links: