Timotheus44
Forum Replies Created
-
Update: I just did an update to Wordfence, meaning I again had to manually comment out this code again. Great time to test if the problem persists: it does. [Ugh!]
I am on HostGator, and it tells me my current version of PHP is now 5.4.29. Yet I have to comment out the part to run authActionNew to make AffiliateRoyale to work. Meaning, even though I have a PHP version greater than 5.4.0, authActionOld runs better for me.
Could the need to choose the PHP version be unnecessary? Could there be something wrong with authActionNew?
For whatever reason, Wordfence decided not to fix their code to correct this error, so Affiliate Royale had to step up and fix it for them. It is a manual fix, so every time you update Wordfence you have to go in and correct the code again. Makes me strongly consider dropping Wordfence…
Here is the change in the code:
*** Modify wordfence/lib/wordfenceClass.php: comment out the logic to force it to use the old version of the hook:
if(false /*version_compare(PHP_VERSION, ‘5.4.0’) >= 0*/){
add_action(‘wp_authenticate’,’wordfence::authActionNew’, 1, 2);
} else {
add_action(‘wp_authenticate’,’wordfence::authActionOld’, 1, 2);I’m getting the same error when I simply try to log-in to my wordpress site, since I had iThemes (back when it was Better WP Security) to change the URL I use to login with. Now I’m regretting going with iThemes…
I have same problem as coolforyou, but am creating separate ticket.