• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Forwarded to devs WordPress Toolkit - Updating website with different WP_CONTENT_URL shows incorrect warning

Visnet

Basic Pleskian
Username: Visnet

TITLE

WordPress Toolkit - Updating website with different WP_CONTENT_URL shows incorrect warning

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.33.0
CentOS 7.9.2009 x86_64

PROBLEM DESCRIPTION

When updating a WordPress website that has the WP_CONTENT_URL constant configured, the update works, but the WordPress Toolkit says that the update failed with an incomplete warning message, for example:
Code:
The following errors have occurred while updating WordPress instance #2 ('https://example.com/admin'): - Unable to update plugin 'wp-sentry-integration`4.0.1`1`', details:

STEPS TO REPRODUCE

  1. Install the WordPress Toolkit extension.
  2. Install WordPress on a domain.
  3. Configure an alternative content directory by defining the WP_CONTENT_URL configuration constant.
  4. Update WordPress, a theme or a plugin through the WordPress Toolkit > Updates interface.
  5. Notice that the update action throws a warning, but the update(s) actually seem to have succeeded.

ACTUAL RESULT

The update action throws a warning, but the update(s) actually seem to have succeeded.

EXPECTED RESULT

The update(s) on a WordPress installation should only show a warning when something actually went wrong, or this warning message should be improved to clearly show what exactly went wrong.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Note that it's also impossible to Secure the option "Configure security keys" in the WordPress Toolkit when the WP_CONTENT_URL configuration constant is defined. Although this is probably a different issue, its cause might be related.
 
From developer:

I cannot reproduce the issue because after then I specified the WP_CONTENT_URL constant then my WP is not functioning correctly. So I have added WP_CONTENT_DIR that helped to fix the site. And after that my plugins and themes were updated correctly using WPT.
 
Back
Top