WassUp Forums

• Forums
• WassUp

1. 

   kanhaji
   Member

   I have been using Wassup for more than six months and everything was working fine but yesterday I got this error while I was trying to monitor the visitor activity on my website. I am getting this error in all the options of visitor tracking ie visitors, search engine bots, spam or everything. As far as I remember I have not done anything in my configuration in the word press or the hosting control panel. The complete text of the error message is given below:

   Invalid argument supplied for foreach() in public_html/thinkahead.net.in/forum/wp-content/plugins/wassup/wassup.php on line 1354

   Some other details that may help you in interpreting the problem:

   WassUp Version: 1.7.2.1

   WassUp Table name: wp_wassup
   WassUp Table Charset/collation: utf8_general_ci

   WordPress Version: 2.8.4

   WordPress Host Server: Apache
   WordPress Time Offset: UTC +5 hours (6:25 am)
   WordPress Character set: UTF-8
   WordPress Language: en-US

   PHP Version: 5.2.11

   PHP Safe Mode: off
   PHP File Open Restrictions (open_basedir): off
   PHP Memory Allocation: 64M
   PHP Memory Usage: 24.17M
   PHP Script Timeout Limit: 120 seconds
   PHP Browser Capabilities File (browscap): not set
   PHP Curl: installed

   MySQL Version: 5.0.81-community

   MySQL Engine: MyISAM
   MySQL Query Cache: 64M
   MySQL Delayed Insert Queue: 1000 rows
   MySQL Index (Key) Buffer: 64M
   MySQL Read Buffer: 2M
   MySQL Wait Timeout: 50 seconds
   MySQL Timezone: GMT-5 (UTC 5)
   MySQL Charset/collation: utf8_general_ci

   Posted 2 years ago #
2. 

   helene
   Moderator

   Thanks for providing the error message and your server settings. It was very helpful.

   The problem is related to one of Wassup's MySQL main queries which is getting no results back. The query cache(buffer) may be the cause, triggered by a change in your ISP's MySQL server setup, traffic overload/table growth, or table corruption.

   If you are familiar with using the Wordpress plugin editor, try removing the word "SQL_BUFFER_RESULT" from line #1149 in the file "main.php" to see if that fixes the problem.

   -Helene D.
   http://techfromhel.webege.com

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.