Bug with php 5.5 not resolved – even worse now :-(

  • Resolved Raphael9973

    (@raphael9973)


    9 years, 6 months ago

    Hi Kris,

    referring to the thread “[resolved] FQ seems not to work with php 5.5 and higher?”… you have published a new FQ version yesterday, but it is not working. Worse than before, there are error messages with *all* PHP-Versions now (5.4xxx and older, as well as in 5.5xxx, and also in 5.6.0)

    How can I switch back to the older FQ-Version before 2.3.2, so I can at least work with PHP 5.4?

    The error messages are now as follows:

    Warning: mysqli_query() expects parameter 1 to be mysqli, object given in /[my-web]/wp-content/plugins/free-quotation/incloudes/Free_Quotation_widget.php on line 58

    Warning: mysqli_fetch_array() expects parameter 1 to be mysqli_result, null given in /[my-web]/wp-content/plugins/free-quotation/incloudes/Free_Quotation_widget.php on line 63

    https://wordpress.org/plugins/free-quotation/

    Amendment: Have reinstalled FQ 2.3.1 from a backup 🙂 and switched back to PHP 5.4 … but of course I would like to use a newer PHP Version asap! Thanks for your work!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author kris_IV

    (@kris_iv)

    9 years, 6 months ago

    Oh sorry.

    It was too late and I make mistake during updating – part of plugin was from older version and the name of variables was not the same. Now I quickly correct this error. Check version 2.3.3.

    Check version 2.3.3.

    —-
    Edit: For future – if you want use older version of any WordPress plugin you can find it in ‘developers’ section. For example hire:
    https://wordpress.org/plugins/free-quotation/developers/
    You can find almost all old version of Free Quotation .

    Plugin Author kris_IV

    (@kris_iv)

    9 years, 6 months ago

    I resolved this problem in version 3.0.0 of Free Quotation. Now database connection is 100% compatible with WordPress Codex.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Bug with php 5.5 not resolved – even worse now :-(’ is closed to new replies.