• Resolved zabbaka

    (@zabbaka)


    Just started to give me error “The pre-scan could not complete.” on one of free sites. Two others is ok. Plugins, wp-versions, even themes are the same

    • This topic was modified 8 years, 1 month ago by zabbaka.
Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Blobfolio

    (@blobfolio)

    Hi Zabbaka,

    I’m sorry to hear the plugin suddenly stopped working for you. With no recent updates to the plugin itself, the issue is going to be found somewhere else.

    Are you able to provide any additional information about your setup? Things like:

    • The web host
    • PHP version
    • Server type (Apache, Nginx, etc.)
    • WordPress version
    • Installed plugins and their versions

    If you have access to an error log, do you see any records corresponding to the scan attempt?

    Thread Starter zabbaka

    (@zabbaka)

    Wordpress 4.7.2
    PHP Version 5.4.16
    Apache/2.4.
    Plugins:
    BBQ latest
    All in one seo pack latest
    tinymce advanced latest
    Google XML Sitemap Generator latest

    Plugin Author Blobfolio

    (@blobfolio)

    Who are you using for web hosting? Almost all instances where this plugin does not work are host-specific (scanning files is a pretty hard job for PHP).

    Thread Starter zabbaka

    (@zabbaka)

    dobryjhosting.ru
    But they are ok about the php overload and even monstrous scripts.

    Plugin Author Blobfolio

    (@blobfolio)

    Would you please try temporarily adding the following to your wp-config.php file:

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );

    If your config file already has entries for either variable, you should just change the entry to match rather than adding new ones.

    Then try running a Look-See scan. If it fails, see if there is anything relevant in the debug log, which can be found at https://yourdomain.com/wp-content/debug.log

    If so, please paste the contents here. (You can censor path information before pasting.)

    After testing, you can undo the wp-config.php change and delete the debug file.

    Thank you for taking the time to help debug!

    Thread Starter zabbaka

    (@zabbaka)

    My bad not doing this earlier.
    The thing is, if any file has CHMOD 000 – pre-scan could not be comleted. If EVERY file is readable – everything is ok.

    • This reply was modified 8 years, 1 month ago by zabbaka.
    Plugin Author Blobfolio

    (@blobfolio)

    Ah, that makes sense. I’ll push an update in a bit that tries to work around PHP’s desire to explode when asked to look at a file it isn’t allowed to look at.

    Plugin Author Blobfolio

    (@blobfolio)

    I just pushed version 20.1.4 with some additional wrappers around file-related function calls. This should help prevent PHP from exploding when it encounters an inaccessible file. Would you please try re-running a scan with the new version (once you’re able to upgrade) and see if that fixes the issue?

    Thread Starter zabbaka

    (@zabbaka)

    Pre-scan completed, but can’t check all site files. Stops and show a-ok 18 or 28
    Debug gives this
    PHP Notice: Undefined variable: result in /var/www/zabbaka2/data/www/my.domain/wp-content/plugins/look-see-security-scanner/index.php on line 418

    • This reply was modified 8 years, 1 month ago by zabbaka.
    Plugin Author Blobfolio

    (@blobfolio)

    Thank you, @zabbaka, for trying again! I see the problem and have fixed it in 20.1.5. Would you please try one more time once you have been able to update the plugin?

    Thread Starter zabbaka

    (@zabbaka)

    Scans perfectly. Appreciate all the hard work.
    You are responsible developer

    • This reply was modified 8 years, 1 month ago by zabbaka.
    Plugin Author Blobfolio

    (@blobfolio)

    Awesome! Thank you so much for taking the time to help debug (most people don’t).

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘The pre-scan could not complete.’ is closed to new replies.