Here is the situation:

If someone browses to the site with javascript already turned on, Hashcash allows them to post.

If someone browses to the site with javascript turned off, gets the error message, then turns javascript on in order to post, they're still treated as though javascript was turned off in their browser.

My site uses aggressive caching in order to handle the traffic and I'm wondering if maybe Hashcash is storing a "THIS BROWSER DOESN'T USE JAVASCRIPT" message in cache somewhere, so it doesn't bother testing the poster a second (or third, or fourth) time around.

Or it could be some other problem completely unrelated to site caching, but that was my first thought.

Comments

sdrycroft’s picture

Hmmm, I've not experienced this. Hashcash definitely doesn't record whether or not a user has Javascript enabled. What browser have you found this issue with? The new 6.x-2.3 version may fix this - you'll need to reload the page (possibly twice) after enabling Javascript though.

ubersoft’s picture

I'll update to 2.3 and start collecting more specific data from my users/unwitting test group. :-)

sdrycroft’s picture

Status: Active » Postponed (maintainer needs more info)

2.4 may fix things for you also (ensure all caches are cleared before trying), please let me know if it doesn't, as I'll need to have a thorough look into things.

kabojnk’s picture

I can confirm this as well. We're running 2.5 and it occasionally pops up for me, especially on a first trip to a page. Users are complaining about it too. This has happened on multiple browsers (Firefox and Chrome and IE 6/7/8). We have no caching methods enabled on our Drupal site either. The message goes away after refreshing once or twice (despite having Javascript enabled the entire time). I can't really tell users to do that though, and I've disabled the module until this might get resolved... it's too bad, because it was working great despite the problems with users not being able to post.

xmacinfo’s picture

I can confirm those problems as well on any browsers.

An anonymous user with JavaScript on will get a warning that JavaScript is disabled. Reloading the page sometimes remove the warning. Entering a username and password will also remove the warning.

In short, anonymous users with JavaScript on see often the warning. All authenticated users do not see the JavaScript warning.

I am thinking about removing the JavaScript message warning altogether from the module until a fix is available.

I did not try to remove the cache, though. Which would not be a good idea, though.

lirazsiri’s picture

I can confirm this is still a problem. Just got the "submission disabled because you don't have Javascript enabled" message on the registration page as an anonymous user using Google Chrome (which obviously has good javascript support). Reloading didn't help. Had to clear the cache. Just the regular cache mind you. We're not using aggressive caching.

I've had to disable the module on our site until this is fixed. Maybe I'll hack the module myself to remove the message.

sdrycroft’s picture

Status: Postponed (maintainer needs more info) » Active

This is clearly still an issue. I'll be upgrading the module to Drupal 7 in due course, so will hopefully be able to look a little closer at some of the issues with the module.

sdrycroft’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

I'm afraid I am having to drop support for the 6.x branch of Hashcash - I simply don't work with Drupal 6 anymore.