Import source
Real Media Library compatibility
Test in progressChecks6 not run yet
ProductReal Media Library folders
Plathix Free can import a Real Media Library folder tree. RML keeps its folders in its own database tables, so the adapter reads them directly, including the parent links that make up the nesting. One known boundary: RML shortcuts — the same file listed in a second folder — are skipped, and only the real assignment is imported. The import copies the structure; it does not move files on disk and does not change attachment IDs.
Versions and environment
| Plathix | 1.0.0 Free |
|---|---|
| Reads | RML tables realmedialibrary and realmedialibrary_posts |
What was checked
| ID | What we did, and what happened | Result |
|---|---|---|
| IMP1 | A Real Media Library install is detected and offered as an import source. | Not run yet |
| IMP2 | The full folder tree is imported, including nested folders. | Not run yet |
| IMP3 | Every file keeps the folder it had in RML. | Not run yet |
| IMP4 | Attachment IDs and file URLs are unchanged after the import. | Not run yet |
| IMP5 | A file that exists in RML as a shortcut is imported once, in its real folder. | Not run yet |
| IMP6 | Running the import twice does not duplicate folders. | Not run yet |
Known limitations
None found in the workflows we tested.
Test setup
- Install and activate Plathix alongside Real Media Library. Nothing in RML needs changing.
- Open Plathix → Tools. A detected import source is listed there with the number of folders found.
- Run the import and compare the resulting tree with the RML one, shortcuts included.
Retest
Planned for the first migration test run; repeated on Real Media Library major releases.