• Resolved vnairp11

    (@vnairp11)


    warning: implode():invalid arguments passed in /home/web/public_html/domain.com/wp-content/plugins/fast-velocity-minify/fvm.php on line 1569

Viewing 12 replies - 1 through 12 (of 12 total)
  • Warning: implode(): Invalid arguments passed in E:\laragon2\www\nuevadiapo\wp-content\plugins\fast-velocity-minify\fvm.php on line 1352

    Getting the same warning: implode():invalid arguments passed in /var/www/domain.com/public_html/wp-content/plugins/fast-velocity-minify/fvm.php on line 1569 after the latest update

    Drake

    (@marcoragogna)

    Same problem, following

    Same problem

    Plugin Author Raul P.

    (@alignak)

    My fault, sorry. Fixed on 2.8.6 now.

    But you people, should really not be running production servers with debug mode on.
    https://wordpress.stackexchange.com/questions/332952/removing-warnings-and-notices-from-production-servers

    All good if those are testing environments though.

    Thanks, Raul, I will switch debug mode off. Thanks for notifying us.
    ASR Martins

    Drake

    (@marcoragogna)

    Thank you Raul, you are right, its Siteground default, I’ll switch it off

    Thread Starter vnairp11

    (@vnairp11)

    hi Raul,

    any reason why we shouldn’t run debug on, is there a performance hit etc?

    how do I turn debug off on siteground?

    Plugin Author Raul P.

    (@alignak)

    @vnairp11 mostly security reasons.
    https://www.acunetix.com/vulnerabilities/web/wordpress-debug-mode/

    The link I posted earlier explains what to do.
    https://wordpress.stackexchange.com/questions/332952/removing-warnings-and-notices-from-production-servers
    You need to edit the wp-config.php file.

    Thread Starter vnairp11

    (@vnairp11)

    Thank you, Raul! those are some great tips!

    Processing…Error: Unable to load current/d762mqwfs9c8ccwc8coo088g' on behalf of 'qi015o02ad9d'. Corrupt data file:/home/qi015o02ad9d/.appdata/current/d762mqwfs9c8ccwc8coo088g’ cannot be loaded.

    Plugin Author Raul P.

    (@alignak)

    @marlon1205 what’s that file and path and where are you seeing the error?

    If it’s on sever logs, sounds like your hard drive is failing, you ran out of space, or possibly have malware.

    current/d762mqwfs9c8ccwc8coo088g doesn’t look like a valid url as well.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘error after new update 4.29.2020’ is closed to new replies.