Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author lytechxdigital

    (@lytechxdigital)

    Hi! Thanks for the report — in Media Folder Manager you won’t see a separate “Parent folder” dropdown.

    For nested folders, the parent is set automatically based on what folder you currently have selected in the sidebar:

    1. Open Media Library (upload.php).
    2. In the left sidebar, click the folder you want to be the parent (example: <code class=””>TT).
    3. Now click New Folder.
    4. The new folder will be created inside the currently selected folder (so your <code class=””>qq becomes child of <code class=””>TT).

    If you click All Files (id <code class=””>0) and create a folder, it will create at the root level.

    If you’re still not getting nested behavior, please confirm you’re running the latest plugin version (we added the nested auto-parent behavior in v1.0.3). A quick cache refresh (Ctrl+F5) and a page reload after updating should also help.

    Plugin Author lytechxdigital

    (@lytechxdigital)

    Hi, thanks for reporting this and for testing with other plugins disabled.

    You’re right — this was caused by a class-loading mismatch during first activation (<code class=””>MFold_Ajax), and it could trigger a fatal on some installs.

    I’ve fixed this in v1.0.2 with a backward-compatible loader update so activation no longer fails when that class name variant is encountered.What to do now

    1. Update to Media Folder Manager 1.0.2 from WordPress.org.
    2. If your site is still on an older cached package, delete the plugin folder and install fresh.
    3. Activate again.

    If the error still appears after updating, please share:

    • current plugin version shown on Plugins page,
    • PHP version,
    • the exact new fatal log line.

    Sorry for the trouble, and thanks again for the clear report.

Viewing 2 replies - 1 through 2 (of 2 total)