Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter nickth

    (@nickth)

    Wow, I figured it out, but it was explained NO WHERE. I had to add ../ to the Filemanager Default Home location. How do you honestly expect anyone to be able to use this plugin if something like that is not set by default or explained in installation clearly? Whack.

    Thread Starter nickth

    (@nickth)

    I only figured it out by looking at the second screenshot, which ../../ threw an error, then I cut it back to ../ and that worked. Now I can see wp-content.

    Plugin Author anantshri

    (@anantshri)

    Thanks for pointing that out.

    I did tried to point that at installation notes here https://www.ads-software.com/plugins/wp-filemanager/installation/:
    3. Update configuration (most importantly home_directory) and select relevent options.

    But looks like its still not clear and next release will make it more clear and i will try and upload a video explaining how to set it up.

    Thread Starter nickth

    (@nickth)

    No video required. Just a simple explanation on the Installation page about adding ../ or ../../ and when to use each… or put those in the configuration page as a dropdown selector or something to make it easier to get started.

    Deborah Delin

    (@deborahdelingmailcom)

    Thank goodness for this thread! I also would have had no clue what to put in the Default Home location.

    ../ seems to do the trick.

    Apart from that thank you for what seems to be an excellent plugin.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WP-Content and theme files are not accessible’ is closed to new replies.