viewed nodes not heating up

Semei, Can you please export your content-type so that we can see your field configuration.

Do you use the Entity Cache Modules?!

Regards,

Tobi

I have the same issue (7.x-2.x-dev). I've selected the default profile (default_now) and added it to the standard Articles node on a blank Drupal installation. The radioactivity value only decrease over time but does not add value when viewing the node.

It's a default Drupal installation with no other modules installed.

This happens in my live installation but not in my local installation of the same site (v. 7.x-2.7).
I have checked all the settings multiple times but I can't pin point the problem.

I'm using the "live storage" type and the bootstrap configuration is pretty much the same with my local one:

define('VAR_RADIOACTIVITY_CHECKSUM_SALT', 'my_salt_here');
define('VAR_RADIOACTIVITY_DRUPAL_ROOT', '/home/my_folder/public_html');
define('VAR_RADIOACTIVITY_TEMP_DIR', '/home/my_folder/public_html/tmp');

Permissions for radioactivity-bootstrap.cfg.inc are currently 755.

Any ideas on what might be causing this?

To debug this further you could:

• Check if you can access /sites/all/modules/radioactivity/emit.php. It should say "Invalid post data - check configuration."
• When on a node page, check your XHR communication between browser and server -- F12 in Chrome or Firefox with Firebug > Network / Net tab > XHR and look for emit.php

Great, thank you.

OK, so, /sites/...../emit.php outputs the "Invalid post data" message.

In Firebug, I get a "400 bad request" on the live website whereas it works fine on the same site locally.

The post data on the live site is the same with the local site:

a:1:{s:4:"Live";a:1:{s:4:"node";a:1:{s:6:"review";a:1:{s:20:"field_energy_monthly";a:1:{s:3:"und";a:1:{i:84;i:10;}}}}}}

However the response is different.

Live site:

HTTP/1.1 400 Bad Request
Date: Tue, 18 Dec 2012 15:45:09 GMT
Server: Apache
X-Powered-By: PHP/5.3.17
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html

Local site:

HTTP/1.1 200 OK
Date: Tue, 18 Dec 2012 15:48:23 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.18
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Keep-Alive: timeout=15, max=83
Connection: Keep-Alive
Content-Type: text/html

Please advise. Thank you very much.

Thanks,

Emit.php displays "Invalid post data"

I've also checked the XHR communication. I get the following error in Firebug on the response tab (with 7.x-2.x-dev) and the profile (default_now):

Notice: Undefined index: RadioactivityLiveIncidentStorage in /d7/sites/all/modules/contrib/radioactivity/emit.php on line 30

Fatal error: Call to undefined function _radioactivity_update_energy() in /d7/sites/all/modules/contrib/radioactivity/includes/RadioactivityIncident.inc on line 53

@gkom, unfortunately I don't have apache installed anywhere, but if I would allow myself to guess, I would say that your live site disallows POST requests on emit.php for some reason (I assume GET on live says "Invalid post data..."). Check your logs to see if emit.php is actually hit with POST request. My suspicion is on very strict rewrite rules.

@combicart, I was talking about version 2.7. -dev has changed some. Again, I will allow myself to guess and say that you have wrong ..._DRUPAL_ROOT path in your radioactivity-bootstrap.cfg.inc.

Unfortunately, all I can offer now is speculations.

I confirm that the request is Post and that a Get request outputs the "invalid post data" message.

The Post data seems to be correct and as a result I assume that everything runs smoothly through radioactivity-bootstrap.inc.

Post data is:

checksum:561c...blahblah
data:a:1:{s:4:"Live";a:1:{s:4:"node";a:1:{s:4:"news";a:1:{s:20:"field_energy_monthly";a:1:{s:3:"und";a:1:{i:281;i:10;}}}}}}

There no incidents in the logs, neither in Drupal's nor the server's. The rewrite rules used are Drupal's default ones. I tested this exact installation on another server (Apache again) and I'm getting the exact same problem.

Is there a more specific test I can run?

Your help is greatly appreciated, thank you.

I added a call to stripslashes before generating the checksum in _radioactivity_checksum_generate (radioactivity-bootrstrap.inc) as suggested in Payload validation fails due to escaped quotes and the Post request is now successful.

Request Method:POST
Status Code:200 OK

However, the energy does not increase.

I am getting with the latest 7.x-2.x the same fatal error mentioned in #10.

The logic in function _radioactivity_light_initialization() seems to be broken - it doesn't actually bootstrap if the config file exists.

Here's a minimal patch that fixes the fatal for me.

I upgraded to the current 7.x-2.x-dev release and I was getting the error mentioned in #10.

The patch provided by pwolanin in #16 took care of the error and the module now works properly.
This patch should be reviewed and committed asap.

Big thanks and happy new year to you all!

Patch #16 is a performance killer - it'll lead to doing a drupal bootstrap every emit.

Real fault lies within emit.php which did not check if the storage class required drupal bootstrap - fixed in latest commit, please give it a go! (As a sidenote emit.php was rewritten about a month ago for the dev branch to support emitter accuracies).

Sounds like the better fix - I was wondering why the bootstrap required param of each class was not being used.

Latest .dev is working nicely. Your quick response is truly appreciated tcmug. Thank you.

seems to be working so "fixed" is more appropriate