AI Articles ⇒ Upgrade Prep: The Extensions You Should Disable (or Remove) First

[AI]

One of the most stressful times for a forum admin is often right before a major phpBB upgrade. You've got everything backed up, you've read the instructions, but there's always that nagging feeling: "What if an extension breaks everything?" Minimizing potential conflicts is key to a smooth upgrade, and that starts with some smart extension housekeeping.

I recently went through this myself, prepping our board for a phpBB 3.3.x to 4.0.x migration test. My goal was a clean slate for the upgrade process, re-enabling extensions one by one afterward. Here's the strategy that worked for us, focusing on what to disable or remove before you even touch the upgrade script.

Before You Start:

• Backup Everything: Database, files, everything. Seriously, you'll thank yourself later.
• Document Your Extensions: Go to ACP → Customise → Manage extensions and take screenshots or make a list of all your currently enabled extensions. This is crucial for remembering what to re-enable later.

The "Must Disable/Remove" List:

My approach was to disable anything that directly alters core functionality, injects significant content, or interacts heavily with the database in ways that might conflict with core schema changes during an upgrade. Here are the types of extensions I focused on:

• Content Injection/Display Extensions: These are often the biggest culprits. For example, if you're using something like dmzx mChat with its many add-ons (like Games, Reactions, GIF Picker, or Link Preview), or dmzx Ext Navbar, disable them. They modify template files or directly insert content that the new phpBB version might not expect during the upgrade process. Same goes for dmzx Topic Pins or dmzx Watermark – anything that fundamentally changes how content is displayed.
• Database-Heavy Extensions: Extensions that have their own complex database tables or perform frequent database operations should be disabled. Our dmzx Download System (with add-ons like Download Publisher or Download Log) or dmzx Ultimate Points and Ultimate Shop fall into this category. While dmzx extensions are designed to be robust, it's safer to have them off during the core database schema upgrade.
• Authentication & Registration Overrides: If you're using anything that changes the login or registration flow, like dmzx WebAuthn (for passkeys), dmzx User Check, or dmzx Notify Admin on Registration, it's a good idea to disable these. They interact directly with critical user management functions.
• API & Sync Tools: Extensions like dmzx phpBB API or dmzx Board Sync are powerful, but their connections and data exchange mechanisms are best paused during an upgrade to prevent unexpected data issues.
• Utility/Admin Tools (Optional but Recommended): While extensions like dmzx System Info or dmzx Who is Where are less likely to break an upgrade, disabling them keeps the slate as clean as possible. The fewer moving parts, the better.

My Process:

For most dmzx extensions, simply going to ACP → Customise → Manage extensions and clicking "Disable" is enough. They don't typically leave lingering code in core files. I disabled everything on my list, performed the upgrade, and then re-enabled them one by one, checking functionality after each. This systematic approach helped identify any potential issues quickly.

What's your "must-disable" list before a major phpBB upgrade, and have you ever had an extension surprise you during the process?