Support » Plugin: SSL Insecure Content Fixer » SSL Insecure Content Fixer PHP 7.2 Compatibility test

  • Resolved Airat Halitov

    (@airathalitov)



    FILE: /test.site/wp-content/plugins/ssl-insecure-content-fixer/views/script-force-https.php
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
     1 | WARNING | No PHP code was found in this file and short open tags are not allowed by this install of PHP. This file may be using short open tags but PHP does not allow them.
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    file: https://plugins.trac.wordpress.org/browser/ssl-insecure-content-fixer/trunk/views/script-force-https.php

    SSL Insecure Content Fixer 2.7.0
    PHP Compatibility Checker 1.4.6

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author webaware

    (@webaware)

    G’day Airat,

    This plugin is compatible with PHP versions 5.3-7.2 (at least). I’m slowly going through my plugins and adding PHPCS sniffs to them, so I’ll catch up with this warning and fix it in due course, but you can be confident that the plugin is compatible.

    With this specific file, it’s just complaining that it’s a PHP file with no PHP in it (only an HTML element containing JavaScript).

    cheers,
    Ross

    Thanks for quick answer.
    Yes, your plugin is working good on PHP7.2.
    My ticket is a small recommendation for you.

    Plugin Author webaware

    (@webaware)

    Ah, no worries. Thanks for the recommendation!

    cheers,
    Ross

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.