This community thread discusses the feature or improvement: APG vNext 5.5 - Offical Tapatalk + improved post management.
Feature Details
What's new in 5.5?Since the release of 5.0, our focus has been to make integration easier with relevant 3rd party services. In 5.1, we introduced Akismet, a...
How APG vNext Handles Feature Requests
Feature requests and suggestions are tracked through the community forum. The development team reviews popular requests and incorporates the most-requested improvements into upcoming releases.
- Vote for features by upvoting the original post in the forum thread
- Add details about your use case to help prioritize the request
- Check the release blog for updates on upcoming features
See the full feature set on the Features page or browse all community discussions.
APG vNext 5.5 — Official Tapatalk Integration
APG vNext 5.5 added official support for Tapatalk, the mobile app that aggregates forum communities into a single native app experience for iOS and Android. Before 5.5, some APG vNext administrators had set up unofficial Tapatalk compatibility through community-contributed plugins, but these were maintenance-heavy and often broke on minor version upgrades. The 5.5 official integration is maintained by the APG team and follows Tapatalk's published API specification directly.
What Tapatalk Integration Provides
- Native push notifications to mobile devices for thread replies and mentions
- Optimised mobile reading experience — no need to open a browser
- Forum appears in Tapatalk's directory, increasing community discoverability
- Member activity on Tapatalk counts in APG vNext's post and activity metrics
- File attachments and inline images display correctly in the Tapatalk app
Enabling Tapatalk in APG vNext 5.5
- Register your forum at tapatalk.com and obtain your Forum ID and API Secret
- In APG Admin Panel → Settings → Mobile → Tapatalk, paste both values
- Set Push Notifications to Enabled
- Upload your forum icon (512×512 PNG) for the Tapatalk directory listing
- Click Save — no IIS restart required
<!-- web.config Tapatalk configuration -->
<appSettings>
<add key="APG.Tapatalk.Enabled" value="true" />
<add key="APG.Tapatalk.ForumID" value="your-forum-id" />
<add key="APG.Tapatalk.Secret" value="your-api-secret" />
<add key="APG.Tapatalk.PushMode" value="all" /> <!-- all | subscribed -->
</appSettings>
Improved Post Management in APG vNext 5.5
Beyond Tapatalk, version 5.5 significantly upgraded the post management tools for moderators and administrators. The improvements were driven by feedback from large communities managing thousands of posts per day.
Bulk Post Actions
Moderators can now select multiple posts across a thread and apply batch actions:
- Move: relocate selected posts to a different thread or create a new thread from them
- Delete: soft-delete with a deletion reason logged for the audit trail
- Merge: combine consecutive posts from the same author into a single post
- Quote-chain: extract a back-and-forth quote chain into its own thread for clarity
Post Revision History
APG vNext 5.5 added a post edit history log. Every edit saves the previous version with a timestamp and the editor's username. Members can see their own edit history; moderators can see all edits on any post. This is critical for communities where post content matters for legal or compliance reasons.
-- Check edit history for a specific post
SELECT ph.EditedAt, ph.EditedBy, ph.PreviousContent
FROM apg_PostHistory ph
WHERE ph.PostID = @PostID
ORDER BY ph.EditedAt DESC;
Spam Post Bulk Removal
When a spam account is banned, 5.5's admin panel now offers a one-click "Remove all posts by this member" with an optional soft-delete (posts hidden, not purged) or hard-delete (posts permanently removed). The action is logged with the admin's username for accountability.
Tapatalk Push Notification Configuration
Push notifications via Tapatalk use Apple Push Notification Service (APNS) for iOS and Firebase Cloud Messaging (FCM) for Android. APG vNext 5.5 delegates the actual push delivery to Tapatalk's servers — you don't need to manage push certificates or FCM server keys yourself. The only configuration required is ensuring the APG Tapatalk plugin can reach the Tapatalk API endpoint:
-- Verify outbound connectivity to Tapatalk API (run from server):
curl -I https://api.tapatalk.com/health
-- Expected: HTTP/2 200
-- If blocked by firewall, add outbound rule:
-- Allow: api.tapatalk.com:443 (HTTPS)
-- Allow: push.tapatalk.com:443 (HTTPS, push delivery status)
Notification Throttling
To prevent notification fatigue, APG vNext 5.5 implements per-member throttling. By default, no more than 5 push notifications are sent per member per hour, regardless of thread activity. Configure in Admin Panel → Settings → Mobile → Notification Throttle.
Upgrading From 5.1 to 5.5
There were three intermediate versions between 5.1 and 5.5 (5.2, 5.3, 5.4). Each introduced incremental improvements. If upgrading from 5.1, run each intermediate upgrade script in sequence rather than jumping directly to the 5.5 script. The 5.5 script assumes the 5.4 schema is in place.
-- Upgrade path from 5.1 to 5.5:
-- upgrade_5.1_to_5.2.sql
-- upgrade_5.2_to_5.3.sql
-- upgrade_5.3_to_5.4.sql
-- upgrade_5.4_to_5.5.sql
-- Verify current version before starting:
SELECT SettingValue FROM apg_Settings
WHERE SettingName = 'Version';
-- Must be 5.1 before running 5.2 script, etc.
Testing Tapatalk After Upgrade
After installing 5.5 and enabling Tapatalk:
- Download the Tapatalk app on a mobile device
- Search for your forum by URL — it should appear in Tapatalk's search results within 24 hours of registration
- Log in with your forum credentials through the Tapatalk app
- Post a test reply in a thread and verify it appears in APG vNext with the correct author attribution
- Subscribe to a thread and trigger a reply — verify push notification is received within 30 seconds
Post Management: What Admins Say After Upgrading to 5.5
The bulk post actions in APG vNext 5.5 received consistently positive feedback from community administrators managing large active forums. The most commonly cited benefit was the ability to split off-topic discussions from a thread without manually copying and pasting content into a new post. Previously, moderators would either leave the off-topic content in place (degrading thread quality) or delete it (losing potentially valuable discussion). The 5.5 "move posts to new thread" feature resolved this dilemma cleanly.
Related Resources
Looking for more help? Browse the support forum or check the Knowledge Base.