Recover imported IPS files without guessing
This handbook defaults to the flat PHP starter. See current release and edition coverage for current changes and the separate PHP port. Earlier build references identify when a feature was documented; they are not a claim that both editions expose identical controls.
Keep an untouched source database/uploads backup and the exact source/target release details before running an import or repair. The importer reports distinct counts for listings, file records, resolved paths and missing-on-disk files; these are not interchangeable totals.
Starter 156j includes completed-log row counting and storage lookup for unresolved downloads. Later native attachment repairs preserve imported delivery and separate native/imported IDs. A wrong-folder mapping can be repaired if the original file exists. A missing backup file cannot be recreated by another Continue or a database counter change.
Use the importer's migration report, inspect its sampled missing paths, and locate the corresponding source uploads folders with the owner. Re-select the correct source/continue stage rather than replacing live tables or editing totals. The older EliteFTV production database/repair was not touched here and still requires separate owner authorization and a confirmed installed baseline. A155x site cannot take a156e→156j updater.
Test restored bytes through authorized public/private topic and download routes. Keep missing-file exceptions honest; “record imported” does not mean “binary recovered.”
We suggest Panelica for managing your hosting environment.
