Error From Logs Page

Bug #002 since Pro 7.0 release.

It looks like that file moved elsewhere.

Try and edit line 73 in the file /ydazyryerg/public_html/wp-content/plugins/ithemes-security-pro/pro/user-logging/logs.php like:

// require_once( ITSEC_Core::get_plugin_dir() . '/pro/two-factor/class-itsec-two-factor-helper.php' );
require_once ITSEC_Core::get_core_dir() . 'modules/two-factor/class-itsec-two-factor-helper.php';

+++++ To prevent any confusion, I’m not iThemes +++++

WOW.. Worked like a charm Thank you so much.

I really wonder how come this happened!!. I did nothing and i have just installed the plugin 2 days ago

I noticed this only happenes when i enable the Two Factor and it logs the history in DB table.

@timothyblynjacobs

FYI

Just in case this has not already shown up on your radar ??

Yep! On the list for the next release.

Okidoki.

I noticed the ITSEC_Core::get_core_dir() function always returns the absolute path to the plugin core folder with a trailing slash (/).
In cases such as below:

ITSEC_Core::get_core_dir() . '/lib/schema.php';

it results in a path with 2 slashes (core//lib):

/path/to/root/http_home/wp-content/plugins/better-wp-security/core//lib/schema.php

There are also occurrences where the concatenated path does not include a leading slash. Basically I noticed there is some inconsistency here.

What would be the best/correct way to deal with this:

1. Remove the trailing / from the ITSEC_Core::get_core_dir() function. And then ensure all the concatenating strings include a leading slash.

2. Remove the leading slash from all the concatenating strings.

Hi @mohkh1,

Since your issue got fixed in the iTSec PR0 7.0.2 release, please mark this topic as “resolved”.

According to the iTSec PR0 7.0.2 Changelog:

Bug Fix: Fatal error on logs page when User Logging and Two-Factor are enabled and a user logs in using Two-Factor.