Closed (fixed)
Project:
Jirafe
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Oct 2012 at 15:43 UTC
Updated:
23 Dec 2012 at 15:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
guguss commentedHi,
Can you try to update the module to the latest Dev version ?
It works fine on my install so I don't know what could go wrong on your site...
Comment #2
threadsniper commentedI installed the Dev version but still not getting any data. Let me make sure I am inputting the data correctly:
App ID = Organization ID
App token = Organization Token
Is this correct?
Comment #3
threadsniper commentedOkay, it seems the problem is in obtaining the proper application id and token. How is this done?
Comment #4
guguss commentedYou can get your App ID and App token from the Commerce Guys Marketplace.
Simply fill in the form at the bottom of the page and process the checkout (no credit card required since it's a free subscription...).
Comment #5
guguss commented@threadsniper: Does that answer your question ? Does the module work for you now ?
Comment #6
threadsniper commentedApologies GuGuss, I've been trying to handle this through Jirafe support as well. They also pointed me in the direction of the Marketplace; I went through this process. Still, no data is being collected. I checked and re-checked all data to ensure it was correct. I am at a loss as to what is wrong here.
Comment #7
guguss commentedThat's weird ! Are you working locally (it should work anyway) ?
There might be something wrong in the Jirafe configuration. Do you see that page (see the attached screenshot) when you go to admin/commerce/config/jirafe ?
Comment #8
threadsniper commentedUnfortunately I only see the Application ID & Token.
Comment #9
willieseabrook commentedI have the same issue. Against both 7.x-1.0-beta1 and 7.x HEAD.
At /admin/commerce/config/jirafe I see fields only for: "Application ID" and "Application Token"
The site configuration fields never appear. This is because of the following logic in jirafe.admin.inc:
After install, $config['sites'] is always empty, so the config form is never shown.
I found a function "jirafe_synchronize" that appears to be intended to pull data from the api to fill up the sites array. But jirafe_synchronize is never called anywhere - not in a cron hook or in install. I tried a drush php-eval "jirafe_synchronize();" to force it, but the API returned a 403 denied error.
Thus, the reason the tracking javascript (jirafe variable) is never added to the page is because jirafe_get_current_site() will always return null, and it just returns.
i tried to cheat, by first figuring out the variable structure and then hardcoding it into settings.php
then using jirafe_current_site_alter to force its use on local devel.
After doing all this, I confirmed that jirafe is being added by inspecting the jirafe var in firefbug console.
Nonethless, data is still not appearing in my Jirafe dashboad.
Hope this info helps. I'd try and patch this to help but I've only been a Jiraffe user for 30 minutes and have no idea of intentions or anything - e.g is jirafe_synchronize supposed to be called, or is that some kind of legacy function. I also checked Confluence and couldn't find any info about how the API is intended to be used.
Comment #10
willieseabrook commentedComment #11
hazaAttached a patch that force the synchronize to be done when we submit the admin form. So it should correctly populate the jirafe_config variable with the data that belongs to the users and sites.
Comment #12
theo_ commentedCommit from #11 fixed the bug for me.
Sites & users part of jirafe_config variable are correctly populated now when saving jirafe's configuration.
Comment #13
hazaAdd a condition in the update that prevent the sync to do be done if the data are already there.
Comment #14
hazaTweaked our synchronize code. If some "user ID" and "site ID" were already existing, the old sync function never take care of using them to call jirafe API sync() method. That means jirafe will create a new "site ID" and "user ID", deleting the existing one.
Patch fix that.
Comment #15
guguss commentedThanks Haza !
Patch #14 committed here
Comment #16
guguss commentedComment #17
jsacksick commentedjirafe_synchronizeis called without catching the potentially exception thrown when the app_id and the token are not configured.Comment #18
jsacksick commentedThe attached patch fixes the issue
Comment #19
hazaSeems good !
Comment #20
jsacksick commentedComment #21
threadsniper commentedI am possibly extremely unlucky. Have updated to the latest iteration of the module (beta4) and still I get absolutely no data.
Comment #22
brephraim commentedConfirmed. Still only seeing Application ID/Token on the configuration page as well.
Tried both patches, nothing. Tried the beta4, nothing.
Comment #23
brephraim commentedComment #24
andor.koza commentedI am unlucky too.
I inspected the code a little bit. And as I see after we add the appID and appToken than after submit the module sync the data and get the sites & user information.
so, I think there is a problem, because I do not get back any site or user data.
I also checked my Jirafe account, but I do not see anything wrong.
I'am using drupal 7.17 and commerce 1.4 (but I think at this part these infos are irrelevant)
Anybody solved the problem?
Comment #25
andor.koza commentedI think I solved the my problem, may be it will help out somebody too.
So when I created a Jirafe account at www.jirafe.com than it simply not works, if you create account at http://marketplace.commerceguys.com/ than it works.
For me it solved the collecting data issue.
Comment #26
hazaWe saw that today, we are investigating why, with jirafe's team.
Comment #27
guguss commentedThe dashboard can't collect any data if the registration happened on Jirafe website... Please only subscribe from the Marketplace !
There is a "free" subscription where you don't have to pay to test the dashboard.
Comment #28
threadsniper commentedUnfortunately, this happens in either case. I have subscribed via Jirafe's site, and done it through the marketplace, in both cases the site collects no data.
Comment #29
threadsniper commentedAny traction on this continued issue?
Comment #30
jsacksick commented@threadsniper, are you using your credentials (App ID, token) on multiple websites (or environments) ? If you do so this can cause issues :
(From the jirafe api documentation)
If it's not the case, then check your drupal logs by going to (admin/reports/dblog) and check if you have curl errors (Jirafe is using it for making requests to the API), this could explain why and you'll probably have to adjust your environment settings.
Comment #31
guguss commentedI reported the following issue here #1859946: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set.
Comment #32
threadsniper commentedjsacksick -- I assumed that having the connection active on multiple sites (like our testing and staging environments, for instance) would cause an undesirable disparity in the data being collected, so I've had the module either disabled or not installed on those other sites since implementing it on our live site. Also, there are no curl issues either. I cannot seem to correct this issue.
Comment #33
threadsniper commentedStrangely, I decided to sign up on the Marketplace again and grab another token and app id, and now Jirafe is working as advertised. The only question is, however, where do we take it from here, as we want to pay for a higher service level to have access to more features, and the token and id from the jirafe site dont' seem to work for Drupal Commerce.
Comment #34
luksakI solved the issue with this patch:
http://drupal.org/node/1859946#comment-6826348
But this module really lacks documentation. I created a issue for this: #1862304: Missing documentation on setup
Comment #35
luksakDidn't mean to change the status...