Search results

I would also like to note that changing the table prefix during the installation is safe and shouldn't cause any issues. Changing the table prefix for an existing site, though, might cause issues with certain plugins and themes written by inexperienced or careless developers.

Hi everyone, We're planning to introduce the ability to define the default DB table prefix in the upcoming WPT 4.9 release. This feature will allow server admins to make sure that all new WordPress installations on the server have the same table prefix they've defined in the Global Settings...

Hi @MicheleB, This is not a known issue, so we're going to check it out ASAP. Thanks for letting us know.

Hi @B4c4rd1, This issue was fixed in WPT 4.8.2, which was published a couple of minutes ago. Let us know if you continue to experience any related issues.

The issue was fully fixed in WPT 4.8.2, which was published a couple of minutes ago. Let us know if you continue to experience any related issues.

Hi everyone, We've found out that the hotfix released in WPT 4.8.1 hasn't addressed the issue for all cases, so we're preparing a WPT 4.8.2 hotfix that should conclusively address it. We're planning to release WPT 4.8.2 a bit later today, on 2nd of June. I'm really disappointed and I feel your...

WPT 4.8.0 was published several moments ago. Changes: [+] Server administrators can now define default WordPress installation language in the global WordPress Toolkit settings. [+] CLI command for enabling and disabling Smart Updates on a site was added. Run plesk ext wp-toolkit --smart-update...

@Prod Juan The fix you've requested is released in WPT 4.7.2, out today. Have a good day!

Whoops, this is embarassing. :oops: We'll fix it in WPT 4.8, promise!

WPT 4.7.0 was released a couple of minutes ago. Here are the changes: [+] WordPress Toolkit now can update paid plugins & themes, if these updates are available in the WordPress admin area. Note that certain plugins and themes do not support automatic updates, but display notifications about...

Hey guys, this is a known issue (ID for reference: EXTWPTOOLK-4622), and we've already fixed it in the upcoming WPT 4.7 release. We plan to release WPT 4.7 in a couple of weeks. Stay tuned for the announcements!

@Bobbbb, @gbotica Well, this is going to be awkward... The issue was technically fixed in the WPT 4.2.0 release. Here's the corresponding line from the release notes: Problem is, we've shipped the code that fixes the issue, but we forgot to enable it (yes, you've read that right). I know...

Hi @Prod Juan, this seems quite logical and reasonable. I'll see when we can do this. Thanks for the image, this helps a lot!

WPT v4.6 is out! Changelog: [+] WordPress administrators can now automatically update their website URL in the WordPress database and wp-config.php file based on the actual current URL. This procedure is particularly useful after migrating a website from a different location like your local...

@MicheleB WPT 4.6.0 will be published later today. However, it will not include the fix for this bug, because, as I've stated earlier, there's not much we can do with this right now -- the issue is with CageFS behavior, which is out of our control at the moment. We will try reaching out to the...

Hi @MicheleB, The good news is that based on our investigation you can actually fix this problem right away without having to wait for someone or something. The bad news is that this problem is caused by CageFS, not by WordPress Toolkit, so there's not much we can do at the moment. Here's...

Hi @TomBoB, To further ensure a great quality of the overall Plesk extension experience, we had to make the Cloudflare ServerShield extension unavailable for all new Plesk installations on Friday last week (28th of February). If you do not have the CloudFlare extension installed on a server...

Hi @TomBoB, Our screenshot service now also renders screenshots for Dynamic View in Plesk Obsidian, so it's been experiencing significant load spikes. I'll talk to our DevOps team to see what we can do.

Hi Dave, We didn't add filtering right away because there are several possible ways to improve labels, and we wanted to hear what our users will ask us about the most to prioritize the improvements. Filtering looks to be one of the most obvious (and cheapest) ones, so we're going to improve...

Plesk has a Site Migrator feature that should help you out. Check this doc for more info: Importing Websites