APG vNext 4.4 Released - New Features / Improvements

APG vNext 4.4 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.4

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.4 — What Was New in This Release

APG vNext 4.4 built on the stability improvements of 4.3 and introduced several features that the community had been requesting since the early 4.x development cycle. This thread overview covers the key additions, performance improvements, and the upgrade path for administrators running 4.3 or earlier.

Key Features in APG vNext 4.4

The headline features of the 4.4 release addressed both the member experience and administrator tooling:

Improved inline image upload: Drag-and-drop image embedding in the post editor, with server-side resizing to limit storage consumption
Enhanced moderator queue: Moderators now see a consolidated queue view across all forums they manage, not a per-forum list
Thread subscription management: Members can bulk-unsubscribe from threads from their profile page — reduces email complaints
Admin panel performance: The member list, post search, and report generation pages were rewritten with async SQL queries, significantly reducing page load time on large databases
Email template editor: Notification email HTML templates are now editable from Admin Panel → Settings → Email Templates without touching the filesystem

Performance Improvements

APG vNext 4.4 introduced output caching for the forum home page and category pages. On high-traffic communities, this reduced database load by 40–60% for anonymous visitors. The cache duration is configurable:

<!-- web.config — adjust duration to match your traffic pattern -->
<outputCacheSettings>
  <outputCacheProfiles>
    <add name="ForumHome"   duration="120" varyByParam="none" />
    <add name="ForumList"   duration="60"  varyByParam="forumID" />
    <add name="ThreadView"  duration="30"  varyByParam="threadID;page" />
  </outputCacheProfiles>
</outputCacheSettings>

Set durations conservatively at first. A 120-second cache on the home page means new posts won't appear for up to 2 minutes for cached visitors — acceptable for most communities, but tune down if real-time activity display is critical for your niche.

Upgrading From 4.3 to 4.4

Database Schema Changes in 4.4

APG vNext 4.4 added two new tables and modified the apg_Attachments table to support the enhanced inline image upload feature. These changes are handled by the upgrade SQL script, but it's worth knowing what to expect:

-- New tables added in 4.4
CREATE TABLE apg_ImageResizeQueue (
    QueueID    INT IDENTITY PRIMARY KEY,
    AttachID   INT NOT NULL,
    Status     TINYINT NOT NULL DEFAULT 0,
    CreatedAt  DATETIME NOT NULL DEFAULT GETDATE()
);

-- Modified column in apg_Attachments
ALTER TABLE apg_Attachments
ADD ThumbPath NVARCHAR(500) NULL;

The upgrade script handles this automatically. The above is shown for transparency so DBAs can review the changes before applying.

Upgrade Steps

Back up the database and application files
Download the 4.4 package from the member area
Run upgrade_4.3_to_4.4.sql in SSMS
Deploy updated application files to IIS, preserving web.config and upfiles
Grant the application pool identity write access to the new thumbs sub-folder inside upfiles
Recycle the App Pool and verify version in Admin Panel → About

Configuring the 4.4 Moderator Queue

The consolidated moderator queue in APG vNext 4.4 is one of the most impactful workflow improvements for communities with multiple sub-forums. Instead of each moderator checking their assigned forums individually for pending reports and posts awaiting approval, everything is surfaced in a single dashboard view.

Setting Up the Consolidated Queue

No configuration is required — the consolidated moderator queue activates automatically after upgrading to 4.4. Moderators see only the items from forums where they have the Moderate permission. Super-admins see everything across all forums.

-- SQL: Grant the Moderate permission to a user on a specific forum:
INSERT INTO apg_ForumPermissions (ForumID, UserGroupID, PermissionType, IsGranted)
SELECT f.ForumID, ug.GroupID, 'Moderate', 1
FROM   apg_Forums f
CROSS  JOIN apg_UserGroups ug
WHERE  f.ForumName = 'Your Forum Name'
  AND  ug.GroupName = 'Moderators';

Moderator Queue Notification Settings

In 4.4, moderators can opt in to email notifications when new items appear in their queue. Configure from Admin Panel → Settings → Moderation → Queue Notifications. This eliminates the need for moderators to manually check the queue panel — they receive an email and can act directly from it.

Troubleshooting the 4.4 Inline Image Upload

The drag-and-drop image upload in 4.4 requires HTML5 File API support. Internet Explorer 9 and below do not support drag-and-drop upload — a fallback button-based file picker is shown automatically for these browsers. If the drag-and-drop area is visible in IE9 but images silently fail to upload, verify that the file is within the configured size limit:

<add key="APG.Upload.MaxFileSizeMB"    value="10" />
<add key="APG.Upload.AllowedImageTypes" value="jpg,jpeg,png,gif,webp" />
<add key="APG.Upload.InlineEnabled"    value="true" />

Also confirm the IIS maxAllowedContentLength and maxRequestLength values are higher than the configured file size limit. IIS enforces these limits at the HTTP layer before the APG vNext application code runs — if IIS rejects the request, the APG file size error handling is never reached.

<system.web>
  <httpRuntime maxRequestLength="20480" /> <!-- 20MB in KB -->
</system.web>
<system.webServer>
  <security>
    <requestFiltering>
      <requestLimits maxAllowedContentLength="20971520" /> <!-- 20MB in bytes -->
    </requestFiltering>
  </security>
</system.webServer>