• Resolved joost de keijzer

    (@joostdekeijzer)


    When moving a site from a Windows (IIS) server to (my local) macOS server I have the following issue:

    Normally the ai1wm-backups directory is inside the wp-content directory which on my machine is in the public_html directory.

    When I restore an ai1wm backup created on the Windows IIS machine I get the following situation:
    A directory with the (literal) name wp-content\ai1wm-backups is created in the public_html directory. So I get a directory with a backslash in the directory name.

    I did some research and found that the ai1wm-backups location is taken from a setting in the WordPress database. On windows, the default directory seperator is \ where on macOS and Linux it’s / .

    When I manually replace all \ to / in the database backup path all works as expected.

    The relevant code is in the constants.php file on the line where the AI1WM_BACKUPS_PATH constant is defined.

    I have not tested this, but perhaps calling the PHP function realpath() fixes the issue.

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

    (@yaniiliev)

    Hi Joost,

    Thanks for providing such detailed information about the issue you’re facing. I’m going to escalate this to our developers so they can try to reproduce the problem and apply a fix. We appreciate your input and will work on getting this resolved.

    Plugin Author Yani

    (@yaniiliev)

    Hi Joost,

    We’ve successfully replicated the issue. The problem arises when you set a custom backups folder during export, but fail to do the same during import.

    The plugin is designed not to overwrite its settings upon import, and we overlooked this aspect for custom backups folder. However, we will make changes to address this issue. If you import a backup with a custom “ai1wm-backups” path set, it won’t overwrite the existing one.

    Thank you for bringing this to our attention.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Wrong ai1wm-backups path when moving from Windows server to macOS’ is closed to new replies.