WordPress.org

Forums

"Warning: array_merge()" when editing/updating comments (6 posts)

  1. Hausfraulein
    Member
    Posted 6 years ago #

    I upgraded to 2.8 recently and now cannot edit comments. I'm getting this error -

    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /wp-includes/comment.php on line 1097 Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/comment.php:1097) in /wp-includes/classes.php on line 1586

    Thanks.
    Penelope

  2. dawblog
    Member
    Posted 6 years ago #

    hi penny,

    i've your same problem! :-( Do you know the solution?
    thank you!

  3. misthero
    Member
    Posted 6 years ago #

    similar problem here

    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/konafans/public_html/wp-includes/comment.php on line 1097

    Warning: Cannot modify header information - headers already sent by (output started at /home/konafans/public_html/wp-includes/comment.php:1097) in /home/konafans/public_html/wp-includes/pluggable.php on line 865

    cannot edit any comment

  4. misthero
    Member
    Posted 6 years ago #

    update: same issue on another blog of mine:

    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/lukartne/public_html/wp-includes/comment.php on line 1097

    Warning: Cannot modify header information - headers already sent by (output started at /home/lukartne/public_html/wp-includes/comment.php:1097) in /home/lukartne/public_html/wp-includes/pluggable.php on line 865

  5. misthero
    Member
    Posted 6 years ago #

    ok solved, it was DB-cache plugin issue not being compatible with wordpress 2.8

    disabling DB-cache fixed the problem, the funny thing was I recently installed the plugin to make the site faster and to solve some other issue with my host...

  6. The J
    Member
    Posted 5 years ago #

    This isnt solved at all.
    Disabling a plugin is just a temporary solution.. the real solution would be if the plugin got actually fixed by the author or someone who knows why the plugin is probably caching the backend as well.
    I opened a new thread with the issue and contacted the author about it.

    http://wordpress.org/support/topic/382004?replies=1#post-1457781

Topic Closed

This topic has been closed to new replies.

About this Topic