Creating many pages in one long request is fragile. Shared hosting often stops a PHP request after a set time, and a run that dies halfway leaves you guessing which rows were written. PageForge avoids this by working through your data in small batches.
How a run works
After Check and preview, click Generate N pages now. From then on:
- The browser sends five rows at a time to your site.
- Each batch creates or updates its pages and reports back.
- The progress bar and the counter, such as
35 of 100 rows, move forward. - Skipped or failed rows are added to the log with their row number and reason.
When the last batch finishes, the log ends with a summary:
Done. Created 92, updated 0, unchanged 0, skipped 6, failed 2.
Keep the Generate screen open while a run is in progress. The batches are sent by that browser tab.
When the server stops responding
If a batch request fails, PageForge tries again once with a single row. If that works, the run carries on. If it fails again, the run stops and the log says where:
The server stopped responding at row 41. Pages created so far are kept.
A Resume from row 41 button appears. Click it to continue from that row. Rows before it are not sent again.
If the same row keeps failing, look at that row in your data first, then at your server’s PHP error log, which usually names the cause. A host time limit or memory limit that is set very low can also stop runs on larger layouts. See Generation stops or times out.
Stop a run yourself
Click Stop to pause after the current batch. The log shows Stopped at row 58. Pages created so far are kept., and Resume from row 58 continues where you left off.
If you closed the tab
In the free plugin, Resume works while the Generate screen stays open. If you reloaded or closed it, start again with the same template, data and Skip it (create new pages only). Check and preview reports the pages that already exist as skipped, so only the missing rows are created.
PageForge Pro remembers an interrupted run in your browser, so Resume is still offered after a page reload.
Reading the summary
| Count | Meaning |
|---|---|
| Created | New pages written |
| Aktualisierten | Existing pages changed in update mode |
| Unverändert | Existing pages where the row and template produced the same result |
| Blau | Rows not written by design, such as duplicates or pages edited by hand |
| Failed | Rows that hit an error, such as a slug that came out empty or a permission problem |
Failed and skipped rows are listed above the summary. Fix the data or template, then run again. With Skip it, pages created earlier are skipped, and the fixed rows are created.
Large campaigns
The free plugin runs up to 100 rows per run. Split longer lists into several files and run them one after another.
Pro PageForge Pro has no row limit. On Starter and higher it can also queue rows for a background scheduler instead of running them in the browser, with automatic retries. See Queue, scheduling and drip publishing.
