ManYue NAS folder moves: verify paths, library entries and local copies

Moving a NAS folder can affect connection paths, scan scope and the identity of old entries. Test a small WebDAV or SMB folder before reorganising a full collection. Treat visible folders, readable pages and correctly associated reading records as separate results to verify.

Record the old path and reading anchor

Record the connection name, share or WebDAV base path, target folder and affected books. Note a chapter and scene for books in progress and keep existing bookmarks. Record account identity without copying passwords into the inventory. Verify any downloaded local copy separately so a remote-path problem can be distinguished from device-file availability.

Test a small copied folder first

Copy one or two test books to the proposed location while leaving the old path available. Check file completeness and the reading account’s permissions on the new parent folder. Keep contents unchanged and avoid combining the move with renaming or a server upgrade. Validate the path before deciding when the full migration and old-folder retirement should happen.

Distinguish the share from a subfolder

For SMB, distinguish host, share and the folder inside the share. For WebDAV, distinguish the server address from its base path. A move within one share differs from a move across shares. Do not paste a NAS-local filesystem path into a client URL field. Test the destination with the same account in a familiar file client, then verify ManYue separately.

Open the new location in the app

Edit the path or create a clearly named test connection using the current NAS interface. Keep the old connection until verification finishes. Refresh or scan where supported and wait for a stable result. Open actual early and final pages; an existing cover can come from cache and is not enough to demonstrate successful access to the new location.

Check entry identity and records

Compare the new entry’s name, chapter coverage and scene with the original record. Test resume and bookmarks directly; path changes may affect association. If both locations produce entries, label them before removing anything. Use chapter and scene anchors to establish the new position manually when needed. Data sync does not automatically solve every path-to-file identity mapping.

Check local copies independently offline

For a downloaded sample, disconnect and check beginning, middle and end from its local entry. One cached remote page is not proof of a complete copy. Conversely, local success does not establish that the new NAS path works. Keep these results separate and postpone cache or download cleanup until the new path and fallback copies are understood.

Keep a migration map after the move

Migrate additional folders in batches and check file counts, representative pages and active books. Retain an old-to-new path map and per-device verification status. Retire old connections or folders only after the relevant devices are checked through your NAS management process. A missing app entry alone does not establish whether a server original was deleted.

Questions and completion criteria

Why does a cover remain while pages fail? Cached artwork can outlive access to the original path. Can sync repair a moved folder? Record transfer and file relocation are separate tasks. Finish with complete destination files, valid account access, readable app pages, verified reading anchors and understood local copies. Use the retained old path as a reference if a batch fails.

Related guides and sources

Connect ManYue to WebDAV: check the address, library and downloads; Connect ManYue to SMB: browse NAS comics and keep offline copies.

Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.