v2 update really not updated?

[tcreek]

I downloaded v2.0 and expanded archive into directory faveo-probe-2.0

As you can see in the image it is showing version 1.0, and reporting

Error! Minimum PHP version required in order to run Faveo is PHP 5.5.*

I have PHP 7.2 installed.

php --version

PHP 7.2.19-1+0~20190531112637.22+stretch~1.gbp75765b (cli) (built: May 31 2019 11:26:38) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.19-1+0~20190531112637.22+stretch~1.gbp75765b, Copyright (c) 1999-2018, by Zend Technologies

[mverma16]

@tcreek the screenshot you shared shows "Probe version:1.0", I am not sure you the zip archive you extracted actually contains v2.0. Can you share the downloaded file and the extracted folder's content with me at manish.verma@ladybirdweb.com

[tcreek]

Responded, but your mail system is not allowing . I have added it here

manish.verma@ladybirdweb.com: host alt2.aspmx.l.google.com[64.233.176.26] said: 552-5.7.0 This message was blocked because its content presents a potential 552-5.7.0 security issue. Please visit 552-5.7.0 https://support.google.com/mail/?p=BlockedMessage to review our 552 5.7.0 message content and attachment content guidelines. g83si221027ywc.216 - gsmtp (in reply to end of DATA command)

faveo-probe-2.0.tar.gz

[mverma16]

Tried in my system extracting the file you shared it shows the correct information. Can you share the content step1.php file which you are running on the server? Also please share the server environment as in the error you got it should show PHP version running on the server.

[tcreek]

I see the problem now. The actual index.php file is the culprit that has not been fully updated as we can see starting on line 37

     <strong>Probe Version:</strong> 1.0
                <br><strong>Testing For:</strong> Faveo HELPDESK 1.0.6 and Newer</p>
                 <div class="woocommerce-message woocommerce-tracker "><p><span id="fail">Error!</span> Minimum PHP version required in$

I had been accessing index.php directly in the browser on a system which was slightly misconfigured, causing the issue.

I started fresh again, and all is good now.

Thanks for the responses

[mverma16]

@tcreek thanks for reporting, we will update index.php for the same.