• Resolved rebornhairppp

    (@rebornhairppp)


    Hey guys,

    Sorry to keep bothering you.

    Not that this is a big issue. I can live without it, but just noticed now when I search for a domain name (e.g. amazon) using the whois lookup feature, I get this message: WHOIS lookup successfully completed. Please see the results below:

    There are no results. It’s just plan white vanilla. When I navigate to my php error log, I get the following messages (note I omitted the full public root file path to remain clandestine):

    [26-Jan-2018 22:51:23 UTC] PHP Warning: Illegal string offset ‘handler’ in whois.gtld.php on line 57

    [26-Jan-2018 22:51:23 UTC] PHP Warning: Illegal string offset ‘nodomain’ in whois.parser.php(370) : eval()’d code on line 1

    [26-Jan-2018 22:51:23 UTC] PHP Warning: Illegal string offset ‘registered’ in whois.parser.php on line 386

    [26-Jan-2018 22:51:23 UTC] PHP Fatal error: Uncaught Error: Cannot unset string offsets in whois.gtld.php:60

    Stack trace:
    #0 whois.client.php(469): gtld_handler->parse(Array, ‘www.amazon.com’)

    #1 whois.client.php(254): WhoisClient->Process(Array, true)

    #2 whois.main.php(259): WhoisClient->GetData(‘www.amazon.com’, true)

    #3 whois-menu.php(119): Whois->Lookup(‘www.amazon.com’)

    #4 plugins/all-in-one-wp-security-and-firewall/admin/wp-security-whois in /plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.gtld.php on line 60

    What seems to be the problem for the white screen of death? This function worked prior to 2018.

    Thanks again for all your help like always!

    Joe

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi Joe, thank you for reporting this issue with us. Just a couple of questions. What PHP version is your server running?

    And what changed in your site before this issue started appearing? This question is regarding the following comment.

    This function worked prior to 2018.

    Thank you.

    • This reply was modified 7 years, 1 month ago by mbrsolution.
    Thread Starter rebornhairppp

    (@rebornhairppp)

    Hey mbrsolution,

    I was originally running PHP 7.0 without any problems with the Whois feature. Looking more closely at my timeline of changes, I decided to upgrade to PHP 7.2 removing all PHP 7.0 files and folders on 12/17/2017. Since Ubuntu 16.04 doesn’t have a repository for PHP 7.2, I had to download the PPA repository ppa:ondrej/php from https://launchpad.net/~ondrej/+archive/ubuntu/php.

    When I look more sharply at the PHP error log, I noticed the first time I ran Whois after the PHP 7.2 upgrade with this white screen of death problem was on 1/5/2018. My timeline of changes shows an update for PHP 7.2 on 1/14/2018. I know I said “this function worked prior to 2018”, but I think taking all this into perspective, my calculation was off. My apologies.

    In reality, I have strong reason to believe the initial PHP 7.2 upgrade back on 12/17/2017 caused the hiccup. I don’t recall using the Whois Lookup in 2017 after the PHP upgrade until sometime in the beginning of 2018. My error log showing the first instance of this hiccup on 1/5/18 seems to correlate with my recollection.

    In summary, the cause of this hiccup is obviously not the PHP 7.2 update conducted on 1/14/2018, since there was already a problem with this feature on 1/5/18. Rather, it was most likely the PHP 7.2 upgrade on 12/17/2017.

    It’s strange that all other features work as expected on PHP 7.2 just not the Whois.

    Any help would be appreciated! Again, don’t sweat it if you can’t find a resolution. I think I can live without this function!

    Take care my friends and I hope the team is in good spirits!!!!!

    All my best,

    Joe

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi Joe, thank you for sharing more light into your issue.

    As I am aware PHP version 7.2 is relative new. So to my understanding some plugins, themes and tools out in the market might not work well with PHP 7.2. And I am sure that PHP 7.2 has many bugs at present because it is relative new. In my humble opinion I would not use PHP 7.2 in a live site for a while yet. I would allow some time for most of the bigger bugs to be fixed. Instead I would test locally in a testing site to see how it functions.

    I have submitted a message to the developers to investigate further this issue.

    Thank you

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Hi,
    The whois lookup feature uses a third party library which unfortunately has not been maintained as one would expect.
    Due to the very minor value it provides to this plugin (and the extra headaches), I will be eventually removing this feature.
    You can easily do a whois lookup online anyway.
    Thanks for the feedback.

    Thread Starter rebornhairppp

    (@rebornhairppp)

    Hi mbrsolution,

    Hmm I think you have a good point, though I am adamant of switching over to the older PHP version. Everything else works fine, so I might just keep it for the time being since I made substantial progress thus far.

    Again, Whois can always be utilized on the web.

    Thanks again for still trying to diagnose this issue.

    All my best,

    Joe

    Thread Starter rebornhairppp

    (@rebornhairppp)

    Hey wpsolutions,

    Just saw your new comment come through.

    YES! We are on the same work page!!

    Take care man and God bless you guys. I will mark this thread as resolved!

    All my best,

    Joe

    Hi,
    Yes, I also got some similar text lines when performed a WHOIS lookup:

    Warning: Illegal string offset ‘handler’ in /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.gtld.php on line 57

    Warning: Illegal string offset ‘regrinfo’ in /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.parser.php(370) : eval()’d code on line 1

    Fatal error: Uncaught Error: Cannot use string offset as an array in /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.parser.php(370) : eval()’d code:1 Stack trace: #0 /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.parser.php(370): eval() #1 /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.gtld.php(58): generic_parser_b(Array, Array, ‘dmy’) #2 /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.client.php(469): gtld_handler->parse(Array, ‘youtube.com’) #3 /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.client.php(254): WhoisClient->Process(Array, true) #4 /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.main.php(259): WhoisClient->GetData(‘youtube.com’, true) #5 /home3/waeg5s0abox6/public_html/wp-content in /home3/waeg5s0abox6/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.parser.php(370) : eval()’d code on line 1

    PHP version 7.1.13 running on my server.

    Best Regards.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi @fatbones, thank you for sharing your issue. However this feature will be removed in the future as stated above by @wpsolutions the developer. I kindly suggest not to use this feature anymore as it is no longer maintained.

    Kind regards

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Whois Lookup White Screen’ is closed to new replies.