• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved WordPress Toolkit - Different wp-content path

PetrusV

New Pleskian
Hi there,

For security reasons, I have changed the path for my wp-content location on all my wp sites to xyzabc-wp-content. It has served me well in avoiding numerous attacks over the years.

Of course, the new path is defined in my wp-config.php file and my sites work perfectly fine.

However, I cannot connect to WordPress Toolkit because it is trying to find the plugin in a location that does not exist. How can I rectify this?

Here is my error:
AH01071: Got error 'PHP message: PHP Warning: require_once(wp-content/plugins/wp-toolkit-management-plugin/wp-toolkit-management-plugin-agent.php): Failed to open stream: No such file or directory in /var/www/vhosts/mywebsite.com/httpdocs/wp-toolkit-entry-point.php on line 6PHP message: PHP Fatal error: Uncaught Error: Failed opening required 'wp-content/plugins/wp-toolkit-management-plugin/wp-toolkit-management-plugin-agent.php' (include_path='.:/opt/plesk/php/8.0/share/pear') in /var/www/vhosts/mywebsite.com/httpdocs/wp-toolkit-entry-point.php:6\nStack trace:\n#0 {main}\n thrown in /var/www/vhosts/mywebsite.com/httpdocs/wp-toolkit-entry-point.php on line 6'
 
I found a way to make it work. I followed the Manual Connect steps:

1. Downloaded and installed the plugin
2. Edited the wp-toolkit-entry-point.php in root of wordpress site and changed line 6 to my custom path
require_once 'wp-content/plugins/wp-toolkit-management-plugin/wp-toolkit-management-plugin-agent.php';
becomes
require_once 'xyzabc-wp-content/plugins/wp-toolkit-management-plugin/wp-toolkit-management-plugin-agent.php';

3. Manually coppied the Plugin end-point URL & Security token found in my WordPress site under Settings, WPT Management Plugin Settings
4. Connected site successfully

Everything's connected and the site is now visible under WorPress Toolkit!
 
Back
Top