Support Thread

Ie 9 Compatibility Issue

Ie 9 Compatibility Issue — APG vNext Guide

Ie 9 Compatibility Issue — this archived support thread from the APG vNext community covers a reported issue and its resolution.

Troubleshooting This Issue

  1. Set customErrors mode="Off" in web.config to expose the full error and stack trace.
  2. Check Windows Event Viewer → Application log for ASP.NET exceptions.
  3. Review Admin Panel → Logs → Error Log for timestamped application errors.
  4. Restart the IIS Application Pool to clear stale state.
  5. Verify the database connection string and run any pending upgrade SQL scripts.

Related Resources

Internet Explorer 9 Compatibility in APG vNext

Internet Explorer 9, released in 2011, has been end-of-life since January 2016 and is no longer used by any meaningful share of web traffic. APG vNext 5.x does not officially support IE9 or any other legacy Internet Explorer version. The platform targets modern browsers — Chrome, Firefox, Edge, and Safari in their current and last two major versions. If you are encountering IE9 rendering issues on an older APG vNext installation, the recommended solution is to stop supporting IE9 entirely rather than spending time on compatibility fixes for a browser used by less than 0.01% of internet users globally.

Historical IE9 Issues and Their Causes

During APG vNext's support for IE9, common compatibility issues fell into several categories. CSS3 flexbox was not supported in IE9, causing layout problems in flexible page sections. SVG rendering had significant bugs in IE9, which caused icons and certain visual elements to appear broken or absent. The placeholder attribute on input fields was not supported, leaving form fields without hint text. The addEventListener API was supported in IE9 but with differences from the W3C standard that caused certain APG event handlers to fail. These issues were addressed using conditional comments, polyfills, and progressive enhancement techniques in older APG vNext releases.

Adding the X-UA-Compatible Meta Tag

If your forum is accessed through an intranet or corporate environment that enforces compatibility mode in Internet Explorer, add the following meta tag to the APG vNext theme layout file to force IE to use the latest rendering engine rather than emulating an older version:

<meta http-equiv="X-UA-Compatible" content="IE=edge">

Place this meta tag as the first element inside the <head> tag — before any other tags including charset declarations — for it to take effect before IE has begun parsing the page. Alternatively, set this as an HTTP header in IIS by adding it to the custom HTTP headers configuration in IIS Manager → the site → HTTP Response Headers → Add with name X-UA-Compatible and value IE=edge.

Microsoft Edge and Modern Browser Recommendations

For organisations whose users are still on older Windows installations that shipped with IE11 as the default browser, strongly recommend transitioning to Microsoft Edge (the Chromium-based version available for Windows 7 and later). Edge provides full modern web standard support, is maintained with regular security updates, and is the only browser Microsoft continues to support on Windows. APG vNext works fully and without issues in all modern versions of Edge, and Edge's IE compatibility mode can handle any legacy internal web applications that still require IE-specific behaviour without needing to keep Internet Explorer installed.

Testing APG vNext Across Browsers

To ensure consistent member experience across the browsers used by your community members, use browser testing tools like BrowserStack or Sauce Labs to test key APG vNext pages — forum thread list, post detail, new reply form, user registration, and admin panel — across the browsers and versions used by your audience. Check your forum's analytics for the browser distribution of your members (Google Analytics → Tech → Browser and OS report) to prioritise which browsers to test. Focus testing effort on the browsers that represent more than 1% of your traffic, and document any known issues with minority browsers in a browser compatibility note visible to members.

Related Resources

Polyfill Strategies for Legacy IE Support

For APG vNext installations that must support Internet Explorer for legacy intranet deployments, a polyfill strategy allows modern JavaScript APIs and CSS properties to work in older IE versions without modifying the APG vNext core code. Use a CDN-delivered polyfill service (polyfill.io) that detects the browser version and serves only the polyfills needed for that specific browser, minimising the polyfill payload for modern browsers while ensuring full compatibility for IE users. Common polyfills required for IE9 include: Fetch API (for AJAX requests), Promise (for asynchronous operations), CSS Custom Properties (for theme variables), and Element.closest (for DOM traversal). Add the polyfill.io script tag as the first script in the theme layout to ensure polyfills are loaded before any APG vNext JavaScript code runs.

Removing IE-Specific Code During Upgrades

If you have customised APG vNext theme files and previously added IE-specific conditional comments, Respond.js polyfills, or IE-targeted CSS hacks, these can be safely removed during theme upgrades to reduce unnecessary HTTP requests and code complexity. The theme files in the latest APG vNext version no longer include IE-specific fallbacks since the supported browser targets no longer include any IE version. Clean theme code without legacy IE workarounds is faster to load, easier to maintain, and eliminates potential conflicts between old IE-targeted code and modern CSS properties used in current theme versions.

Looking for more help? Browse the support forum or check the Knowledge Base.