Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
- Unable to refresh WP instance in the WP Toolkit of Plesk, because it is always reported as BROKEN
- The following error appears in the WP Toolkit logs:
PLESK_ERROR: Site data was not refreshed due to the following error: Failed to reset cache for the instance #13: . Cache tags: ["action-log-existence","main-information","ip","ssl-statuses","remote-agent-instance","cloud-linux-cagefs","cpanel-links","admin-credentials","admin-login-link","php","plugins","themes","config","nginx-caching","maintenance-mode","table-prefix","force-updates","security-measures","protected-dir","screenshot","virtual-patches"]
-
The Plesk GUI reports that the operation is successful via the following message:
PLESK_INFO: WordPress data was reloaded
- A Short PHP open tag is used in
wp-config.phpfile of the WP installation (<?instead of<?php)
Cause
This issue is tied to a known Plesk WP Toolkit bug with ID #EXTWPTOOLK-10429 and will be resolved in future versions of Plesk.
Note: Please click the Follow button near the article headline to stay informed - you will receive an update via email when the bug is fixed
When the bug is fixed permanently, this will be recorded in the Change Log for Plesk Obsidian
Resolution
As a workaround, you can do the following:
1. Log into Plesk
2. Go to Domains > example.com
3. Open the File Manager
4. Navigate to the main directory of the WP installation
5. Open the wp-config.php file for editing
6. Change the PHP opening tag in the wp-config.php file of the affected WordPress installation from <? to <?php
7. Save the changes
Comments
Did not fix it for me. The opening tag was already <?php in the wp-config.php file
It is already <?php and not fixes.
Please sign in to leave a comment.