122 results found

1. Support Wordpress multi-site network in WP toolkit

   It's a useful for me, to manage all my sites in one wp instance, using 3rd level domains, like mydomain.com, forum.mydomain.com, shop.mydomain.com, catalog.mydomain.com, etc.

   31 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Hi Jeremy,

   WP Toolkit supports WordPress multi-site if you enable the multi-site feature manually. However, it seems to make sense for us to provide an option of creating a multi-site WP instance upon the installation. Let us know if this will help you out.

   —AK

2. Improvements for Wordpress Toolkit

   Disable the built-in code editor adding define('DISALLOWCODEEDIT', true); in wp-config.php

   Anonymize login error message because it actually tells you what is wrong (the username or the password), hooking into loginerrors with addfilter('login_errors, function() { return 'Login error'; });

   Apply permission 400 (-rw-------) to wp-config.php

   Change login URL avoiding the standard /wp-login.php or /wp-admin/ (pre)installing plugin "Lockdown WP Admin" or applying the same idea.

   Block brute force (pre)installing plugin "Limit Login Attempts" or applying the same idea.

   Mentioned plugins may be installed by default when Wordpress is installed through the APS, and may be added as an optional security measure by the Wordpress Toolkit.

   Disable the built-in code editor adding define('DISALLOWCODEEDIT', true); in wp-config.php

   Anonymize login error message because it actually tells you what is wrong (the username or the password), hooking into loginerrors with addfilter('login_errors, function() { return 'Login error'; });

   Apply permission 400 (-rw-------) to wp-config.php

   Change login URL avoiding the standard /wp-login.php or /wp-admin/ (pre)installing plugin "Lockdown WP Admin" or applying the same idea.

   Block brute force (pre)installing plugin "Limit Login Attempts" or applying the same idea.

   Mentioned plugins may be installed by default when Wordpress is installed through the APS, and may be added as an… more

   49 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   8 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   These suggestions look quite reasonable. We encourage other WPT users to join and let us know what other security improvements you’d like us to implement in WPT.

   —AK