-
Author
-
October 3, 2016 at 01:30 #137903bamaroParticipant
This is to reopen a ticket that was previously marked as resolved but is not. Login protection is enabled on all WPEngine sites now and as a result, all Kleo installs will receive a 502 errors when using the login popup modal. Effectively, this breaks Kleo on all new WPEngine sites and the only way to solve the problem is to contact WPEngine support and have them disable login protection.
Below is the fix that you can add to the theme. You can even add it as a script within your documentation’s WPEngine compatibility section.
—–
One of the ways that WP Engine determines what’s a valid login attempt — and what’s a script based brute force attack — is by requiring a query argument (of wpe-login) on all login attempts. The value must match the name of the install in order to be considered valid.
The install name is defined with PWP_NAME in wp-config.php on all WP Engine installs.
An example of a valid URL to submit your login query to is:
http://domain.com/wp-login.php?wpe-login=PWP_NAME
If you’d like to detect if you’re on a WP Engine install, it’s best if you check for the existence of the wpe_site function.
<?php
if( function_exists( ‘wpe_site’ ) ) {
// This site is hosted on WP Engine.
}
Hopefully this gives you what you need to make your login related code WP Engine compatible!
October 3, 2016 at 18:50 #137981RaduModeratorHi,
Thanks for your suggestion it’s very helpful for wpEngine customers and also for us.
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionOctober 28, 2016 at 01:15 #141792bamaroParticipantHas this fix been added to the next release of core theme? If so, what version of Kleo? I would like to update all my sites.
October 31, 2016 at 17:22 #142232RaduModeratorHi,
This hasn’t been fixed in this update but we will do this implementation in future updates.
I’ve already added this to improvement list.
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 11, 2016 at 13:07 #143882AbeKeymasterHi, it was scheduled for the release coming next week.
We will probably need to test it with you and see if it solves the problem.
Cheers
Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.November 11, 2016 at 13:28 #143883AbeKeymasterHI, please see the attached zip file. extract the archive and replace the file from kleo/page-parts
Let me know how it went.
Cheers
Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.Attachments:
You must be logged in to view attached files.November 11, 2016 at 17:00 #143910bamaroParticipantIt Works! As an FYI, after updating the file you will have to purge your WPEngine cache to see it work.
Well done.
November 11, 2016 at 17:44 #143924RaduModeratorGreat then
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution -
AuthorPosts
The forum ‘Bugs & Issues’ is closed to new topics and replies.