Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
I just upgraded to 7.x-2.3 and I am getting the following error when viewing a node with a radioactivity field attached to it:
"NetworkError: 400 Bad Request - http://www.example.com/sites/all/modules/radioactivity/emit.php"
Response: Invalid post data - check configuration.
Any idea what configuration I need to check?
Thanks
Comment | File | Size | Author |
---|---|---|---|
#7 | data_field_radioactivity.jpg | 131.76 KB | Cromicon |
#6 | firebug.png | 24.6 KB | Cromicon |
Comments
Comment #1
tcmug CreditAttribution: tcmug commentedUsually this is the result of the security checksum salt being different so;
Compare your radioactivity-bootstrap.cfg.inc with the one the assist shows in admin/structure/radioactivity/settings - there is a new variable that 2.3, but I doubt that it is the cause.
Also you can try deleting the file if present, see if it helps and re-create it to see if the problem persists.
Comment #2
pnigro CreditAttribution: pnigro commentedI re-installed the module and the error is gone. However, the field is still not emitting. I checked firebug and the logs for errors and there are none. If I enter a default value for the field the decay process works as expected. I am not sure what else to check. Any thoughts?
Thanks again
Comment #3
tcmug CreditAttribution: tcmug commentedPlease check that you are not using the flood protection.
Yes, it has happened to me many many many times.
Comment #4
pnigro CreditAttribution: pnigro commentedI tried your suggestion, but unfortunately I am getting the original error. The only thing I can think of is I am testing this on a subdomain. Could this be the cause?
Thanks
Comment #5
Cromicon CreditAttribution: Cromicon commentedHello. I'm getting this too on 7.26
400 Bad Request (showing in Firefox Firebug) in sites/all/modules/radioactivity/emit.php - Response: Invalid post data - check configuration.
I checked the radioactivity-bootstrap.cfg.inc file it looks ok. I show it here, it is CHMOD 0644:
I had no /tmp directory so created one in Drupal root CHMOD 0755 (for now).
Not knowing where it should be I placed one in the radioactivity module folder too (/public_html/sites/all/modules/radioactivity). I tried this admittedly pot luck approach to no avail.
I have used a defined CHECKSUM_SALT and also the undefined one.
I have un-installed the module and reinstalled. (Having had to delete the radioactivity field after cron).
I'm not using flood protection.
I think I have two questions really.
1) Where should the /tmp folder be?
2) Should I actually display the Energy display: Hotness gauge field anywhere (I have tried with and without doing so).
I've also tried a logical approach believe it or not :-) Given that the /tmp folder might be required in Drupal root I thought this might work but it doesn't.
Any help you can provide would be great thank you.
Comment #6
Cromicon CreditAttribution: Cromicon commentedThe above is what firebug is telling me is in the post. Does that look about right for what emit.php will be expecting?
Comment #7
Cromicon CreditAttribution: Cromicon commentedHi :-)
I've updated all content with a starting value of 2000.
I've tried all combinations of settings now and the error is consistently involving emit.php not accepting the post data.
I have created the radioactivity-bootstrap.cfg.inc manually as well as using the configuration helper.
I have used a long checksum salt and also kept it at default "undefined"
I have made the radioactivity counter visible in all cases then repeated with it hidden.
I have tried all storage methods other than memcache as I don't have that.
With emit.php not accepting post data none are working of course.
The radiactivity half life is working though as evidenced by the screenshot.
I think this is a bug now rather than a support request. If I can help in any way, or if you need more information please let me know.
Radioactivity version 7.x-2.6
My drupal version is 7.14
PHP 5.2.17
Web server Apache/1.3.42 (Unix) mod_gzip/1.3.26.1a mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.8e-fips-rhel5
Database system MySQL
Database system version 5.0.91mm-log
Comment #8
Cromicon CreditAttribution: Cromicon commentedComment #9
jenlamptonSame problem on newer versions of the module.
Comment #10
jenlamptonWeird...
I changed my settings (admin/structure/radioactivity/settings) as follows:
- salt for checksums: undefined
- Enable flood protection (unchcked)
- drupal root (confirmed correct)
- tmp directory (confirmed correct)
And now the
400 Bad Request
error has stopped. Still no increase in value where there should be, but at least I have determined that it wasn't this error that was causing those increases not to happen.... back to the drawing board!