Support Thread

APG vNext 4.5 Released - Feature Refinements for 4.4

📅 👤 ASP Playground
APG vNext 4.5 Released - Feature Refinements for 4.4 — APG vNext Guide

APG vNext 4.5 brings new features and improvements to help you build a better online community. This release is available for all license holders.

Release Highlights

  • New and improved features as detailed in the community announcement
  • Performance and stability fixes based on user-reported issues
  • Enhanced mobile and responsive design improvements
  • Admin panel usability refinements

Upgrading to 4.5

Existing users can upgrade by following the standard upgrade procedure. This release is a drop-in upgrade for users on the previous minor version.

Download

Download the latest version of APG vNext from the download page. Registered users can access the member download area for the full release package.

APG vNext 4.5 — Feature Refinements and Stability Fixes for 4.4

APG vNext 4.5 was a focused maintenance and refinement release targeting issues discovered after the 4.4 launch. Rather than introducing new major features, the 4.5 team concentrated on polishing the inline image upload added in 4.4, improving the moderation queue workflow, and resolving three edge-case bugs that affected specific hosting configurations.

For communities running 4.4 without major issues, 4.5 is a low-risk quality-of-life upgrade. For communities that experienced problems with 4.4's image upload or email template editor, 4.5 is a recommended update.

What Was Refined in 4.5

  • Inline image upload stability: Fixed a race condition where simultaneous uploads from multiple browser tabs could corrupt the attachment record in apg_Attachments
  • Moderation queue: Cross-forum queue view now correctly filters by moderator's forum permissions — a 4.4 oversight allowed moderators to see (but not act on) posts from forums outside their scope
  • Email template editor: HTML entities in saved templates were being double-encoded on re-open; fixed in the server-side template loader
  • Thread subscription bulk-unsubscribe: Checkbox state was being lost on paginated member profile pages; fixed with a server-side selection state handler
  • Output cache invalidation: Cache was not being cleared when a thread was deleted by a moderator, causing ghost thread links on the forum home page for cached visitors

Database Changes in 4.5

APG vNext 4.5 requires a small SQL script to run against your database. The schema changes are minimal — two index additions and one stored procedure update:

-- Adds missing index on apg_Attachments for upload deduplication
CREATE UNIQUE NONCLUSTERED INDEX UX_apg_Attachments_Hash
ON apg_Attachments (FileHash)
WHERE FileHash IS NOT NULL;

-- Updates stored proc for cache-aware thread deletion
ALTER PROCEDURE apg_DeleteThread
    @ThreadID INT,
    @DeletedBy INT
AS
BEGIN
    -- (procedure body updated to set cache invalidation flag)
    UPDATE apg_CacheInvalidation
    SET InvalidatedAt = GETDATE()
    WHERE CacheKey = 'ForumHome';

    DELETE FROM apg_Threads WHERE ThreadID = @ThreadID;
END

Run the provided upgrade_4.4_to_4.5.sql script — do not run the above manually, it is shown for reference only. The script handles execution order and wraps everything in a transaction.

Hosting Configuration Considerations

IIS Application Pool Recycling

The output cache fix in 4.5 depends on the ASP.NET in-memory cache being accessible. If your hosting environment recycles the application pool on a schedule shorter than the cache TTL (e.g., a 30-minute auto-recycle with a 120-second cache), the cache invalidation feature works correctly because the recycle itself flushes the cache. However, on environments with very infrequent recycling (or never), the fix is critical.

<!-- Recommended App Pool settings for APG vNext 4.5 -->
<processModel
    idleTimeout="00:20:00"
    maxWorkerThreads="50"
    maxIoThreads="50" />

Shared Hosting Notes

On shared Windows hosting where you cannot control the application pool recycle schedule, the 4.5 ghost-thread bug workaround is to reduce the forum home page cache duration to 30 seconds or disable it entirely for the ForumHome profile. Real-time accuracy is more valuable on shared hosting than the marginal performance gain from caching.

Post-Upgrade Verification Checklist for 4.5

After upgrading to APG vNext 4.5, run through the following checks to confirm the refined features are working correctly:

  1. Image upload: Open two browser tabs simultaneously and upload an image from each at the same time. Both uploads should succeed independently without corrupting each other's attachment records.
  2. Moderator queue scoping: Log in as a moderator with access to only specific forums. Verify the queue only shows posts from those forums — not from forums you don't moderate.
  3. Email template re-open: Edit a notification email template in Admin Panel → Settings → Email Templates, save it, then re-open it. Verify the HTML content is identical to what you saved (no double-encoding of entities like &amp; appearing instead of &).
  4. Cache invalidation on delete: Post a test thread, allow it to be cached (visit the forum home and wait 30 seconds), then delete the thread as a moderator. Refresh the forum home page — the deleted thread should no longer appear.

Deciding Between 4.5 and Jumping to 5.0

If you're on APG vNext 4.4 and considering the upgrade path, you have two options: upgrade to 4.5 (a stable refinement release), or skip ahead to 5.0 (which includes major new features like Tapatalk integration and mobile-first design). The decision depends on your community's mobile traffic share and your tolerance for larger upgrades.

If more than 30% of your community uses mobile devices, jump directly to 5.0 — the mobile-first design improvements are too significant to pass up by stopping at 4.5. If your community is primarily desktop-based and you value stability over new features, 4.5 is a safer step in the upgrade path before eventually moving to 5.x.

-- Check mobile vs desktop traffic from APG vNext analytics:
SELECT DeviceType, COUNT(*) AS Sessions
FROM   apg_SessionLog
WHERE  StartDate > DATEADD(DAY, -30, GETDATE())
GROUP  BY DeviceType
ORDER  BY Sessions DESC;

Related Resources

4.x Release History

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