OIOpub Forum » Wordpress  »   Bug in OIO publisher 2.07

1.) First recommendation would be to double-check all the EC payment settings. The only other person who had this problem with a recent version (and it took a long time to realise what it was) had confused their EC user ID with their EC seller ID.

2.) If you confirm all the values are correct, you may also want to check for the existence of the following code in the modules/entrecard/include/sha1.php file:

if(function_exists('sha1')) {
return sha1($str);
}

If it's not there, re-upload the entrecard module (it should be there though).

3.) If all of the above is present and correct, the final question is - what version of php are you running?

Providing the seller secret is correct too, then the values should be ok.

What about points 2 and 3?

You are welcome to a refund if you aren't satisfied, but you should remember the followng:

(a) the error is manifesting itself on the EntreCard site (the error the advertiser sent to you is from the EC site, not OIO)

(b) the majority of users are not having this problem

If this is an OIO problem, it's more likely to be an issue with the particular server the site is hosted on (because most users aren't experiencing an issue). It's almost always possible to overcome / workaround such a problem, but very difficult to forecast them.

Most established web applications you come across will have gone through at least 1 such phase, I would expect. Even the most accomplished apps like Wordpress experience issues for some users on major new releases, and a lot of it is down to code compatibility in the multitude of environments it is used on.

-------

I just went about creating a test purchase so you can see the error for yourself on the EC site. I'd definitely recommend double-checking the "seller secret" given to you by EC, if you haven't already. I'm also trying to find out from EC what that error actually covers, as it isn't very explicit:

http://gregorymathews.com/wp-content/plugins/oiopub-direct/payment.php?rand=b-Ydg8qmZCJu

I remembered that I had the FTP details from the other problem you experienced. I did some testing, and tracked down the cause of the issue, which I've sent on to Richard at EC.

Here's a copy of the email I sent, so you can see the exact cause. There's not much I can do yet until I get a suggestion / solution from EC, since the fault would seem to be on their side:

NB: if you were to change your zone description to get rid of the full stop, it would fix the problem for that particular case, although I'm more interested in a universal solution for developers.

-------

Email Copy:

1.) The following code is used to urlencode a description for EC:

$params .= "description=" . urlencode($item['type'] . " at " . $oiopub_set->site_url) . "&";

2.) The user in this instance had a description which when urlencoded, reads:

description=Banner+Ad%2C+125x125+badge+on+left+of+gregorymathews.com+at+http%3A%2F%2Fgregorymathews.com&

After some testing, I narrowed it down to one character in the description. The EC payment gateway seems to choke on the full stop in gregorymathews.com - I'm not sure what the cause of the error is, but it would be good if you could come up with a solution on your end to make it compatible with full stops (it will also make sure other developers don't come up against similar problems where the solution isn't obvious).

This one should work for you:

http://gregorymathews.com/wp-content/plugins/oiopub-direct/payment.php?rand=b-1QUcA2BNAm

Not sure what is going on with the EC error messages, but it seems that certain combinations of characters (eg .com) stop the process dead. I've tried to minimise the chances of the error occurring when using OIO.