• Resolved osamahilal2000

    (@osamahilal2000)


    Hi,
    I have noticed that ai1wm-backups is essentially hard-coded in Database at wp_options during installation.

    The entry I’m referring to would be ai1wm_backups_path as the option_name – so when ever the website is migrated to a different server/path, it starts giving permission error due to it still having the older path.

    This is usually a pain and in resolving the issue as manual changes are required.

    Why cannot it use the ABSPATH of the wordpress system? That usually seems to be more of a robust answer to this.

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

    (@yaniiliev)

    Hi osamahilal2000.
    I hope you are well.

    The plugin handles ai1wm_backups_path at import. It will be replaced with the value of ai1wm_backups_path that the current site has. Let me illustrate this with an example:
    1. Export site 1 where backup_path = /www/backups
    2. Import the backup from step 1 to site 2 where backup_path = /site/backups
    3. After the import process, backup_path will be equal to /site/backups on site 2.

    What you are describing should never happen. The backup path is not transferred between sites.

    Thread Starter osamahilal2000

    (@osamahilal2000)

    Hi Yani,

    Thank you for the explanation! This example seems to rely on utilizing the plugins import feature. However, there are many events in migrations where clients prefer to either manually migrate the database or use a different tool for migration from hosting providers such as hostinger, Cloudways, Kinsta etc.

    This is usually where the failure point comes in. During my experience migrating a handful of sites, this is usually experienced when using any other solutions to migrate than the plugin itself. Its not a pain to change this – but it would be a nice to have feature as typically this is the only variable I have to change manually.

    Thanks!

    Running into the same issue, unfortunately I am not a pro. So how can this be solved? And is there a way to solve this from the outside? Unfortunately I cannot login to phpMyAdmin to adjust the entries. So any workaround from the WP Backend ist highly appreciated.

    Thread Starter osamahilal2000

    (@osamahilal2000)

    @td82td
    In that case, fetching your hosting support would be the way to go for now.

    @yaniiliev Any further insights? I see this case from time to time if the plugins migration/import feature is not used directly, which is usually common when people prefer to use a different migration tool, such as that of a hosting provider. Its not a huge issue to change it manually, but it would have been a nice to have feature as only aiwm is what we typically have to end up updating the path for.

    @osamahilal2000 thank you for your feedback. I am absolutely no pro with this plugin, but I know my way around the database. It is just unclear to me what needs to be done in the database in order to solve this issue. If you could tell me what you did in order to solve this, please?

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

The topic ‘HardCoded Entries on Database – Improvment’ is closed to new replies.