Nextgen copy path for symlinked wp-content

Viewing 4 replies - 1 through 4 (of 4 total)
  • Benjamin

    (@benjaminowens)

    5 years, 6 months ago

    Sorry, NextGEN doesn’t support WP_CONTENT_DIR being a symlink for security reasons. Not that it helps, but in my personal experience I’ve found that symlinking wp-content breaks quite a few other plugins as well.

    However you can use mount --bind to achieve the same effect as a symlink.

    Thread Starter fivetr01

    (@fivetr01)

    5 years, 6 months ago

    Hello Benjamin,

    Thank you for your answer,

    Do you mean if i use mount –bind it will do the same effect as a symlink but will perform correctly ?

    Regards,

    Benjamin

    (@benjaminowens)

    5 years, 6 months ago

    Correct. mount --bind /mnt/nfserver/wp-content/ /var/www/wp-content/ will cause Linux to treat the two locations as one and the same, but each directory is treated as having unique files so beware of existing backup configurations possibly making duplicate copies.

    You can make that permanent in your /etc/fstab with:

    /mnt/nfserver/wp-content /var/www/wp-content none bind 0 0

    Thread Starter fivetr01

    (@fivetr01)

    5 years, 6 months ago

    Thank you for your answer. I can’t try directly that solution but i will definitely go that way

    Regards,

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

The topic ‘Nextgen copy path for symlinked wp-content’ is closed to new replies.

Tags