Closed (duplicate)
Project:
Ubercart
Version:
6.x-2.x-dev
Component:
Payment
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Oct 2011 at 04:47 UTC
Updated:
8 Dec 2011 at 22:35 UTC
Hello all, my site has a Comodo SSL certificate that is signed and the chain is complete. The site displays a padlock on Chrome and IE and is marked as secure on Opera. However, when I enable the Google Analytics module, the site is no longer marked as secure and I am asked if I want to display unsecured content. This is clearly being caused by the module or by Google Analytics itself. Any suggestions?
Comments
Comment #1
hass commentedNo example link provided.
Comment #2
frank0051 commentedI didn't leave a link because I disabled it. I've leave the site like this for the next 24 hours, be sure to visit it before then, haha. https://www.croomsalumni.com/
Comment #3
hass commentedThis is not a bug of the GA module. It's the Google Checkout code embedded by you without SSL logic. Google Docs are missing this... Google Docs bug.
Comment #4
hass commentedComment #5
hass commentedComment #6
frank0051 commentedIt's not the Google Checkout module, otherwise the page wouldn't be secure once I disable Google Analytic.
Comment #7
frank0051 commentedSee, look, Google Analytics is now disabled - low-and-behold, the page is now secure.
Comment #8
hass commentedYou can hire me... Send me a mail for payed support. It's checkout.
Comment #9
frank0051 commentedI'm not going to pay you do to anything when you haven't even shown why it is Google Checkout. Why is it Google Checkout when the only difference between the period when you clicked on the link and now is Google Analytics? Yet, that happens to make the difference when I disable. Why is the page now secure when Google Analytics disabled? Provide some evidence, then maybe I'll think about providing you some money to fix it. Otherwise, the problem hasn't been fixed and the problem still lies with Google Analytics module.
Comment #10
hass commentedPlease stop changing the title. Enabling/Disabling GA does not prove anything. You are not a developer, aren't you?
Here is the deal - if I can prove this is checkout integration you pay me 50€ - otherwise not. I can fix your checkout integration code, too :-)))
Comment #11
frank0051 commentedI'm using the Google Checkout module for Ubercart - so it isn't like I do any coding.
Screw it, I just won't use your module. Google Checkout seems to work just fine without it and is secure until I tell it to send the cart unsigned. Consider it fixed and consider me one less user using this module. I will also be removing it from the other two sites I have it on.
Why the hell would I want to pay you when you haven't offered any proof of anything.
Comment #12
frank0051 commentedTurning it back to active for other individuals that might have the same problem.
Comment #13
frank0051 commentedAnd, your new title cannot even be right since I did not use the Google Docs examples or copy and paste. So changing the title back too.
Comment #14
hass commentedDON'T CHANGE THE TITLE AGAIN, PLEASE!
Deal or no deal? I offered you - only to pay if I'm able to prove that I'm correct and google checkout code is the reason. Yes/No, but don't complain if you need to pay, please. Otherwise we close this case here.
Comment #15
frank0051 commentedThe reason you have given in the title isn't even right, I did not use the google example, I used Ubercart's core Google module. You're title still isn't correct, hence why it is being change. I did not use Google Docs to get some tracking code example. Instead, are you saying Ubercart is the problem? If so, title the issue correctly AND tag Ubercart. However, I don't think it is since it is in the core of Uercart. Again, the problem ONLY exists with THIS module, not Ubercart. And, I question how it could be Google Checkout's tracking numbers either (since you removed "copy and paste" from the topic) since I am using https in the API integration setting on Google Checkout and sending the callback contents as over HTTPS using the Notification as XML selection.
You would need to explain/offer proof as to why you think it is Google Checkout before I'm going to pay you, or allow you to change the title to something that isn't even relevant. All you have to do is offer some type of RELEVANT REASONING (I can type in caps too). I'm fighting you on this because even though you may be a developer, it doesn't give you the right to extort people for money or blame another module WITHOUT OFFERING a logical reason or some proof. You may indeed be right, but that doesn't mean you have to be pompous about it.
So, again, you are the one that is the wrong for changing a topic title without even offering explanation or reasoning of it.
--
In sum, provide some reasoning, provide some logic, or provide some proof and I will stop changing the topic back. That is what you are supposed to do in an open source community: provide evidence and reasoning, not just make assumptions willy-nilly and change contributions made by others (afterall, an issue posted on Drupal is just that, a contribution).
Comment #16
hass commentedI'm the maintainer of GA. There is no bug in the GA module.
So we finish discussion here as you have not answered the deal with - Yes.
Comment #17
frank0051 commentedNo, it isn't fixed, if you are going to write it off - write it off correctly: as closed (won't fix) with the proper title.
Again, being a maintainer of a open source project doesn't make you immune to the accepted protocol of open source communities: reason, logic, and factually based solutions. You have not offered any of these, therefore you have no right to change a title.
Comment #18
hass commentedMy queue, my decission. Nothing to fix.
Comment #19
frank0051 commentedIt isn't YOUR queue, it is the open source community's queue. You let go of all rights to the intellectual property when you submitted here, plus you are building on top of Google's API.
Again, don't violate commonly held open source protocols without providing reasoning, logic, or proof. Provide reasoning, logic, or proof that shows the title you want should be what (as I have with my suggested title) and I'll stop editing it back. I'm suggesting the topic title I have in order to help other users that may face this problem in the future...and, to alert them that it is something you [as a maintainer] don't see fit to fix.
Comment #20
hass commentedThe maintainers of a project queue make decissions. Stop changing status and titles or I will lock the case.
Broken documentation is here http://code.google.com/intl/de-DE/apis/checkout/developer/checkout_analy.... If you need a developer to fix and you don't understand it yourself what is wrong you need to hire one.
Comment #21
hass commentedComment #22
longwave#1137970: Google Checkout JS being loaded on cart/checkout without https
Comment #23
frank0051 commentedSee, Hass, that's all you had to do, provide reasoning, logic, or proof. You could have avoided this entire waste of time by doing so.
Thank you for actually doing what is accepted in an open source community - you showed that the problem isn't with your module, but rather with Ubercart. There, was that so hard to actually do what is right?
Comment #24
hass commentedYou wasted the time. I do not need to prove anything.
Comment #25
frank0051 commentedYet you did, imagine that :rolls eyes:.
Comment #26
payalord commentedMay be it is not google analytics module. May be it is Secure Pages module have a problem. Try to disable option called "Switch back to http pages when there are no matches" in Secure Pages module settings and check your https pages again.