In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
The reason we haven't integrated the same WYSIWYG as we use in KB, is the security.
In tickets section, we have editor that stores source in bb code and in kb, it's html editor.
So only agents have access to html editor in announcements and knowledge base to get improved interface for formatting, to make blog posts, news, manuals, etc.
Tickets and Topics shouldn't have all the features html editor has, as most users woud use basic formatting in comments and on request in description - so bb code editor is more than enough.
But we'll consider improving it in the next major release.
The reason we haven't integrated the same WYSIWYG as we use in KB, is the security.
In tickets section, we have editor that stores source in bb code and in kb, it's html editor.
So only agents have access to html editor in announcements and knowledge base to get improved interface for formatting, to make blog posts, news, manuals, etc.
Tickets and Topics shouldn't have all the features html editor has, as most users woud use basic formatting in comments and on request in description - so bb code editor is more than enough.
But we'll consider improving it in the next major release.
Leave a Comment
Login
/ Register
Loading...
Replies have been locked on this page!
No connection
Real-time notifications may not work
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
Thanks for sharing idea. We have some plans in regards to improving alignment, links.
Font Colors and HTML Mode (we use bb code editor as simple mode) are not in plans
Thanks for sharing idea. We have some plans in regards to improving alignment, links.
Font Colors and HTML Mode (we use bb code editor as simple mode) are not in plans
Hello Chris,
Could you please explain me why do you need it and why our editor doesn't work for you in full mode, but not in bb code editor mode?
We don't allow HTML because of security reasons.
Hello Chris,
Could you please explain me why do you need it and why our editor doesn't work for you in full mode, but not in bb code editor mode?
We don't allow HTML because of security reasons.
Tables are rarely used. But you can try the following.
Make any tables in other editor or even word and paste them here. They will be saved with all the formatting.
P.S. All html tags won't work like you did, because of security reasons
Tables are rarely used. But you can try the following.
Make any tables in other editor or even word and paste them here. They will be saved with all the formatting.
P.S. All html tags won't work like you did, because of security reasons
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
In 3.1 release, we've integrated new html5 WYSIWYG for Knowledge Base, announcements where formatting is very important with more options to work with styles, images, fonts, alignments, links, etc
WYSIWYG for topics and tickets remains the same as it's more then enough to provide support with bbcode editor which provides general formatting and input media, code or hide text in community.
Please, improve wysiwyg for tickets too! You must enable same wysiwyg of KB for tickets...
Thanks!
Please, improve wysiwyg for tickets too! You must enable same wysiwyg of KB for tickets...
Thanks!
Replies have been locked on this page!