#stripe

/

      • TakeMyMoney
        yea, i have another test account on the main account which is the connected account
      • markin
        TakeMyMoney: so the customer on the connected account has a card on file (and you're logged into the connected account's dashboard), and you're using the connected account's access token to create the charge?
      • TakeMyMoney
        correct
      • markin
        Then I'd email support@stripe.com and make sure to reference the iar_ of the log request
      • TakeMyMoney
        ok
      • zachsnow joined the channel
      • zachsnow has quit
      • Raj_ has quit
      • gwendall joined the channel
      • markin what is the iar_
      • nm
      • markin
        the request number from the stripe logs
      • TakeMyMoney
        lol
      • yea i see it
      • gwendall has quit
      • sakcraig joined the channel
      • irctc566
        Markin you there?
      • shalecraig joined the channel
      • we tried editing out that line
      • I switched Stripe to test mode
      • switched out live publishable and secret keys for test kills
      • markin
        yeah, I'm here
      • irctc566
        in index.html and process.php files
      • and it's not working
      • I'm getting internal server error
      • even tho the verisign green check is coming up when I put my card info in
      • markin
        your index.html still has the live key for Stripe checkout
      • for some reason there is still some old Stripe.js code in there
      • irctc566
        well that's weird
      • ok let me fix key issue
      • the js code I don't understand tho..
      • markin
        you don't need js code for what you're doing
      • sakcraig has quit
      • aracodex12 has quit
      • irctc566
        well the key is correct
      • still not working..
      • should I remove the js code and see if that works?
      • markin
        the js isn't even being called because you don't have jquery included
      • irctc566
        yes correct
      • markin
        its showing me publishable key: pk_SkLMPem9319mAKSfYSBWCIIS4RH7e which is a live key
      • irctc566
        in page source?
      • maybe hard refresh
      • I'm seeing test key
      • Seventoes
        where is that key from? my keys all have _live_ or _test_ in them
      • irctc566
      • markin
        Seventoes: its just an older key
      • Seventoes
        ah, weird :P
      • markin
        irctc566: I see you changed the key in the js but not the one in the Stripe checkout code
      • data-key="pk_SkLMPem9319mAKSfYSBWCIIS4RH7e"
      • irctc566
        oh crap
      • where's checkout code lol
      • markin
        just lower in the page
      • in div id chargebox
      • irctc566
        dumb mistake my bad
      • imkmf has quit
      • markin
        so I got the internal server error, does your php error logs show anything?
      • you likely have an uncaught exception
      • aracodex12 joined the channel
      • irctc566
        no it's not showing anything
      • markin
        Stripe logs show anything to v1/charges?
      • fugiman has quit
      • irctc566
        nope just tokens
      • fugiman joined the channel
      • got the internal server error
      • Seventoes
        there should be something in your php error logs for sure
      • markin
        hmm, maybe you edited / commended out that line in the php.ini wrong? though weird how your php error logs don't log it
      • irctc566
        I'm online with my hosting
      • apparently some "necessary" PHP modules are missing
      • lol
      • sakcraig joined the channel
      • I've been working with you and them to hash this out
      • ok interesting it's generating the SAME error in the log that my clients were generating
      • I assumed NYC American Express could only be one person but apparently even the test keys are generating same error
      • markin
        and this is why I love my side project and node
      • Seventoes
        this is why i hate shared hosting :P
      • irctc566
        lol it's not even shared hosting
      • it's liquidweb just FAILING the last 1.5 yrs
      • shalecraig has quit
      • Seventoes
        is it managed dedicated?
      • irctc566
        I have no idea why the quality of their product and support has gone down so hardcore
      • yes
      • Seventoes
        specifically _managed_ dedicated? :P
      • markin
        its all about commencepayments.com managed stripe :p
      • Seventoes
        cuz if it's unmanaged all this stuff is on you, their support won't really help unless the particular agent you're talking to is in a good mood :D
      • irctc566
        yeah it's managed
      • fully managed vps
      • Seventoes
        k :D
      • dqsf_ joined the channel
      • irctc566
        last year there was a database issue
      • corrupt tables
      • from another longstanding issue
      • instead of fixing it the tech terminated my server
      • started a new one
      • handed me a blank site
      • it was surreal
      • Seventoes
        if the disk was screwed i can see that happening
      • irctc566
        I'm like.. you know you just effectively ended a 6 figure business, right?
      • Seventoes
        disk goes bad an no backups = you get a new server, nothing else that can be done.
      • irctc566
        well they spent the next 12 hrs restoring the site from multiple backups
      • |ShortCode|
        That long? Wow...
      • irctc566
        actually more like 10
      • it was a bitch.
      • end result: Rebuilding Apache will resolve the 'stock' module issues: PDO, pdo_sqlite, pdo_mysql. Once this has completed I can resolve the issues with the non-stock modules: magickwand, imagick, oauth, uploadprogress, and ixed. EasyApache will take some time, usually around 40 minutes sometimes up to an hour
      • thank you Markin you have been great.
      • Seventoes
        welcome to the wonderful world of PHP! *puke*
      • dqsf_ has quit
      • |ShortCode|
        C'mon Seventoes :P
      • Seventoes
        *continues puking* :D
      • markin
        Long live Node!
      • Seventoes
        that ^
      • |ShortCode|
        Node, has it share of problems as well.
      • goddard
        with the pre-built form how can I just use text with my own class to launch the script?
      • markin
        goddard: you'd have to do a custom integration
      • goddard
        k
      • shalecraig joined the channel
      • sakcraig_ joined the channel
      • irctc566
        lol!
      • sakcraig has quit
      • TakeMyMoney
        YOU HAVE TO BE SHITTING ME MARKIN
      • just updated the stripe gem and everything is a go now...
      • markin
        TakeMyMoney: what?
      • yay!
      • TakeMyMoney
        lol
      • shalecraig has quit
      • sakcraig joined the channel
      • _DB has quit
      • sakcraig_ has quit
      • pokoleo joined the channel
      • sakcraig has quit
      • sakcraig joined the channel
      • shalecraig joined the channel
      • |ShortCode| has quit
      • pokoleo has quit
      • aracodex12 has quit
      • sakcraig has quit
      • pokoleo joined the channel
      • kellysutton has quit
      • shalecraig has quit
      • irctc566
        Markin you there?
      • markin
        irctc566: yup
      • irctc566
        got it working
      • fucking local php.ini file
      • here's the blurb from the page you pasted that got us headed in the right direction..
      • Also, if you are in a shared hosting environment which is upgrading its PHP to 5.4 and running into this kind of problem try removing your local php.ini and using the default php.ini on the server instead. I had two web apps break as a result of a shared host's upgrade to PHP 5.4 and in both cases simply removing (renaming actually) the local php.ini file fixed the problem.
      • aracodex12 joined the channel
      • markin
        sweet
      • irctc566
        so that little blurb I found was the issue? Dan Pock Not fully; but it was definitely related. I believe the blurb you found was caused by the local php.ini, but the errors causing it to fail were related to the modules being messed up. This would fully explain why even the 'phpinfo' page was having issues when I had tried to set one up.
      • sakcraig joined the channel