Offer WHITE LABEL w/ fields for Super Reseller's PLID, Name, Logo, and Plugin Name

[nelsonknelson]

Super Resellers need a White Label version where "GoDaddy" is not seen in the Plugin Name nor Dashboard Controls nor Settings, and especially not at Sign-In/Account Activation.

Features: This would be a downloadable version of the plugin where the Super Reseller enters into (a) configuration file(s) the following White Label settings, then re-zips and distributes plugin to his or her Pro/Basic Resellers for them to deploy:

• 1. - PLID of the Super Reseller account (needed?)
• 2. - Plugin Name as Super Reseller wishes it to appear in Plugins and Dashboard and Settings
• 3. - Author Name wherever it appears to user as "GoDaddy" (needed?)
• 4. - Company Name as Super wishes for it to appear (wherever "GoDaddy" appears now)
• 5. - Logo(s) (by URL to file) as Super wishes them to appear for Plugin itself and in user's Plugin list, Dashboard, Settings, and anywhere else.
• 6. - Links to help pages on godaddy.com - Super provides alternates, writes his own help pages
• 7. - Links to this Repo on GitHub (either Super provides alternate, or removed completely)
• 8. - Remove "GoDaddy" option at Sign-In Account Activation Screen (attached img)
• 9. - Updates function normally from your repo and do not over-write White Label settings -- else perhaps provide an option to set our own repo location to be polled for updates we would make manually to each GoDaddy-issued update if updating White Label versions is problematic

(Looking over the code cursorily, it seems we could likely achieve most of this ourselves with code changes, but they would get wiped with updates. Also there may be back-end changes needed to function and/or to get authorized updates.)

NO Changes Needed (thus making this version less work) would be any changes to the following (since I don't think any have "GoDaddy" in the name, or aren't seen by users):

• Same Module names,
• Same Shortcode Names/IDs
• Same Classes, Packages, Slugs, Products, other Post-Elements
• Same Javascripts (users don't see these)
• Same Variable Names & Notations in Code (most users would never dig this deep)
• Same API variable names, values, and API-called URLs
• Same secureserver.net URLs (since any of these already link to user's cname-pointed subdomain or query-string appended secureserver.net URIs carrying user's own branded pages)

And, no separate "generic" repo is needed... just so long as this GoDaddy-branded repo (here) is not linked to from the Plugin or its controls

The only other thing needed would be backend changes.

At Update time, it's even possible the same update could be pushed out to both White Label and GoDaddy-branded versions, so long as the master code used variables rather than hard-code anywhere "GoDaddy" appears. (We didn't notice many places "GoDaddy" appears hard-coded, other than "@author" type PHP code comments -- and those wouldn't need to be changed/removed anyway.)

Attached: