Is Wysiwyg Formatting Available In The Software
Answer
This question was discussed in the APG vNext support community. For a complete answer, browse the Knowledge Base or search the support forum.
Quick Reference
- FAQ — common questions answered
- Installation Guide — step-by-step server setup
- Upgrade Guide — upgrading between versions
- Features Overview — what APG vNext includes
- Support Forum — ask the community directly
WYSIWYG Formatting in APG vNext
Yes, APG vNext includes a full WYSIWYG rich text editor. The editor allows users to format their posts visually without needing to know HTML or BBCode syntax. The platform ships with TinyMCE as its default WYSIWYG editor, one of the most widely used and well-supported open-source rich text editors available for ASP.NET web applications.
Enabling and Disabling the WYSIWYG Editor
The WYSIWYG editor can be toggled at the forum level via the admin panel. Navigate to Admin > Editor Settings > Enable Rich Text Editor to turn it on or off globally. When enabled, individual users can still switch to a plain-text or BBCode mode using the editor toolbar toggle, giving power users the flexibility to write in raw markup while new members get the visual editor by default.
Editor Features Available
The TinyMCE-based editor in APG vNext supports: bold, italic, underline, strikethrough, text color, background highlight, font size, heading levels, text alignment, numbered and bulleted lists, indent and outdent, blockquote, horizontal rule, hyperlink insertion, image insertion from URL or file upload, table creation and editing, code block formatting with monospace font, and emoticon insertion from the forum's configured smiley set.
BBCode vs. WYSIWYG Mode
APG vNext stores post content internally as BBCode, not as raw HTML. The WYSIWYG editor converts user input to BBCode on save and displays BBCode as formatted HTML on read. This design ensures posts remain readable even if the rich text editor is later disabled or replaced, and it prevents malicious HTML injection through the editor. Users who prefer writing directly in BBCode can click the editor source toggle to switch to BBCode view while composing their post.
Commonly supported BBCode tags include bold, italic, underline, strikethrough, color, size, url, img, quote, code, list, and table. Administrators can configure which tags are permitted for specific user groups, enabling restriction of certain formatting options — for example, preventing guests from using image tags, or allowing only moderators to use the color tag to prevent misuse.
Code Syntax Highlighting
For technical forums, APG vNext supports syntax-highlighted code blocks using the language-tagged code BBCode. When a user wraps code in a code block with a language specifier, the forum applies syntax highlighting using a client-side library. Supported languages typically include C#, VB.NET, JavaScript, SQL, HTML, CSS, XML, and PHP. The syntax highlighting library is loaded only on pages that contain code blocks, keeping page load times efficient for general discussion threads that do not contain code.
Mobile Editor Behavior
On mobile devices, TinyMCE operates in a simplified mode adapted for touch input. All core formatting operations remain available on mobile, but some advanced table editing features behave differently due to browser content-editable limitations on touch screens. APG vNext detects the user agent and can optionally serve a simplified editor interface to mobile users that prioritizes the most commonly used formatting actions in a touch-optimized toolbar layout with larger tap targets.
Configuring the Editor Toolbar
The editor toolbar buttons can be customized in the APG vNext admin panel to show only the formatting options relevant to your community. A general discussion forum might enable only the basic formatting buttons (bold, italic, lists, links), while a technical community might add the code block, table, and syntax highlighting buttons. Reducing the toolbar to only necessary buttons simplifies the editor for new users and reduces the JavaScript bundle size since unused TinyMCE plugins can be excluded from loading.
Accessibility of WYSIWYG Content
TinyMCE is designed with accessibility in mind and supports keyboard navigation through the toolbar and editor area. Users who cannot use a mouse can format their posts entirely with keyboard shortcuts: Ctrl+B for bold, Ctrl+I for italic, Ctrl+U for underline, and Alt+F9 to access the menu bar. The editor meets WCAG 2.1 AA accessibility requirements for the toolbar interface, making APG vNext suitable for communities with diverse accessibility needs.
Troubleshooting WYSIWYG Issues
If the WYSIWYG editor is not appearing for some users even though it is enabled, check whether their browser has JavaScript disabled or a browser extension is blocking the TinyMCE script. The editor falls back to a plain textarea when JavaScript is unavailable, which is the correct degraded behavior. If users report that formatted posts display as raw BBCode tags rather than rendered HTML, check that the APG vNext BBCode renderer is not disabled in settings. Finally, if the editor loads but formatting is not saving correctly, inspect the form submission in the browser network panel to confirm the post content field is being sent with BBCode markup rather than plain text.
Looking for more help? Browse the support forum or check the Knowledge Base.