• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by ArmReu

  1. A

    Issue Custom define( 'WP_PLUGIN_DIR' ...) in wp-config.php can sort interfere badly with cloning process

    Hi! I literally by accident found out that the existance of a custom define( 'WP_PLUGIN_DIR' ...) in wp-config.php sort of ruins the clone process as it is not checked for and is 1:1 taken to the new close which mich cause the wordpress installation to act strange or even be broken as this even...
  2. A

    Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site

    Update and appologies: It turned out all the trouble were simply caused by a custom added define( 'WP_PLUGIN_DIR' ...) in wp-config.php which had a fixed path in it. So I guess it is not really a problem of the cloning process. Yet perhaps the devs should be informed that this variable...
  3. A

    Resolved Plugin path not corrected/re-written during cloning process

    Update and appologies: It turned out all the trouble were simply caused by a custom added define( 'WP_PLUGIN_DIR' ...) in wp-config.php which had a fixed path in it. So I guess it is not really a problem of the cloning process. Yet perhaps the devs should be informed that this variable...
  4. A

    Resolved Plugin path not corrected/re-written during cloning process

    When creating a clone of a wordpress site the plugins path is not corrected/re-written during cloning process. It always stays the same as in the original site, even if you are cloning into a different subdomain or even full domain. Files are copied correctly, just the correction of the plugins...
  5. A

    Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site

    Okay ... now it gets even more confusing ... and concerning: I did another clone of the site but to a different domain. And even here the plugin path remains the same to the original site/domain. I checked the plugins folder of the cloned sites and it looks like all the files have been copies...
  6. A

    Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site

    And highly related to this: If I remove a wordpress installation from wordpress toolkit, where the plugin path is set to outside the normal wordpress path, will the plugin directory still be deleted, even if it "belongs" to another wordpress installation managed by wordpress toolkit too?
  7. A

    Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site

    A little update: I just created another clone of the live site (without any errors) and the new clone shows exactly the same problem. All directories are corrent pointing into the subdomains folders except the plugin directory. This - again - is pointing to the plugin directory of the live...
  8. A

    Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site

    A little typo in my post: 2. I am searching for a way to fix this, ideal would be to now having to recreate the dev and stage clones again. That was ment " ..., ideal would be NOT having to recreate the dev and stage clones again." Sorry about that.
  9. A

    Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site

    Hi everyone! I have experienced some very strange behavior with a clients site, or with its clones to be more precised The situation: I had a live site managed in Wordpress Toolkit and everything works fine (WP Toolkit version: 6.1.2-7079, Web Admin license). I cloned the live site into two...
  10. A

    Resolved Backup Manager times out and unusable after failed remote backup

    For those running into the same problem, here the way I solved it: Reduce Timeout for FTP in /usr/local/psa/admin/conf/panel.ini to something like [pmm] ftpResponseTimeout = 30 ftpConnectionTimeout = 60 ftpRequestTimeout = 60 In Plesk to into Backup Manager and wait the seconds you have set...
  11. A

    Resolved Backup Manager times out and unusable after failed remote backup

    A little update on the issue: Using the changes suggested in the link below I was able to access the backup manager settings after waiting for the time set in the parameters...
  12. A

    Resolved Backup Manager times out and unusable after failed remote backup

    Hi everyone, I am facing a somehow strange problem: We are running local and remote backups (via FTP) on a regular base and everything worked fine. Last night the provider where the FTP-space is located had a problem and so the backup could not be completed. I received a notification mail...
  13. A

    Resolved Ubuntu: Plesk Obsidian 18.0.47 after Update 5: inconsistencies were detected in the system's package manager database

    I forget to add the info coming after the update process: Grund: 2022-10-31 09:45:34 INFO: pum is called with arguments: ['--update', '--json'] 2022-10-31 09:45:35 INFO: no packages to update 2022-10-31 09:45:37 ERROR: installArchives() failed 2022-10-31 09:45:37 ERROR: Exited with returncode 1.
  14. A

    Resolved Ubuntu: Plesk Obsidian 18.0.47 after Update 5: inconsistencies were detected in the system's package manager database

    Hi everyone! I am running Plesk Obsidian 18.0.47 Web Pro Edition on Ubuntu 20.04.5 LTS for about a year now without any problems/issues at all. Since the (automatic) Plesk Update 5 about a week ago I keep getting messages in the system updates panel within Plesk: Warning: Information on some...
Back
Top