Jump to:
| Project: | Woopra |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I just enabled the module, discovered that no need to put a Key on the settings, but the tracking is not worknig.
I disabled the module, copy&paste the script to my page.tpl.php and then it worked, but of course I didn't get the names of the users and so on (as I did on a drupal5 site for example).
Removed the script from page.tpl.php, reenabled the module but it's not there...
I have some variables starting with woopra on my variables table. I cleared the cache, even disabled it, also the Js optimizer... I removed all the rows that started with woopra from my variables table, as doing the "uninstall" from the modules page didn't work, then reenabled it but still not working.
What am I missing?? The site is www.lynxeds.com
Comments
#1
I'm having the same issue... any ideas?
#2
Same here, subscribe.
#3
I just added the script by hand on my page.tpl.php, but that is not the desired (in fact, that method doesn't need the module at all...)
The main problem using this is that I don't see the username of the registered users...
#4
seems like in a recent update that the https://sec1.woopra.com/js/woopra.js location doesn't exist anymore. Their stored location of the file must have changed bc I can't access the file to have it loaded in anymore :\
#5
Has anyone resolved this?
Baffled....
Mike
#6
Still with the code manually added into the page.tpl.php...
#7
Same problem.
#8
Same problem here. The previous version of the Woopra module was working fine: however, I updated it yesterday and tracking info is no longer being passed upstream.
(I have another site running Drupal 5.20 with the 5.x version of the module and it's working perfectly, even after updating to the newest version a few days ago.)
#9
I had the same problem, then I noticed that the theme I am using does not have 'standard' footer code in it. i.e.
<div id="footer"><?php print $footer_message . $footer ?></div>As soon as I added this into the theme the woopra code was added and it all works OK
#10
My theme is printing both variables but code seems to be missing too. So not sure if this is going to be the problem for other people in here...
#11
Latest dev version seems to work fine. Try upgrading to that.
#12
I have the same problem with 1.3 - should I downgrade...? (And no - I do have a footer in my theme. This shouldn't be the problem.)
#13
I too had this problem. I upgraded to Woopra 6.x-1.x-dev (2010-Jan-11) and still no luck. I finally got it to work by going to admin/settings/woopra and selecting the roles I wanted tracked. The text says "Leave empty for all roles.", but I think that's incorrect.
#14
Installed latest stable release.
The README.txt mentions signing up for a website ID - but does this need to be added to the Drupal config somewhere? Looking at the generated code snippet on woopra.com the js code included the site ID - but in the Drupal settings I see no form to enter the website ID in to !
I had to check 3 roles in order to make the js code appear - authenticated, anonymous, and an empty checkbox option (!)
The output in the footer of my site :
<script type="text/javascript">var woopra_array = new Array();woopra_array['name'] = 'superuser';
</script>
<script src="http://static.woopra.com/js/woopra.js" type="text/javascript"></script>
This looks nothing like the code provided by woopra.com:
<!-- Start of Woopra Code --><script type="text/javascript">
var woo_settings = {idle_timeout:'300000', domain:'example.com'};
var woo_actions = [{type:'pageview',url:window.location.pathname+window.location.search,title:document.title}];
(function(){
var wsc = document.createElement('script');
wsc.src = document.location.protocol+'//static.woopra.com/js/woopra.js';
wsc.type = 'text/javascript';
wsc.async = true;
var ssc = document.getElementsByTagName('script')[0];
ssc.parentNode.insertBefore(wsc, ssc);
})();
</script>
<!-- End of Woopra Code -->
So currently this module is less useful than putting the code in to the page.tpl !