ManYue Wi-Fi folder previews: distinguish identically named pages by relative path

When two folders both contain cover images, final filenames alone cannot audit a Wi-Fi directory import. Trace four loose pages from relative paths through preview grouping to imported images, beyond the introductory single-file transfer. No fixed grouping or automatic deduplication is guaranteed; confirm the proposed scope before proceeding.

Prepare two distinct groups with matching final names

Make two owned groups on the computer, each with a cover and body image visibly marked by group and page role. Example paths are alpha/cover.jpg, alpha/001.jpg, beta/cover.jpg, beta/001.jpg. These are four different full paths, not four records of one file. Record sizes, marks and intended group, retaining originals separately rather than testing a restricted library. Keep the sample far below the published individual-file limit, checking current page limits too; individual compliance does not guarantee acceptance of any batch total.

Fix the current session and selected directory level

Start and pair the current Wi-Fi import session through the existing workflow on a trusted mutually reachable network, using its actual address rather than an old session. Record whether you select the common parent containing both groups or each subdirectory separately: selection scope affects the relative root. If the browser lacks directory selection, mark this method unsupported rather than inventing guaranteed drag-and-drop equivalence. Retain the required service state without opening router access to the internet. Keep account/device aliases and session time personally; omit pairing codes and private network details when sharing.

Retain more than each final filename

If the browser shows a file list, record its actual names and hierarchy. If full paths are absent, distinguish them in your source ledger and state the page limitation. Directory-upload APIs explain relative-path information, not identical behaviour across every browser and page. Two cover rows do not alone prove duplication, and tidiness does not justify deleting one. If the selection root makes group identity unclear, cancel and inspect scope before submission instead of inferring afterwards what must have been sent.

Match preview groups to the source ledger

When a preview appears, record proposed book titles, chapters, page counts and target grouping before matching all four paths and marks. Its proposal may differ from yours; the two-group example does not promise two app books. If body-image ownership is unclear, pause confirmation and reorganise a copy or select a smaller scope. A total of four images does not certify correct grouping: an incorrect merge can retain four. Every source item should have an identified destination rather than an invented hierarchy filling preview gaps.

After confirmation, verify identities with all four marks

Proceed only when the preview is understood and matches this task. Open each resulting work or chapter and check group cover, body mark and neighbours, recording displayed name and position. A cover from A with B’s body is a mapping failure despite clear images. Transfer completion, import processing and readable output remain separate, but the main evidence here is path-to-content identity, not basic networking. If one source group is absent, mark its result unresolved instead of deleting successful objects from another group and retransmitting everything.

Use the ledger to bound retries after partial success

For each item record mapped success, not submitted, processing, failed or unknown using actual evidence, without requiring identically named UI buttons. Do not retransmit a confirmed group together with an anomalous group unless deliberately making a distinguishable control. Before retrying, verify the original sample and intended target scope, retaining both attempts and session identities. Use a visible retry control only under its actual scope; otherwise manually select the confirmed small subset. No automatic duplicate prevention is promised, and partial import never justifies deleting the whole source directory.

Troubleshoot selection roots and flattened previews

For unexpected hierarchy, check parent-versus-subdirectory selection, then the browser list, preview and app result rather than blaming image corruption for every path issue. A page showing final names only does not prove the server discarded paths. A clearly prefixed copy can serve as a control, but disclose that names changed. Do not rename a production library to accommodate one preview. If the version cannot express your intended organisation, cancel and import distinguishable small groups separately, recording the limitation rather than promising an undiscovered setting.

Close the service and revisit all four ledger items

End the transfer service through its available control, exit the reader and return to each object to recheck all four cover/body marks. Retain selection root, relative paths, source identities, preview proposals, actual destinations and retry scope, leaving unseen fields unknown. Completion is not merely “four images transferred,” but traceability to groups without blind resubmission of successes. Different directory structures need a new preview audit; one sample does not guarantee identical merging for all nested folders, and Wi-Fi transfer does not automatically back up the source directory.

Related guides and sources

ManYue Wi-Fi import: upload a comic from a computer browser; Import image folders into ManYue: one book or separate chapters.

Checked on November 11, 2026: Apple public information lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the official App Store for published capabilities; verify specific controls in the installed version.

Method reference: MDN: File Relative Paths in Directory Selection. Samples, passages and controls are original exercises. Sources establish definitions and checking methods rather than new automatic analysis in the app. Manual records may be kept externally, and unknown fields should remain explicit. This article does not claim step-by-step testing on a physical device, private server or every output environment.