A Admatic StackDocumentation 5.14.2
Download stack DA

Admatic Stack

Documentation for release 5.14.2

Search, install, operate and repair the coordinated Elementor website-production stack.

Search

Browse

Documentation

Installation

Stack architecture

Using the builder

Design & media

→ Troubleshooting

Updates & maintenance

Version note

This site documents stack 5.14.2. The stack is expected to evolve, so update the version badge and changed procedures when publishing a new coordinated bundle.

Troubleshooting

Find the first failing layer, repair the exact issue and continue the same project. Most failures are version, pairing, temporary-file, media-reference, package-validation or rendered-QA problems.

Start with the correct diagnostic layer

1. Core health

Check Core readiness, connector scopes, capability negotiation, project state and paired-site status.

2. Staging preflight

Check component versions, Elementor/Pro pairing, Worker state, ZIP support, OpenSSL, temp files, uploads and background jobs.

3. Workflow report

Read the first failing stage, package validation rows, screenshot QA and release-gate blockers.

Common errors and fixes

Install the exact coordinated staging versions. For the 5.14.2 false-mismatch issue, replace central Core with 2.14.3 and run all health checks. Core now compares contracts semantically and accepts compatible Core patch releases within the same major/minor line.
Update the licensed Elementor Pro package so its major/minor version is not older than Elementor Core, then rerun preflight.
Open Remote Worker on staging, generate a new ten-minute code, paste the pairing bundle into Core → Sites and rerun health checks.
Disconnect the stale Worker record and pair again. Do not reuse an expired code.
Configure a writable PHP temporary directory and verify that WordPress can create a temporary file. Rerun staging preflight.
Enable PHP ZipArchive or ensure the WordPress PclZip fallback is available before importing a package.
Update to the coordinated Kit Factory release, clear browser and WordPress caches, reload the modern workspace and check the REST workflow response. The current release includes null-safe workflow bootstrap handling.
Do not treat the number alone as a design score. Verify that global header/footer are approved and every page section has either approved-component evidence or an executable bounded-native composition.
Confirm the files entered Media Library and the current project manifest before navigating away. Reattach missing assets by stable references and regenerate the current project package instead of creating a new project.
Repair the exact missing reference on the same Core project. Core reports the unresolved key so the media manifest can be corrected without replacing the project.
Check for project.json, supported schema, allowed file types, package-size limits, local asset files, valid relative paths and no remote-only Elementor images.
Install local Chrome/Chromium or configure the central Screenshot QA endpoint. Capture-only warnings may be advisory, but missing rendered comparison evidence blocks a reference-led release.
Read the blocking reason. Correct the named region, reference or package failure, then rerun the same project. Poll the existing workflow rather than rebuilding only to check status.
Confirm Elementor Pro is active, pages use elementor_header_footer, the templates use the header/footer taxonomy and include/general entire-site conditions, and the required frontend markers are present.
Remove negative margins and direct positioning, set explicit mobile widths and use a one-column mobile Grid. Leave Elementor Flexbox Container Wrap/No Wrap controls blank unless a specific design requires a deliberate override.

What to collect for support

  • Stack version and each coordinated component version.
  • Explicit Core project ID and current revision.
  • Paired staging site ID or label.
  • Workflow ID and first failed stage.
  • Package validation summary and blocking rows.
  • Release-gate status.
  • Screenshot QA report and failing regions.
  • Core execution trace or companion diagnostics file.
  • The exact missing media reference or contract mismatch.

Keep secrets out of tickets

Do not paste OAuth tokens, HMAC secrets, private filesystem paths or raw credentials. Core and browser diagnostics are designed to redact them.

Safe recovery rules

  • Continue the existing explicit project.
  • Do not duplicate a project solely because a build or QA pass failed.
  • Do not replace persisted media unless the referenced asset is actually wrong.
  • Use the latest change preview before a destructive rebuild.
  • Create or retain a recovery snapshot before replacement builds.
  • Poll the existing workflow until it reaches a terminal state.

When all normal fixes fail

Using AI assistance such as Claude or ChatGPT is permitted and may help identify the failing layer, interpret logs, compare versions or propose a safe repair plan. Remove credentials, tokens, secrets and private paths before sharing diagnostic material, and verify any proposed change before applying it to production.