Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
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
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...
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...
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...
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...
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...
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?
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...
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.
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...
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...
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...
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...
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.
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...
I dropped the trigger within phpmyadmin. Turned out it was a fragment of an old malware infection.
Dropping it did not effect wordpress in any way. So all good now. Question can be closed.
Update: I found out where and how to drop the trigger in phpmyadmin. What I am wondering now is if it is safe to just drop it.
I have a cloned version of the website (not using WPTK) and checking the database there the trigger doesn't exist.
The trigger is assosiated to a necessary yet empty...
Hi everyone,
I am trying to clone a wordpress installation within Wordpress Toolkit 5.12.3-6596 (pro version) on on Plesk 18.0.46 Linux. I am cloning into a blank subdomain.
Cloning starts normaly
Copying files without errors
Copying database fails with ERROR 1142 (42000) stating a line in...