• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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

V

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.
 
You must log in or register to reply here.

Similar threads

M
Resolved Missing HTTP_HOST causes incorrect URL generation in WP Toolkit
Replies
12
Views
2K
Maarten
M
T
Issue WP Toolkit incorrect vulnerability and version reports
Replies
4
Views
852
TurnRound
T
F
Forwarded to devs PHP: Additional directives extension handling incorrect
Replies
7
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Bitpalast
Forwarded to devs Update to 18.0.63 #4 removed /etc/fail2ban/jail.local, crashed Fail2Ban
Replies
3
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
A
Resolved WP Toolkit: Live site cloned, clones using plugins folder of original site
Replies
5
Views
3K
ArmReu
A
Back
Top