WordPress.org

Ready to get started?Download WordPress

Forums

Duplicator
[resolved] Duplicator warning long path names (4 posts)

  1. thorpemark
    Member
    Posted 4 months ago #

    Hello. I tried searching this out but am new to WP and DUPLICATOR and could use a point in the right direction kind of thing.

    Duplicators scan turned up 2 warnings for bad path names. In my case it is long path names. One is 204 chars and is to a NextGen thumbnail (I can change this by shortening the image name used there. I use long image names like tags.. bad habit. The second is 215 chars and is to a NextGen PHP file ending in..

    ..nextgen_basic_slideshow_settings_gallery_dimensions.php

    Unfortunately, my root folder is rather long on my shared server as well..

    /home/ballati/public_html/balloon-decorator/wp-content/

    I have WP in that subdir of my public_html dir now and it works. What I want to do is install the current WP in my public_html directory and do without the redirect I have there now. Then I want to start using the balloon-decorator folder as a development folder and change its name to something much shorter.

    I think duplicator can help with that... if I can get past this path length issue. But maybe what I need to do is just look at the current site (which is small) as a place-holder and just develop a whole new dev site that will keep name lengths in check and eventually move that one to become the live site one day.

    Any advice is appreciated.

    https://wordpress.org/plugins/duplicator/

  2. Cory Lamle
    Member
    Plugin Author

    Posted 4 months ago #

    Hey Thorpemark,

    Acutally if the length is below 256 characters you should be good. I put the warning at 200 characters just to warn users that their might be an issue if the path continues to grow.

    Basically is what happens with zip programs like winrar/winzip and even the PHP library used to extract the files is that they work fine to package up the files, however when they are extracted on some operating systems such as windows they run into a path limit.

    All of the items on the scan page are simply warnings and you can still proceed to run the build. They are just placed there to give you a heads up should something go wrong when creating the package or installing it. I would go ahead and try to build the package and see if it builds.

    One way to validate if the zip file is corrupt or unusable when extracted to its new destination, is to try and extract it with a program like winrar and it will throw errors about file length issues if they are present...

    Cheers~

  3. thorpemark
    Member
    Posted 4 months ago #

    Thank you much!

  4. Cory Lamle
    Member
    Plugin Author

    Posted 4 months ago #

    No problem, glad to help and its something I need to add to the FAQ...

Reply

You must log in to post.

About this Plugin

About this Topic