How to Fix Missing Branding Options in AMP Advanced Edition

If you've got AMP Advanced Edition and noticed that the branding configuration options have mysteriously vanished from your panel, you're not alone. This is a known issue that can occur after updates or configuration changes, leaving you without access to one of the key features you paid for.

The good news? There's a simple command-line fix that takes less than a minute.

The Problem

You have a valid AMP Advanced Edition license, but when you navigate to Configuration, the Branding section is completely missing. You can't customize your company name, logos, or any other branding elements that should be available with your license tier.

The Solution

The fix involves using AMP's built-in configuration tools to force-enable the branding display setting. Here's how to do it:

Step 1: Switch to the AMP User

First, you need to log in as the amp user. This is crucial because AMP's instance manager needs to run with the correct permissions.

sudo su -l amp

Step 2: Stop Your ADS Instance

Before making configuration changes, stop your ADS01 instance:

ampinstmgr stop ADS01

Step 3: Reconfigure with Branding Enabled

Now run the reconfigure command to explicitly enable the branding display setting:

ampinstmgr reconfigure ADS01 +Core.Branding.DisplayBranding True

This command tells AMP to add (the + symbol) the Core.Branding.DisplayBranding setting and set it to True for your ADS01 instance.

Step 4: Restart ADS

Start your ADS instance back up:

ampinstmgr start ADS01

Step 5: Clear Your Browser Cache

This is important! Your browser might have cached the old configuration panel layout. Clear your cache or do a hard refresh (Ctrl+F5 on Windows, Cmd+Shift+R on Mac) when you log back into AMP.

Verify It Worked

Log into your AMP panel and navigate to Configuration. You should now see the Branding section appear in the configuration menu, complete with all the customization options like:

• Company Name
• Custom Logos
• Background Images
• Color Schemes
• Footer Text

Why Does This Happen?

This issue typically occurs when:

• AMP updates don't properly migrate all license-specific settings
• Configuration files get corrupted or reset
• The instance was created or upgraded in a way that didn't properly initialize Advanced Edition features

Wrapping Up

Missing configuration options can be frustrating, especially when you've paid for premium features. Fortunately, AMP's command-line tools make it easy to fix these issues without having to reinstall or recreate your entire setup.

Keep this guide bookmarked - you might need it again after future updates!

Having other AMP-related issues? Check out the official CubeCoders documentation for more troubleshooting guides and tutorials.