WassUp 1.7 does not show any data

WassUp Forums » WassUp Bug report

WassUp 1.7 does not show any data

(15 posts) (6 voices)

Started 9 months ago by poutnik
Latest reply from helene

Tags:

poutnik
Member

Hello, first I've been very happy with WassUp for more than a year, but after update to version 1.7 it stopped working correctly (and even after update to 1.7.1 development):

It does not show any data for any visitors, although there are entries in the "wp_wassup_tmp" table. Also there is no graph, since there are no entries to graph. So effectively it does not log any visitors at all. (last entry was just before the update, and as the 24h limit I have for deleting old records was reached, there was no data at all).

Thanks for any hint why that may be...

Jiri

Posted 9 months ago #
helene
Moderator

Jiri,
We need more info to figure out what's going wrong. Can you show us your server configuration settings from Wassup=>Options=>Manage Files & Database? Also, please go to Wassup Main screen and select "view source" in your browser and let us know if you see any error messages near the bottom of the page. It would be useful to look at the source for your blog index page as well. If WassUp 1.7 is recording, you should see a Wassup timestamp hidden in your theme's footer.

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

Posted 9 months ago #
poutnik
Member

Hello Helene,

the settings is as follows:

WordPress Version: 2.7.1
WordPress Host Server: Apache/2.2.8 (Win32) PHP/5.2.5
WordPress Time Offset: UTC 1 hod.. (08:13)
PHP Version: 5.2.5
PHP Memory Allocation: 32M
PHP Memory Usage: 20.23M
PHP Script Timeout Limit: 120 seconds
PHP Browser Capabilities File (browscap): not set
PHP Curl: installed
MySQL Version: 5.0.51b-community-nt
MySQL Engine: InnoDB
MySQL Query Cache: 0 (disabled)
MySQL Index (Key) Buffer: 84M
MySQL Read Buffer: 0M
MySQL Wait Timeout: 28800 seconds

There are no errors in the source of the page to be seen, and the correct timestamp is correctly added to the bottom of the page.

Only instead of the graph, I see: "Too few records to print chart...", and where there should be the data, there is nothing. If I look at the tables in MySQL database, wp_wassup_tmp table is populated correctly (entries are added, they look reasonable, old entries are deleted), but wp_wassup table is empty since the reinstall. (I even deleted both wp_wassup and _wassup_tmp tables and installed the plugin from scratch, to no avail).

Thanks

Jiri

Posted 9 months ago #
poutnik
Member

I have nailed down the problem to be caused by DELAYED transactions (inserts) into the wp_wassup database. Maybe a glitch in the configuration of my provider's SQL server. I have solved the problem by editing the wassup.php file and in the function insert_into_wp changing the line $delayed = "DELAYED" to $delayed = "";

I'll look into the configuration of the SQL server.

Jiri

Posted 9 months ago #
c0d3r
Member

I'm having the same issue with 1.7.1
Even removing the DELAYED string from the statement in wassup.php did not solve the issue for me

I did, however, see a warning in my php log :
E_WARNING
Division by zero at /data/www/blog/wp-content/plugins/wassup/wassup.php (1154)

Any suggestions ?

Posted 9 months ago #
helene
Moderator

Poutnik,
You are AWESOME! We will fix the "insert delayed" problem asap.
***

C0d3r,
Thanks for reporting the division by 0 error. It means that WassUp detailed queries to MySQL is getting no data back. Probably because of a syntax compatibility issue with your MySQL engine and version. I visited your blog (nice!) and Wassup seems to be recording visitor data. To diagnose why you can't see that data, I need to see your server settings in Wassup=>Options=>Manage Files&Database to verify your MySQL engine's particular requirements.

Also, while you are in "Manage Files&Database", please note the number of records shown under "Table usage". Then after a few minutes have passed (or seconds, depending on your visitor count), reload the page and check the "Table usage" again. Let me know if the record count gets bigger.

Posted 9 months ago #
SaW
Member

Hello again..
I have a blog on my site on a subdomain (blog.***.net)
I am using a php code which is publishing the latest entries on my site www.***.net's homepage. The code would use the database.. I got an error when i activate the wassup 1.7.1

Warning: Cannot modify header information - headers already sent by (output started at /home/*****/public_html/index.php:9) in /home/*****/public_html/blog/wp-content/plugins/wassup/wassup.php on line 1814

How can i fix this?

Thanks..

Posted 9 months ago #
helene
Moderator

SaW,

Your question is confusing as that error cannot occur unless Wassup's "wassupPrepend" function has been altered to print html/javascript output prior to writing Wassup's cookie or there is another plugin installed that prints output other than headers and cookies during Wordpress' "init" process (see Wordpress' Action reference codex doc for information about the "init" hook).

Please check your code and plugins.

Posted 9 months ago #
Michele
Key Master

May be, SaW you could have a wp-config.php file messed up, or you have some white space around your plugins after the php closing tag (?>) or before...
Please chek these

Michele - WassUp Project

Posted 9 months ago #
SaW
Member

Thanks for your reply Michele..
I tried to deactiveted my theme first. Then i activated wassup but i get the same error again.. Then i deacvtiveted all my plugins and i tried again but the result is same..
I checked the wp-congig.php, it has not messed up.
Any idea?

Posted 9 months ago #
helene
Moderator

Try going to Wassup-options=>[Statistics Recording] Tab and disable "Record Akismet comment spam" (uncheck).

Posted 9 months ago #
SaW
Member

didn't work :/

setcookie("wassup", "$cookievalue", $expire, $cookiepath, $cookiedomain);
this is the line 1814.
should i try to comment out line 1814?
like
//setcookie("wassup", "$cookievalue", $expire, $cookiepath, $cookiedomain);
this?

Posted 9 months ago #
Snowgasm
Member

Got the same problem on 3 blogs in total.

ordPress Version: 2.7.1

WordPress Host Server: Microsoft-IIS/6.0

WordPress Time Offset: UTC 1.5 hours. (10:21 am)

PHP Version: 5.2.6

PHP Safe Mode : off

PHP File Open Restrictions (open_basedir): off

PHP Memory Allocation: 128M

PHP Memory Usage: 17.22M

PHP Script Timeout Limit: 120 seconds

PHP Browser Capabilities File (browscap): browscap.ini

PHP Curl: installed

MySQL Version: 5.0.41-community-nt

MySQL Engine: InnoDB

MySQL Query Cache: 0 (disabled)

MySQL Index (Key) Buffer: 174M

MySQL Read Buffer: 0M

MySQL Wait Timeout: 28800 seconds

MySQL Char Set/Collation: utf8_general_ci

MySQL Timezone: CEST (UTC 2)

On all blogs there is no recording going on in wassup. Even a new blog does not allow recording.

Posted 9 months ago #
helene
Moderator

SaW...I do NOT recommend commenting out the cookie. It is important to WassUp tracking. Your error is someplace else and it is affecting WassUp's ability to write the cookie. Try disabling all Spam check in WassUp. Also triple-check your wp-config.php file. Because white spaces are not visible to the eye, you should rebuild it from a copy of wp-config-sample.php and do NOT copy and paste between old and new as that will also copy white spaces. Edit with "NotePad" or "Vi", NOT Wordpad or Word.

Posted 9 months ago #
helene
Moderator

Snowgasm,
Thank you for providing your server config info. We have noted a syntax compatibility problem with Wassup 1.7.1 and the MySQL engine "innoDB" which you have. To fix, go to Wordpress Admin==>Plugins==>Editor, under "Select Plugin to Edit", select Wassup, scroll down to line #2391 and change

$delayed="DELAYED"; //for delayed insert
to
$delayed=""; //for delayed insert

Click "Update File", and you are done and WassUp should start recording again.
This bug will be fixed in the next revision coming soon.

Posted 9 months ago #

RSS feed for this topic

Reply

You must log in to post.