Setup
Overview
MAC Core is installed like a normal WordPress plugin, but it is maintained as an internal product rather than a public WordPress.org plugin.
Current runtime requirements:
- WordPress
6.9+ - PHP
8.3+
Current tested version:
- WordPress
7.0
Install and Update Source
Use one of these sources:
- the published ZIP from the GitHub releases page
- a checked-out copy of the repository in
wp-content/plugins/mac-core
This is not a plugin that should be patched directly on live sites. Treat the repository as the source of truth and deploy built releases intentionally.
Activation and Admin Screen
After activation, MAC Core adds a top-level admin menu entry:
MAC Core
The main screen lives at:
wp-admin/admin.php?page=mac-core
If the base route is opened without a tab query argument, the plugin redirects to the Settings tab.
Licensing
Licensing is handled inside the same admin area through the License tab.
- the licensing UI is powered by the bundled SureCart licensing SDK
- the tab renders inside the existing
MAC Coremenu instead of creating a second menu entry - if licensing is unavailable, the tab shows a warning instead of a broken screen
See Admin / License for the exact behavior and supported customization point.
Settings Storage
Plugin settings are stored in a single WordPress option:
mac_core_settings
The current modules are:
coremedia
Defaults come from the plugin schema, not from ad hoc UI state. Saved values are normalized and sanitized on write.
Uninstall Behavior
Uninstall cleanup is opt-in.
By default, deleting the plugin does not remove stored settings or related data. Cleanup only runs when the Delete plugin data on uninstall core setting is enabled.
When cleanup is enabled, uninstall removes:
mac_core_settingsmaccore_license_options- the SureCart version transient for
mac-core - the
mac_core_last_loginuser meta
Recommended Builder Workflow
- Install or update the released plugin.
- Activate it.
- Open
MAC Core -> Settings. - Enable only the policies needed for the specific build.
- Configure licensing if the distribution workflow requires it.
- Put project-specific logic in a child theme or site plugin unless it clearly belongs in shared
MAC Core.