• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue WP Toolkit Parent Theme Updates

Atlantic1929

New Pleskian
Server operating system version
Debian 12.15
Plesk version and microupdate number
Plesk Obsidian v18.0.80_build1800260901.22 os_Debian 12.0
A few version updates ago Plesk changed how the parent themes update in WP Toolkit, in the past when a parent theme was updated it would keep the child theme as the active theme, now when the parent theme is updated it makes the parent theme the active theme, thus all the actual settings for the website are not gone as the child theme is no longer active. As I manage several hundred wordpress websites inside WP Toolkit it now requires me to go back over all the websites with child themes to re-active the child themes. This is a needless hassle that I should not have to do as per the older version of Plesk and WP Toolkit.

How to recreate:

Manually upload a parent theme with a higher version number, refresh the Themes page, the current theme will show the update link, click the update link to update the theme to the one uploaded. Now your parent theme is active and the child theme is inactive.
 
Thank you for the report, @Atlantic1929 . I was unable to replicate the reported behavior about the theme change during an update. The steps I performed:

1. Upload an older version of a theme
2. Create a child theme of the aforementioned theme
3. Activate the child theme
4. Update the parent theme from the WP Toolkit manager

Please let me know if any of the steps should be different. If these are the steps you followed, I would suggest getting in touch with Plesk support so they can conduct an investigation directly on the server and attempt to determine what exactly caused the theme change.
 
Back
Top