WP Comment Autoresponder error_log

Salah satu plugin yang saya pakai di blog ini adalah WP Comment Autoresponder. Tapi belakangan plugin tersebut bermasalah di perintah query-nya sehingga menciptakan error_log yang besar banget. Awalnya saya tidak tahu kalau masalahnya gara-gara plugin tersebut. Tapi tiap saya cek file manager kenapa error_log-nya besar banget sampai puluhan Mb.

Kemudian beberapa hari lalu saya coba search di google pesan error di error_log tersebut. Ternyata asalnya dari plugin wp comment autoresponder buatan Ahlul Faradish Resha. Sayangnya ketika saya chat dengan beliau, saat ini beliau belum fokus mengembangkan plugin tersebut. Sehingga error-nya akan tetap ada hehehe..

Maka pilihannya sekarang cuma 2 mau tetep pakai tapi harus sering-sering cek error_log dan menghapusnya kalau sudah gede (kalau komentar yang masuk dikit, ini opsi yang bisa dipilih).

Atau anda non aktifkan aja dulu pluginnya dan baru diaktifkan setelah ada notifikasi dari wordpress.org atau saya ada waktu untuk melihat kesalahannya dimana dan mempublishnya disini. Yang saya khawatirkan kalau ada yang memanfaatkan masalah ini sebagai celah untuk melakukan penyusupan walaupun belum bisa saya pastikan sih.

UPDATE:
Alhamdulillah.. saya menemukan solusi mengatasi gemuknya error_log gara-gara plugin wp comment autoresponder ini. Caranya simple ternyata. Buka file wp-comment-auto-responder.php lalu cari kode ini:

  $table_postmeta = $wpdb->prefix . "postmeta";
  $postmeta_row = $wpdb->get_row("SELECT `meta_value` FROM `$table_postmeta` WHERE `post_id` = ".$comment_post_ID." AND `meta_key` = 'wp_car_tag' LIMIT 1");
  $post_tag = $postmeta_row->meta_value;

Sekarang ganti kode tersebut dengan kode ini:

  if ($comment_post_ID) {
  $table_postmeta = $wpdb->prefix . "postmeta";
  $postmeta_row = $wpdb->get_row("SELECT `meta_value` FROM `$table_postmeta` WHERE `post_id` = ".$comment_post_ID." AND `meta_key` = 'wp_car_tag' LIMIT 1");
  $post_tag = $postmeta_row->meta_value;
  }

Insya Allah sekarang tidak akan ada error lagi karena jika $comment_post_ID kosong, maka script tidak akan melakukan pencarian meta πŸ™‚ Mudah-mudahan bisa jadi solusi πŸ™‚

Dicari dengan kata kunci:

lutvi avandi,plugin wordpress buatan indonesia,arti parse error: syntax error unexpected t_variable in,unexpected t_variable,parse error: syntax error unexpected t_variable,arti syntax error unexpected t_variable,mengatasi unexpected t_variable,cara mengatasi syntax error unexpected T_VARIABLE,mengatasi masalah php parse error,mengatasi masalah pada php parse error: syntax error unexpected \<\

39 thoughts on “WP Comment Autoresponder error_log

  1. Taufan Prakoso

    Malah keluar erorr ini saat web di buka, mas.

    Parse error: syntax error, unexpected T_VARIABLE in /home/xxxx/public_html/topan.web.id/wp-content/plugins/wp-comment-auto-responder/wp-comment-auto-responder.php on line 328

    1. adhani

      sama mengalami juga, tapi saya error setelah me save perubahan yang saya lakukan

      keluar pesan
      Parse error: syntax error, unexpected T_VARIABLE in /xxxx/xxxx/adhani.com/wp-content/plugins/wp-comment-auto-responder/wp-comment-auto-responder.php on line 326

      1. Lutvi Avandi Post author

        Bentar, editnya di dashboard atau file manager? Kalau di dashboard, apakah anda lihat kode ini di bagian paling bawah?

        //if you edit this plugin, please dont remove my credit, OK!

        Saya khawatirnya scriptnya belum terload semua ketika mau edit sehingga pas disimpan maka dianggap menghapus baris-baris yang bawah mengingat file ini cukup besar

        1. adhani

          terima kasih mas lutvi, setelah saya menghapus dari daftar plugin terus menginstal ulang dan melakukan perbaikan di cpanel, Alhamdulillah sudah berjalan dengan baik.. tanpa error hhehehe

      1. Taufan Prakoso

        Sesuai artikel di atas, Saya replace ini :

        $table_postmeta = $wpdb->prefix . “postmeta”;
        $postmeta_row = $wpdb->get_row(“SELECT `meta_value` FROM `$table_postmeta` WHERE
        `post_id` = “.$comment_post_ID.” AND `meta_key` = ‘wp_car_tag’ LIMIT 1″);
        $post_tag = $postmeta_row->meta_value;

        Dengan code ini :

        if ($comment_post_ID) {
        $table_postmeta = $wpdb->prefix . “postmeta”;
        $postmeta_row = $wpdb->get_row(“SELECT `meta_value` FROM `$table_postmeta` WHERE `post_id` = “.$comment_
        $post_tag = $postmeta_row->meta_value;
        }

        Ada yg salah ?

        1. Lutvi Avandi Post author

          Periksa bagian bawah filenya. Apakah kode ini masih ada.

          //if you edit this plugin, please dont remove my credit, OK!

          Kuatirnya sama kasusnya dengan adhani karena load terputus ketika edit pluginnya. Coba baca komentar saya atas kasusnya adhani

  2. Anggi Alfonso

    mas mau nanya .. kok plugin ini saya pakai di web saya tapi emailnya ga masuk,

    maksudnya gini.. jika sebagai admin aja email baru masuk
    tapi jika menggunakan selain email admin sitenya email tidak masuk.. ada solusi?

  3. panji

    mas lutvi mo nanya kenapa plugin yg saya download di fle wp-comment-auto-responder.php di buka secara ofline juga cuma sampe tulisan //if you edit this plugin, please dont remove my credit, OK! gak ada lanjutannnya lagi mohon pencerahhannya

  4. Ricky Caselden

    Outsourced ASP model autoresponders operate on the provider’s infrastructure and are usually configurable via a web-based control panel. The customer pays a monthly usage fee. This is easiest to implement for the end-user.*:’.

    Look out for our own blog page too
    <http://homelifestyledigest.com/

  5. go to this web-site

    I simply want to mention I’m new to weblog and seriously enjoyed your web page. More than likely I’m going to bookmark your blog post . You surely have incredible writings. Thanks a lot for sharing with us your webpage.

  6. Lupe Ferrari

    This is very interesting, You are a very skilled blogger. I have joined your feed and look forward to seeking more of your fantastic post. Also, I have shared your site in my social networks!

  7. Ethelene Luellen

    A lot of the things you assert is surprisingly legitimate and that makes me wonder the reason why I hadn’t looked at this in this happy facing. This piece in truth did switch the effortless resting on on behalf of me as further as this particular topic goes. Nevertheless by this calculate here is actually 1 status I am not exceedingly comfortable with and although I try to reconcile that with the focal indication of your arrange, okay me observe immediately what all the rest of your visitors have to say.Well done.

  8. Olen Ortelt

    Everything is very open with a clear clarification of the challenges. It was really informative. Your website is extremely helpful. Many thanks for sharing!

  9. Matthew C. Kriner

    Zune and iPod: Most people compare the Zune to the Touch, but after seeing how slim and surprisingly small and light it is, I consider it to be a rather unique hybrid that combines qualities of both the Touch and the Nano. It’s very colorful and lovely OLED screen is slightly smaller than the touch screen, but the player itself feels quite a bit smaller and lighter. It weighs about 2/3 as much, and is noticeably smaller in width and height, while being just a hair thicker.

  10. Arthur Vecchi

    Hi there, You’ve done an incredible job. I’ll certainly digg it and personally suggest to my friends. I’m confident they’ll be benefited from this web site.

  11. Vera Steenken

    That is a very good tip particularly to those new to the blogosphere. Simple but very accurate info… Thanks for sharing this one. A must read article!

  12. Shaquana Leckband

    I just like the helpful info you supply on your articles. I will bookmark your blog and test once more here regularly. I am slightly sure I will be told a lot of new stuff proper here! Good luck for the next!

  13. Maria Aguallo

    Pretty section of content. I just stumbled upon your web site and in accession capital to assert that I acquire actually enjoyed account your blog posts. Any way I will be subscribing to your feeds and even I achievement you access consistently quickly.

Comments are closed.