Front Office


Update on LeagueApps HTML Editor

By LeagueApps
January 30, 2015
2 min

Earlier this week we released an update which included an upgraded version of our HTML Editor. Today we have decided to roll back to the previous version of that HTML Editor. This is actually the second time we attempted an upgrade, and the second time we are reverting to the previous version.

In December after we launched the new version of the editor, we found out that the editor was taking out <style> tags that were inserted into the HTML code. Since then, we changed the configuration options on the editor and figured out a way for the <style> tags to work within the editor. We launched it again this week and things seemed to be going great as the initial problem we encountered was not occurring anymore. But over the last couple days we received reports of some oddities, and upon further investigation we realized the editor had other issues and was not up to our standards.

In particular, if a LeagueApps partner’s website had advanced HTML code in a content page that was not 100% accurate to the official web standards, the code would be automatically changed without any notification. This is similar to a spell checker changing your words while you are typing an email without letting you know. We realize that not everyone writes “perfect” HTML code and we simply cannot use this editor and have to revert to our previous version.

This HTML Editor is a popular 3rd party plugin. In general we have been big fans of this plugin, but in this case we’ve determined that it’s no longer flexible enough for use within LeagueApps.

We are committed to providing our partners with the best tools possible. So we’ve decided to do a thorough evaluation of all available editor plugins, and we’ll be selecting the one which allows us to provide the most effective content editing capability. We aim to have the new HTML Editor integrated into LeagueApps in the very near future. Managing webpages and content is an important part of running your business, and we are committed to making these tools work as smoothly as possible. We apologize for any inconvenience this may have caused, and will keep you updated on our progress. If you have any questions, concerns, or feedback, don’t hesitate to reach us at