Faq For Apg Vnext V5 — an archived discussion from the APG vNext support community.
About This Topic
This thread covers faq for apg vnext v5 in the context of APG vNext, the ASP.NET forum and community platform. The community includes APG developers and experienced administrators who can help with similar questions.
APG vNext Support
- Knowledge Base — documented solutions
- FAQ — frequently asked questions
- Installation Guide
- Upgrade Guide
- Support Forum
APG vNext V5 FAQ - Community Discussion Thread
This thread is the community discussion companion to the V5 FAQ blog post. Members and administrators share their specific V5 upgrade questions and experiences here. Key questions and answers from this thread are periodically consolidated into the Knowledge Base.
Q: Can I run APG vNext 5 on IIS 7.5?
No. APG vNext 5 requires IIS 8.0 or later (Windows Server 2012 R2 minimum). IIS 7.5 (Windows Server 2008 R2) does not support the OWIN middleware that APG vNext 5 uses for authentication pipeline.
Q: The upgrade wizard stalled at 68% - is my data safe?
Yes - the upgrade wizard uses a transaction-based migration. If it stalls, restart IIS, navigate to Admin Panel -> Tools -> Resume Upgrade, and it will continue from where it stopped. Your data is not partially committed.
Q: My custom stored procedures are failing after upgrade
APG vNext 5 renamed several internal tables. Custom stored procedures referencing old table names need updating:
-- Key table renames in V5:
apg_ForumPosts -> apg_Posts
apg_ForumThreads -> apg_Threads
apg_Members -> apg_Members (unchanged)
apg_ForumGroups -> apg_GroupsQ: Can I trial V5 before committing to the upgrade?
Yes - restore a copy of your database to a test server, deploy V5 there, and run the upgrade wizard on the test copy. This lets you validate the upgrade process and check your custom code before touching production.
Additional V5 Questions from the Community
Q: Does V5 support multi-tenancy (multiple forums in one installation)?
Not natively — APG vNext 5 is designed as a single-community platform. Multi-tenancy requires separate installations per community, each with their own database and IIS site. If you need multiple distinct communities under one roof, the recommended approach is to deploy multiple APG vNext instances on the same server using separate IIS sites and application pools, sharing the same SQL Server instance with separate databases. A load balancer or Cloudflare worker can route requests to the appropriate instance based on the requested domain, creating a seamless multi-community experience from the visitor's perspective.
Q: How do I handle the old numeric thread URLs after upgrading to V5?
APG vNext 5 uses SEO-friendly slug URLs as the primary URL for threads and forums. The old numeric-ID URLs from 4.x are automatically redirected with HTTP 301 to their new slug equivalents. No manual redirect configuration is required. The 301 redirects are handled by APG vNext's routing layer and preserve all link equity from inbound links pointing to old numeric URLs. After upgrading, submit your updated sitemap to Google Search Console to help Googlebot discover the new URLs faster.
Q: Can I keep using my V4 licence key with V5?
No. APG vNext 5 uses a new licence key format. V4 licence holders with an active maintenance subscription receive a V5 licence key automatically — check your account on the APG customer portal. If your V4 maintenance subscription has lapsed, you will need to renew to obtain a V5 licence key. Contact support for upgrade pricing options available to existing licence holders.
Q: Is there an in-place upgrade path from V3 to V5 directly?
No — direct upgrade from V3 to V5 is not supported. The upgrade path is V3 → V4 (run V4 upgrade wizard) → V5 (run V5 upgrade wizard). Both upgrade wizards are idempotent, so running them in sequence on the same database is safe. Estimate 2-4 hours for the complete two-step migration on a database with 100,000+ posts, including pre-migration backup time and post-migration testing.
Common Post-Upgrade Issues and Their Fixes
After upgrading to APG vNext V5, some installations encounter one of the following common issues. Familiarising yourself with these before upgrading saves debugging time during production maintenance windows. CSS style regression: the new skin system loads stylesheets in a different order than the 4.x system, which can cause custom CSS overrides written for 4.x to lose specificity in V5. Fix by reviewing custom CSS and increasing selector specificity where needed. Search bar not appearing: V5 moved the global search bar to the responsive header template, which requires the updated skin. Custom skins that were only partially migrated from 4.x may be missing the new header partial. Fix by copying the header partial from the default V5 skin into the custom skin. Email notifications not sending after upgrade: V5 uses a new email queue table that requires the V5 migration script to be run. If the migration script was applied in stages, the email queue table may be missing. Run the targeted migration script section to create the missing table.
Related Resources
Looking for more help? Browse the support forum or check the Knowledge Base.