Todd - WireFlare

djsteveb,

I just wanted to let you know that I’m in the final stages of implementing this feature. The plugin should be released within 1 week.

Gotcha,

I think that it is something we could wrap up into the plugin as an extra, but it wouldn’t be something that would be defined as its core purpose. We would also have to store the log in data in the DB and export to CSV.

What information would you like to see in a report?

I should be able to work something out in the next week or two.

So if I’m understanding correctly, you would like to see the log be generated locally and not to the syslog facility?

The problem I see with that is that it wouldn’t suite the purpose of the plugin. It’s a good idea for another plugin possibly. But people might get confused as to what the plugin does if it doesn’t integrate with Fail2Ban.

What do you think?

Ptums,

That is completely expected for some themes.

Ask your theme author to resolve this. It’s not a blanket fix for everyone.

Todd

You’re lucky, I’m on vacation in a hotel and being yelled at because I’m working. Have a great night!

All we are doing is commenting out something that’s already part of the core WP files. You can easily revert should you choose.

It’s just referencing the closing bracket. Make the replacement that I suggested and your website should work again.

Replace:

function get_avatar_url($get_avatar){
preg_match("/src='(.*?)'/i", $get_avatar, $matches);
return $matches[1];
}

With

/*
function get_avatar_url($get_avatar){
preg_match("/src='(.*?)'/i", $get_avatar, $matches);
return $matches[1];
}
*/

I understand that you don’t want to mess things up and I don’t want you to either. Why don’t you paste the few lines above and below line 34 in your functions.php file here so I can see it.

Ok then follow the steps I outlined and your site will be up and running again. It should show the exact file and line number that you need to modify. You want to make sure you comment out the entire statement so it should be about 9 lines of code that you comment out.

The block will start with “function” and end with “}”

It should look similar to this with it commented out:

/*
function get_avatar_url($get_avatar){
    if(preg_match("/src='(.*?)'/i", $get_avatar, $matches)) {
    	preg_match("/src='(.*?)'/i", $get_avatar, $matches);
   		return $matches[1];
    } else {
    	preg_match("/src=\"(.*?)\"/i", $get_avatar, $matches);
   		return $matches[1];
    }
}
*/

This is most likely being caused by the get_avatar_url.

Please take a look at your hosting error logs.

If you look at the error log it will tell you which line contains the error and which file. An easy way to fix this would be to edit that file. Comment out the section that is causing the error. The file should be in your theme directory

On the noted line (found in the error log) you should see a statement that is used for avatars. Comment out the entire thing by placing /* in front of the statement and */ immediately following it. This will exclude it from being processed. Your website should load just fine after making this change and the code will still be there, just excluded from processing.

This function was built into WordPress in 4.2, but was previously something that the theme author had to bake in. In 4.2 the exact same statement that you commented out is included in wp-includes/link-template.php.

Therefore, it is completely safe to remove it because it’s a duplicate code conflict. Commenting it out is just a safer way to explain to people. I hate telling people to remove code because they may remove the wrong thing.

This is causing 4.2 to not load for many people.

This is most likely being caused by the get_avatar_url.

Please take a look at your hosting error logs.

If you look at the error log it will tell you which line contains the error and which file. An easy way to fix this would be to edit that file. Comment out the section that is causing the error. The file should be in your theme directory

On the noted line (found in the error log) you should see a statement that is used for avatars. Comment out the entire thing by placing /* in front of the statement and */ immediately following it. This will exclude it from being processed. Your website should load just fine after making this change and the code will still be there, just excluded from processing.

This function was built into WordPress in 4.2, but was previously something that the theme author had to bake in. In 4.2 the exact same statement that you commented out is included in wp-includes/link-template.php.

Therefore, it is completely safe to remove it because it’s a duplicate code conflict. Commenting it out is just a safer way to explain to people. I hate telling people to remove code because they may remove the wrong thing.

This is causing 4.2 to not load for many people.

@djstangl – no problem.

I should have added that this function was built into WordPress in 4.2, but was previously something that the theme author had to bake in. In 4.2 the exact same statement that you commented out is included in wp-includes/link-template.php.

Therefore, it is completely safe to remove it because it’s a duplicate code conflict. Commenting it out is just a safer way to explain to people. I hate telling people to remove code because they may remove the wrong thing.

If you look at the error log it will tell you which line contains the error and which file. An easy way to put a temporary fix on this without removing the theme would be to edit that file. Comment out the section that is causing the error. In the case of the OP it would be editing the file:

/home/wstaging/subdomains/tax/public_html/wp-content/themes/zeyn/lib/custom_functions.php

On line 623 you should see a statement that is used for avatars. Comment out the entire thing by placing /* in front of the statement and */ immediately following it. This will exclude it from being processed. Your website should load just fine after making this change and the code will still be there, just excluded from processing.

Having issues with the redirect on login as well. Can’t get the referer to work properly or the custom link. Everything re-directs to the site home page, which I’m assuming is because the referer is sending the user to the dashboard. I’ve disabled the dashboard using roles and capabilities in function.php which kicks all non-authorized users to the home page.

The rule in functions.php wouldn’t get triggered if the referer or custom link worked properly.