Current Known Issues

This archived support thread addresses Current Known Issues. The discussion below documents the reported issue and the steps taken to resolve it.

Troubleshooting Steps

When encountering errors in APG vNext, the following steps help diagnose the problem quickly:

Enable detailed errors: Set customErrors mode="Off" in web.config to see the full error message and stack trace.
Check the Windows Event Log: Application-level ASP.NET errors are logged in the Windows Event Log under Application.
Review the APG error log: Admin Panel → Logs → Error Log shows application-level errors with timestamps.
Verify recent changes: If the error appeared after an upgrade or configuration change, roll back or review what changed.

Common Fixes

Restart the IIS Application Pool to clear stale state
Verify database connectivity and run any pending SQL upgrade scripts
Check that all required .NET assemblies are present in the bin folder
Clear the ASP.NET temporary files folder (%windir%\Microsoft.NET\Framework\...\Temporary ASP.NET Files)

For further assistance, visit the support forum or review the Knowledge Base.

Current Known Issues in APG vNext - Status and Workarounds

This thread is the canonical list of known issues in the current APG vNext release. The development team updates it with each release. Issues are categorised by severity and include the version they were introduced in, the fix status, and any available workaround.

Severity Levels

Critical: data loss or security vulnerability - patched within 24-48 hours
High: major feature broken - patched in the next minor release
Medium: feature partially broken - addressed in next scheduled release
Low: cosmetic or minor UX issue - backlog

How to Report a New Issue

Search this thread and the Knowledge Base first
Post in the APG vNext Support Forum with: version number, OS, browser, steps to reproduce, and error log output
Include output from Admin Panel -> System -> Error Log

Checking for Updates

-- Admin Panel -> System -> Check for Updates
-- Or check programmatically:
GET https://aspplayground.net/api/v1/version/latest
{"version":"5.5.2","releaseDate":"2026-04-15","critical":false}

Applying Hotfixes

Critical hotfixes are distributed as DLL patches. Deploy by replacing the affected DLL in the /bin/ folder and recycling the app pool - no database migration required for hotfixes.

Related Resources

Current Known Issues in APG vNext

This thread tracks active known issues in APG vNext that have been confirmed by the development team but not yet resolved in a released patch. Issues listed here are under investigation or scheduled for a future release. Check this thread before reporting a new bug — if your issue is listed here, it's already being tracked and a workaround or fix is in progress.

How to Use This Thread

Search the thread before reporting a new issue (use Ctrl+F with a keyword)
If your issue is listed, add a "Me too" reply with your APG vNext version and environment details to help prioritise the fix
If your issue is NOT listed, start a new thread with a detailed bug report
The APG development team updates this thread when workarounds are available or issues are resolved

Common Issue Categories

Installation and Upgrade Issues

Issues related to fresh installations, version upgrades, and migration from other platforms. Most common: database migration scripts failing on non-standard SQL Server configurations, and IIS URL Rewrite module not being installed, causing 404 errors on all forum URLs.

Email Delivery Issues

Issues where notification emails are not being sent or are being marked as spam. Most common: SPF/DKIM misconfigurations on shared hosting environments, and notifications not triggering after the post moderation queue is enabled.

Performance Issues

-- Quick performance diagnostic queries:
-- 1. Check for blocking queries:
SELECT r.session_id, r.blocking_session_id,
       SUBSTRING(qt.text, r.statement_start_offset/2,
           (CASE r.statement_end_offset WHEN -1 THEN LEN(CONVERT(NVARCHAR(MAX), qt.text))*2
            ELSE r.statement_end_offset END - r.statement_start_offset)/2) AS QueryText
FROM   sys.dm_exec_requests r
CROSS  APPLY sys.dm_exec_sql_text(r.sql_handle) qt
WHERE  r.blocking_session_id != 0;

-- 2. Check index fragmentation:
SELECT i.name, s.avg_fragmentation_in_percent
FROM   sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('apg_Posts'), NULL, NULL, 'SAMPLED') s
JOIN   sys.indexes i ON i.object_id = s.object_id AND i.index_id = s.index_id
WHERE  s.avg_fragmentation_in_percent > 30
ORDER  BY s.avg_fragmentation_in_percent DESC;

Workarounds for Common Known Issues

The APG vNext support team publishes interim workarounds for high-priority known issues in this thread before the patch release. Workarounds are clearly labelled with the issue reference number and the APG vNext versions they apply to. Always apply workarounds in your staging environment before applying them to production, even when the workaround is a simple configuration change, to verify there are no unintended side effects in your specific environment.

Contributing to the Known Issues List

Community members who discover a new bug that isn't on the known issues list are encouraged to report it in the appropriate support forum with detailed reproduction steps. A clear, reproducible bug report significantly speeds up the development team's ability to confirm and fix the issue. Include: your APG vNext version, the exact sequence of steps to reproduce the bug, the expected behaviour, the actual behaviour, and a screenshot or screen recording. Reports that include a database query or server log excerpt showing the error are especially valuable and often result in faster resolutions. The APG vNext development team triages new bug reports weekly and adds confirmed bugs to the known issues list within 5 business days.

Related Resources

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