Current Known Issues Updated Sept 8 '14 — this archived support thread from the APG vNext community covers a reported issue and its resolution.
Troubleshooting This Issue
- Set
customErrors mode="Off"inweb.configto expose the full error and stack trace. - Check Windows Event Viewer → Application log for ASP.NET exceptions.
- Review Admin Panel → Logs → Error Log for timestamped application errors.
- Restart the IIS Application Pool to clear stale state.
- Verify the database connection string and run any pending upgrade SQL scripts.
Related Resources
Known Issues Updated September 2014 - Historical Context
This is the September 2014 snapshot of APG vNext known issues, preserved for historical reference. If you are running an older version of APG vNext and encountering one of these issues, upgrading to the current version is the recommended resolution - all issues listed below were resolved in subsequent releases.
Issues Resolved Since September 2014
- Full-text search returning zero results after upgrade from 3.9 to 4.1 - resolved in 4.1.2
- Quick Reply form not submitting on IE11 - resolved in 4.2
- Avatar upload page hanging IIS under high load - resolved in 4.2 (ImageSharp migration)
- Email notifications not sent when forum is behind a load balancer - resolved in 4.1.3
- Mobile theme crash on theme switch - resolved in 4.2.1
Checking Your Version
SELECT SettingValue AS AppVersion
FROM apg_Settings
WHERE SettingKey = 'AppVersion';If your version is below 5.0, a full upgrade path is available. The upgrade is tested and documented in the Knowledge Base. All data (posts, members, attachments) is preserved during the upgrade.
Upgrade Path from 3.x / 4.x
3.x -> 4.0 (major migration, run upgrade wizard)
4.x -> 4.5 (incremental, run SQL migration scripts)
4.5 -> 5.x (major migration, run upgrade wizard + skin update)Understanding the September 2014 Release Context
In September 2014, APG vNext was at version 4.1.x. At this point, the forum software had recently transitioned from its legacy GDI+ image processing to an early version of its managed imaging pipeline. Several of the known issues listed in this thread relate directly to that transition period — unexpected interactions between the new image handling code and older server configurations running Windows Server 2008 R2 with IIS 7.5.
If you are referencing this thread to understand historical behaviour, it is important to note that the codebase has changed substantially since 2014. More than 400 bug fixes and 80 new features have been introduced across versions 4.2 through 5.x. The architectural decisions made in 2014 around session handling, output caching, and SQL query optimisation were revisited and improved in the 4.4 and 5.0 releases respectively.
How APG vNext Handles Known Issue Documentation
Since 2014, the APG vNext team has improved its issue documentation process significantly. The community forum remains the primary channel for known issue reporting, but the team now also maintains a structured changelog in the Admin Panel's Help section that documents every bug fix by version number. This allows administrators to quickly cross-reference a reported symptom with the version in which it was fixed, without having to read through long forum threads.
Searching the Historical Issue Archive
The APG vNext community forum maintains a complete archive of all known issues threads dating back to the initial public release. When encountering an unexplained error on an older installation, searching the forum with keywords from the error message often surfaces a historical thread with a workaround or resolution, even for issues that predate the current support team's involvement with the product.
Upgrade Decision Framework
When deciding whether to upgrade a long-running older APG vNext installation to resolve historical known issues, consider three factors: the severity of the issues currently affecting your community, the complexity of the upgrade path (particularly for heavily customised skins), and the compatibility of your server's .NET Framework version with the target APG vNext release. For installations running 4.x with custom skins, allocate 1–3 days for a properly tested upgrade to 5.x. The effort is consistently worthwhile — the performance, security, and feature improvements in 5.x over 4.1 are substantial and have a direct positive impact on community member experience and SEO performance.
Version 4.1 Architecture and Why These Issues Occurred
APG vNext 4.1, released in mid-2014, was a transitional release that introduced the new modular plugin architecture while maintaining backward compatibility with 3.x themes and data formats. This dual requirement created a category of issues where the new plugin loading code interacted unexpectedly with IIS application pool settings and SQL Server connection pooling configured for the older architecture. The avatar IIS hang issue, for example, was caused by the new plugin loader acquiring a file handle on the plugin manifest during each avatar processing request, exhausting available handles under concurrent load — a bug that was invisible in single-user testing but catastrophic at moderate traffic levels.
Understanding why these issues occurred in version 4.1 is useful context when evaluating APG vNext's reliability on newer versions. The architectural lessons from 2014 directly influenced the design decisions in 4.4 and 5.x, where resource handle management, connection pool sizing, and request timeout handling were all systematically reviewed and improved. The platform in 2025 is architecturally far more robust than the 2014 codebase, and the categories of issues documented in this thread no longer apply to current installations.
Related Resources
Looking for more help? Browse the support forum or check the Knowledge Base.