New to Translating WordPress? Read through our Translator Handbook to get started. Hide
Prio | Original string | Translation | — |
---|---|---|---|
↓ | Enhancement: Hide Backend functions purely in PHP code now rather than relying half on PHP code and half on .htaccess and nginx.conf modifications. This allows Hide Backend to function on web servers and server configurations that it was previously not compatible with. | Enhancement: Hide Back End functions purely in PHP code now rather than relying half on PHP code and half on .htaccess and nginx.conf modifications. This allows Hide Back End to function on web servers and server configurations that it was previously not compatible with. | Details |
Original current
Enhancement: Hide Backend functions purely in PHP code now rather than relying half on PHP code and half on .htaccess and nginx.conf modifications. This allows Hide Backend to function on web servers and server configurations that it was previously not compatible with.
You have to log in to edit this translation. Meta |
|||
↓ | Enhancement: Changed default Hide Backend Register Slug from wp-register.php to wp-signup.php since WordPress switched from using wp-register.php to wp-signup.php for registrations. This will not affect existing sites. | Enhancement: Changed default Hide Back End Register Slug from wp-register.php to wp-signup.php since WordPress switched from using wp-register.php to wp-signup.php for registrations. This will not affect existing sites. | Details |
Original current
Enhancement: Changed default Hide Backend Register Slug from wp-register.php to wp-signup.php since WordPress switched from using wp-register.php to wp-signup.php for registrations. This will not affect existing sites.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Enhancement: The Hide Backend hidden login URL is no longer leaked by password-protected content. | Enhancement: The Hide Back End hidden login URL is no longer leaked by password-protected content. | Details |
Original current
Enhancement: The Hide Backend hidden login URL is no longer leaked by password-protected content.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Enhancement: Improved efficiency of Hide Backend code, increasing site performance when the feature is enabled. | Enhancement: Improved efficiency of Hide Back End code, increasing site performance when the feature is enabled. | Details |
Original current
Enhancement: Improved efficiency of Hide Backend code, increasing site performance when the feature is enabled.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Fixed password-protected posts not properly handling the password when Hide Backend is enabled. | Bug Fix: Fixed password-protected posts not properly handling the password when Hide Back End is enabled. | Details |
Original current
Bug Fix: Fixed password-protected posts not properly handling the password when Hide Backend is enabled.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Hide Backend now hides registration pages on multisite sites. | Bug Fix: Hide Back End now hides registration pages on multisite sites. | Details |
Original current
Bug Fix: Hide Backend now hides registration pages on multisite sites.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Hide Backend is now compatible with Jetpack Single Sign On. | Bug Fix: Hide Back End is now compatible with Jetpack Single Sign On. | Details |
Original current
Bug Fix: Hide Backend is now compatible with Jetpack Single Sign On.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Fixed issue that could prevent "Register" and "Lost your password?" links from working properly on the login page when Hide Backend is enabled. | Bug Fix: Fixed issue that could prevent "Register" and "Lost your password?" links from working properly on the login page when Hide Back End is enabled. | Details |
Original current
Bug Fix: Fixed issue that could prevent "Register" and "Lost your password?" links from working properly on the login page when Hide Backend is enabled.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Fixed issue where access to wp-admin/admin-post.php when Hide Backend is enabled. | Bug Fix: Fixed issue where access to wp-admin/admin-post.php when Hide Back End is enabled. | Details |
Original current
Bug Fix: Fixed issue where access to wp-admin/admin-post.php when Hide Backend is enabled.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Fixed compatibility issue with the Jetpack plugin when Hide Backend is enabled which could prevent Jetpack from redirecting users to the wordpress.com login page. | Bug Fix: Fixed compatibility issue with the Jetpack plugin when Hide Back End is enabled which could prevent Jetpack from redirecting users to the wordpress.com login page. | Details |
Original current
Bug Fix: Fixed compatibility issue with the Jetpack plugin when Hide Backend is enabled which could prevent Jetpack from redirecting users to the wordpress.com login page.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Fixed an infinite loop that could occur when expiring a cookie and Hide Backend is enabled. | Bug Fix: Fixed an infinite loop that could occur when expiring a cookie and Hide Back End is enabled. | Details |
Original current
Bug Fix: Fixed an infinite loop that could occur when expiring a cookie and Hide Backend is enabled.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Important: The way that Hide Backend functions changes in this release. Previously, if your Hide Backend Login Slug was wplogin, going to example.com/wplogin would result in the URL remaining example.com/wplogin. The new implementation of this feature results in a redirect to a URL that looks as follows: example.com/wp-login.php?itsec-hb-token=wplogin. While this may not be desireable for some users, this change was necessary to fix longstanding compatibility issues with other plugins. Once you access the login page using the Login Slug page, a cookie is set with an expiration time of one hour. As long as the cookie remains, you can access example.com/wp-login.php without having to access the Hide Backend Login Slug first. If you wish to confirm that Hide Backend is working properly on your site, opening up a private browsing window is a quick way to test without having to log out and clear cookies. | Important: The way that Hide Back End functions changes in this release. Previously, if your Hide Back End Login Slug was wplogin, going to example.com/wplogin would result in the URL remaining example.com/wplogin. The new implementation of this feature results in a redirect to a URL that looks as follows: example.com/wp-login.php?itsec-hb-token=wplogin. While this may not be desirable for some users, this change was necessary to fix longstanding compatibility issues with other plugins. Once you access the login page using the Login Slug page, a cookie is set with an expiration time of one hour. As long as the cookie remains, you can access example.com/wp-login.php without having to access the Hide Back End Login Slug first. If you wish to confirm that Hide Back End is working properly on your site, opening up a private browsing window is a quick way to test without having to log out and clear cookies. | Details |
Original current
Important: The way that Hide Backend functions changes in this release. Previously, if your Hide Backend Login Slug was wplogin, going to example.com/wplogin would result in the URL remaining example.com/wplogin. The new implementation of this feature results in a redirect to a URL that looks as follows: example.com/wp-login.php?itsec-hb-token=wplogin. While this may not be desireable for some users, this change was necessary to fix longstanding compatibility issues with other plugins. Once you access the login page using the Login Slug page, a cookie is set with an expiration time of one hour. As long as the cookie remains, you can access example.com/wp-login.php without having to access the Hide Backend Login Slug first. If you wish to confirm that Hide Backend is working properly on your site, opening up a private browsing window is a quick way to test without having to log out and clear cookies.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Enhancement: Introduce password requirements module to centralize handling of password updates. | Enhancement: Introduce password requirements module to centralise handling of password updates. | Details |
Original current
Enhancement: Introduce password requirements module to centralize handling of password updates.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Fix strong passwords not being recognized as strong on the profile page. | Bug Fix: Fix strong passwords not being recognised as strong on the profile page. | Details |
Original current
Bug Fix: Fix strong passwords not being recognized as strong on the profile page.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
|||
↓ | Bug Fix: Enabling or disabling the Hide Backend feature now properly updates the .htaccess/nginx.conf file on enable and disable rather than at some future point. | Bug Fix: Enabling or disabling the Hide Back End feature now properly updates the .htaccess/nginx.conf file on enable and disable rather than at some future point. | Details |
Original current
Bug Fix: Enabling or disabling the Hide Backend feature now properly updates the .htaccess/nginx.conf file on enable and disable rather than at some future point.
CommentFound in changelog list item. You have to log in to edit this translation. Meta |
Export as
Comment
Found in changelog list item.