$response = parent::upgradeUser($userId, $upgrade, $allowInsertUnpurchasable, $endDate);
return $response;
No, it's been fixed for next version.Since the Upgrade to 3.1.0 the shared computers list is empty (and also stays empty). Is that the right behaviour?
You are using an old version (was already fixed). https://marketplace.digitalpoint.com/digitalpoint_betteranalytics-310-zip.3599/notesMine is not empty, but the pagination buttons link directly to the digital-point website.
Also fixed for next version.@digitalpoint
@xfrocks just discovered that this addon caused errors with [bd] Paygates as reported at
https://xenforo.com/community/threads/bd-paygates.47280/page-14
Fix
Changed line 60 to
and add this return around line 100 before the closing } of the function.Code:$response = parent::upgradeUser($userId, $upgrade, $allowInsertUnpurchasable, $endDate);
Code:return $response;
You are using an old version (was already fixed). https://marketplace.digitalpoint.com/digitalpoint_betteranalytics-310-zip.3599/notes
- Better handling of realtime views to threads that no longer exist
- Fixed issue where Model_UserUpgrade::upgradeUser() wasn't returning expected results
- Fixed issue where Computers Shared By Multiple Users could return zero results
- Fixed cosmetic width issue with Computers Shared By Multiple Users reports when there were more than 7 users on a single computer
- Don't try to get realtime API data when requested if API is not set up
- Pass through Google API error if there...
Yeah, I'm pretty sure that was fixed in the 3.1.1 version (the item related to Model_UserUpgrade::upgradeUser() not returning expected results).@digitalpoint is there any way that this add-on would be messing with my user upgrade transaction log? Every entry in the log (since late Feb 2015), lists "Unknown account" instead of showing the username that purchased the upgrade. In the table xf_user_upgrade_log, the field "user_upgrade_record_id" is ALWAYS "0" since late Feb, and I'm trying to think what I changed/upgraded on Feb 23rd that would cause this issue....
Yeah, I'm pretty sure that was fixed in the 3.1.1 version (the item related to Model_UserUpgrade::upgradeUser() not returning expected results).
The AdSense linking doesn't have anything to do with this add-on... you set that up under Google Analytics Admin -> Property -> AdSense Linking... truthfully, it's sketchy at best anyway and has all sorts of problems. Like it really only works well with a single website (the default one you set), and works terrible if you have multiple websites.I can't seem to get adsense tracking to work with this add-on. I have this message in my Google Analytics profile for the site:
Property Aspies Central is configured to use Advertising Features, but it isn't collecting data for these features.
Duplicate Campaign Parameters:
Campaign parameters are case sensitive, so hits with the same source text but different letter cases will show up separately in reports. As an example, the sources "referral" and "Referral" would be considered different sources and would have separate rows in reports.
Property http://mydomain.com is receiving hits with utm_sourceparameters of the same text but different letter cases, such as:
- MyDomain.com
- mydomain.com
To avoid having data from the same source split across multiple rows in reports, ensure all your campaign links have parameters of the same case. Alternatively, you can set a case filter for Campaign Source on your views.
We use essential cookies to make this site work, and optional cookies to enhance your experience.