Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter htz77

    (@tzeldin88)

    Though i was unable to login to my wp-admin (because deactivating this crazy plugin broke my wp), i was able to re-activate the plugin using phpMyAdmin, and manually editing the active_plugins value (in the options table).

    This allowed me to login to wp again. Whew.

    But now, even with the plugin ACTIVE, my wp (and site) shows
    Warning: Invalid argument supplied for foreach() in /home2/mysite/public_html/mywp/wp-includes/post.php on line 1468

    That’s clearly a wp-core file. Not a conflict from some other plugin.

    Hey @smackcoders – i need some help here, please.

    Thread Starter htz77

    (@tzeldin88)

    I tried de-activating and re-activating a couple times, from inside wp.
    When i re-activate, i get a white-screen with:

    Warning: Invalid argument supplied for foreach() in /home2/mysite/public_html/mywp/wp-includes/post.php on line 1468
    
    Warning: Cannot modify header information - headers already sent by (output started at /home2/mysite/public_html/mywp/wp-includes/post.php:1468) in /home2/mysite/public_html/mywp/wp-includes/pluggable.php on line 1207
    
    Warning: Cannot modify header information - headers already sent by (output started at /home2/mysite/public_html/mywp/wp-includes/post.php:1468) in /home2/mysite/public_html/mywp/wp-includes/pluggable.php on line 1207

    Then if i reload the url in the browser, i return to wp-admin, with no php errors.
    Good, but now the plugin is active, and i do NOT want that.

    I can’t de-activate your plugin, without breaking my site.
    What in the world???

    We will fix your issue. Kindly create the support ticket by using the below link.

    https://www.smackcoders.com/support.html

    we will guide you there.

    Thread Starter htz77

    (@tzeldin88)

    (As posted in related thread..)

    The problem is fixed.

    Eventually I found a problem in my theme’s register_post_type() code, where the taxonomies value was a string not an array.

    But for some reason, when this plugin is active, the php-errors from that problem were HIDDEN, so I had never seen them before.

    I assume the plugin DISABLES my php Error Reporting. VERY BAD IDEA! Those errors display for a reason!!

    That said, the plugin otherwise works well, and did NOT actually DESTROY my site.

    Thanks for update.Kindly provide your support to our plugin always.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘This plugin DESTROYED my site’ is closed to new replies.