Comments

stillcut’s picture

What Lorell VanFossen from the Woopra team answers to this question

"Probably. Please contact the Drupal module authors to ask them to update it. It will work, but the new version of the script works a lot faster. "

http://www.woopra.com/forums/topic/is-drupal-woopra-module-outdated

SoCalCreations’s picture

Category: task » feature

Just posted under that forum post

After going through the code in the file 'woopra.module' I noticed that there is two possibilities for using the Woopra module, one for the beta and one for the production.

The beta had the code 'https://sec1.woopra.com/js/woopra.js'
The first production code for woopra is also included of 'http://static.woopra.com/js/woopra.js'

It seems to me that the first production code must be changed to an 'elseif' statement and added above that code similar to
if (variable_get('woopra_cache', FALSE)) {
$woopra_js = '/'. _woopra_cache('http://static.woopra.com/js/woopra.v2.js');
}

One other thing I noticed is this module is NOT for use in the Drupal Sites/All/Modules directory as it does not contain the ability to do subdirectories or subsites. Furthermore I would prefer the drupal module to have the ability to actually to login to my woopra account for accurate tracking.

just my .02cents
Will
SoCalCreations.net

tomdeb’s picture

This should be now fixed in CVS (message http://drupal.org/cvs?commit=312878)

Since woopra got out of beta, I don't have a full account. For this reason I had to remove the code related to ssl support.

Please let me know if it works for you.

I plan on creating a new release once I have updated support for usernames,avatars and profiles

tomdeb’s picture

Assigned: Unassigned » tomdeb
Status: Active » Needs review
stillcut’s picture

Thank you for the upadte.
I will test it as soon as possible.

I think you should contact the Woopra team to ask a "special" due to for status of drupal maintenair.

archimedes’s picture

Has this been committed in the latest (non-dev) release?

killua99’s picture