Background Import Jobs and Progress​

Summary: Background import jobs make large Antimanual Builder Pro imports more stable by processing ZIP projects in stages, showing live progress, and generating per-page previews for safer migration and review before final editing.

Background import jobs in Antimanual Builder Pro let large uploads continue processing after the file transfer is complete. Instead of holding the browser on one long request, the importer assembles the project, creates pages in stages, and shows live progress as each step finishes. This makes large ZIP imports more reliable on servers with limited memory or strict timeout settings.

This workflow is designed for substantial migrations, not just small single-page transfers. You can monitor the current import state, review per-page previews as content is generated, and verify results before moving on to manual edits. For related setup and upload guidance, see and .

How background import jobs work

When you upload a large ZIP project, Antimanual Builder Pro processes it in stages. First, the archive is uploaded in chunks and assembled in a protected import directory. Next, a background job analyzes the project, resolves pages and assets, and creates content without requiring a single uninterrupted server request.

This approach reduces the risk of timeouts and failed requests during heavy imports. It also improves stability on hosting environments that impose low PHP memory limits or aggressive request execution limits.

• Chunked uploads break large files into smaller transfer units.
• Background processing avoids long blocking requests in the browser.
• Progress indicators help you follow the import as it advances.
• Per-page previews let you validate output before final editing.

What you see during an active import

While the background job runs, the importer displays progress updates so you can see how far the operation has advanced. This visibility is especially helpful when importing a site with many pages, multiple assets, or a complex folder structure.

In addition to progress feedback, the system can generate per-page previews. These previews help confirm that the import is assembling pages correctly and that content is being interpreted as expected. If a page requires adjustment, you can identify it before beginning detailed manual refinement.

• Live progress updates show the current stage of processing.
• Page-by-page creation makes the workflow easier to track.
• Preview output helps verify imports before post-processing.
• Large projects remain manageable because processing continues in the background.

Why background jobs are more reliable for large sites

Large imports often fail when everything is processed inside one request. Background jobs solve that problem by splitting the work into smaller operations. The browser can remain responsive while the server continues building the project in stages.

This design is particularly useful when importing large archives with many assets or when migrating from older sites with extensive content. It allows the importer to continue even when a single synchronous process would likely exceed server limits.

Security and access control

Background import jobs are protected by the same security-first import pipeline used throughout Antimanual Builder Pro. Import endpoints require the proper WordPress capabilities, and each job is scoped to the user who created it. The Pro license is also required for import routes to be available.

Imported content is sanitized during save and render operations to reduce the risk of unsafe markup. The import system is designed to work within a controlled builder environment rather than exposing arbitrary code execution features.

• Only authorized users can run and manage import tasks.
• Jobs are tied to the user who started them.
• Imported markup is sanitized before it is stored and displayed.
• Temporary chunked uploads are handled in a protected directory.

Where import files and assets are stored

Imported assets are stored under wp-content/uploads/antimanual-builder/. Large chunked uploads are assembled separately in wp-content/uploads/ambld-import-chunks/, which is protected from direct web access and cleaned up after the import completes.

This separation keeps temporary upload data isolated while the job is running and helps maintain a cleaner, more predictable asset structure inside WordPress.

Best practices for large imports

For the best results, use background import jobs when you are moving a large ZIP project or a site with many linked pages. If the archive is very large, ensure that the server has enough disk space and that the importing user has the correct page editing and file upload permissions.

• Use background jobs for multi-page or asset-heavy projects.
• Watch progress before moving to final design edits.
• Review per-page previews to catch structural issues early.
• Confirm that the free plugin and Pro license are active before importing.

If you want to understand the broader workflow around large site transfers, continue with and The Advantages and Disadvantages of Developing a Custom WordPress Theme. These sections explain how data is processed, protected, and prepared for editing inside the builder.

Summary

Background import jobs make large imports more stable, visible, and manageable. By combining chunked uploads, staged processing, live progress, and per-page previews, Antimanual Builder Pro gives you a safer workflow for substantial migrations and complex site rebuilds.