Just upgraded to v 1.2 – errors

  • S1L1K0N

    (@s1l1k0n)


    7 years, 7 months ago

    Good evening, I just upgraded bbPress Pencil Unread to v1.2 on a WordPress 4.6.1 installation and I get the following errors when I go to my forums:

    Warning: DOMDocument::loadHTML(): Empty string supplied as input in ../wp-content/plugins/bbpress-pencil-unread/bbpress-pencil-unread.php on line 852

    I also receive the following error at the top of home page, even when the plug-in is deactivated:

    Warning: Missing argument 2 for wpdb::prepare(), called in ../wp-content/plugins/bbpress-pencil-unread/bbpress-pencil-unread.php on line 154 and defined in /home/mmfawebmin/public_html/wp-includes/wp-db.php on line 1285

    Any assistance you can provide is greatly appreciated, thx.

Viewing 5 replies - 1 through 5 (of 5 total)
  • gordielachance

    (@gordielachance)

    7 years, 7 months ago

    Hi and thanks for your feedback.
    I think I fixed your two bugs here, update to 1.2.1 and tell me if it works !

    Thread Starter S1L1K0N

    (@s1l1k0n)

    7 years, 7 months ago

    Installed v1.2.2 this afternoon, no more errors, thanks for your help and the plug-in.

    radioinsight

    (@radioinsight)

    7 years, 7 months ago

    On version 1.2.2 and getting similar errors.

    Warning: DOMDocument::loadHTML(): htmlParseEntityRef: no name in Entity, line: 1 in /home/insight/public_html/wp-content/plugins/bbpress-pencil-unread/bbpress-pencil-unread.php on line 866

    Warning: DOMDocument::loadHTML(): htmlParseEntityRef: no name in Entity, line: 2 in /home/insight/public_html/wp-content/plugins/bbpress-pencil-unread/bbpress-pencil-unread.php on line 866

    Warning: DOMDocument::loadHTML(): htmlParseEntityRef: no name in Entity, line: 6 in /home/insight/public_html/wp-content/plugins/bbpress-pencil-unread/bbpress-pencil-unread.php on line 866

    https://radioinsight.com/community/

    gordielachance

    (@gordielachance)

    7 years, 7 months ago

    Fixed in 1.2.3 !

    radioinsight

    (@radioinsight)

    7 years, 7 months ago

    Indeed it has. Thank you for quick fix.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Just upgraded to v 1.2 – errors’ is closed to new replies.