Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.My auto-refresh didn't worked at first, because I was testing your module in a subdirectory, and the Ajax call was returning a 404.
Many thanks, this is really a great module!
Jérémy
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | livecoverage.js_.basepath.patch | 412 bytes | Remon |
| #2 | livecoverage.base_path.patch | 1.97 KB | jonskulski |
Comments
Comment #1
kevin hankens commentedYeah, sorry about that :) There is an admin setting for that purpose, but maybe not the most elegant solution. Try going to admin/settings/livecoverage and see if that works.
Comment #2
jonskulski commentedKevin,
(We had talked in #drupal about converging our modules, so I'm reviewing live coverage so I'll have some patches & issues for you :) - heads up!)
I ran into this too. The subdirectory is an ok solution, but base_path() will catch subdirectories for you.
For example I develop locally at
http://localhost/Sitename
and on our server at
http://site.c3.net/~jskulski/
And in both cases base_path() will catch these for you and not require any administrative actions (which is good). Also, I was confused at first, I thought it was a subdirectory WITHIN the files dir, and only after firebug told me about a 404 did i realize what it was.
Here is a patch that adds base_path support for the updatedir and removes the the live subdirectory variable from admin settings.
Comment #3
kevin hankens commentedThanks! I like that solution a lot, I just committed the patch.
Comment #5
Remon commentedAlso, Drupal.settings.basePath should be taken into account.
Comment #6
Remon commented