Support » Plugin: Pronamic iDEAL » Callback Sisow failure

  • Resolved Clegg

    (@clegg)


    I use Pronamic iDeal with Gravity Forms and Sisow Advanced. As of this morning, i noticed the payment status of my orders suddenly remained “processing”. I updated to version 1.2.3. (which I hadn’t done earlier) but still the problem remains. When testing payments, after the payment I get redirected to for example “mysite.nl/?gateway=ideal_advanced&status=Success&trxid=TEST080486052051&ec=510d4b386da85&sha1=31aa326caf982ace511748ff76ad3c08b2f50bd8”, which is a blank page and nothing happens after that. I switched to a forced fixed callback for now, but I would really like to see this get fixed.

    http://wordpress.org/extend/plugins/pronamic-ideal/

Viewing 15 replies - 1 through 15 (of 25 total)
  • Clegg

    (@clegg)

    Edit: forcing a callback page doesn’t work, so all my clients are redirected to a blank page after payment. Still no idea what suddenly happend this morning :S

    Clegg

    (@clegg)

    Okey another update then. Went to the log files today the following error keeps coming up:

    [Sat Feb 02 20:18:13 2013] [error] [client xx.xxx.xxx.xxx] PHP Fatal error: Call to a member function getStatus() on a non-object in /var/www/vhosts/mysite.nl/httpdocs/wp-content/plugins/pronamic-ideal/classes/Pronamic/Gateways/IDealAdvanced/Gateway.php on line 207

    DeSlimmeShopper

    (@deslimmeshopper)

    I’m getting the same error. Anybody got an solution?

    miepiemappie

    (@miepiemappie)

    Same problem here, was working fine before and nothing has changed…

    Plugin Author Remco Tolsma

    (@remcotolsma)

    Thanks for noticing this issue, we have contacted Sisow and are waiting for an reply…

    Clegg

    (@clegg)

    What is the status on this problem, Remco. I like to have a little insight in how long this is going to take because I have to manually check payment statusses and send notification e-mails right now. Not my favourite waste of time.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    We had an reply from Sisow and are now trying to reproduce the problem.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    I can reproduce the problem, it looks like an error at Sisow. We have mail contact met Sisow to verify this.

    Clegg

    (@clegg)

    Thanks for keeping me updated, Remco.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    I just had an reply from Sisow, they will investigate the problem.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    Unfortunately still no update from Sisow, so i’ve contacted them again.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    We are getting somewhere, just got the following reply from Sisow (in Dutch):

    We hebben het probleem gevonden. Het heeft waarschijnlijk te maken met het nieuwe extended certificaat van ons. We zijn op dit moment druk bezig met het oplossen hiervan.

    Clegg

    (@clegg)

    Okey, hopefully this problem will be resolved soon.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    Just got the following reply from Sisow (in Dutch):

    Zou je het nu nogmaals willen proberen?

    I have tested it in the Sisow test modus and this is working :-).

    Clegg

    (@clegg)

    Everything seems to be working fine again Remco. Thanks!

Viewing 15 replies - 1 through 15 (of 25 total)
  • The topic ‘Callback Sisow failure’ is closed to new replies.