Retweeting private Tweets

So now that you are part of the “VIP” crowd and you are one of those special friends that is allowed to see your friend’s private tweets, let me ask you. Is it acceptable for you to ReTweet something that is has been marked as private? After all it was private to start with but at the same time it could be some nice piece of information that you want to share with the word and you want to give credit to your friend.

It is as easy as writing “RE” in front of your ReTweet you are passing along or putting a (via @fancyNameGoesHere) at the end of it and it is again out in the open and the “privacy” is out of the window.

So I say, think accordingly before you ReTweet those private Tweets.

YourPay some common errors and solutions

When working with YourPay service there some small issues you might run into and so I can remember in the future I am listing them here.

Fraud issue

If hit the server several times for testing you might be tempted to hit it with the same amount but remember that even though for you they are different hits, the store is receiving the same “client” hit so they will reject you request by marking it as a fraud.

Fraud Solution

Hit the server with different totals, even a minimum of 1 cent in difference between transactions is enough for you to get successful transactions with the store.

Store not able to process orders

One common issue is that when you hit the server from a page that is not registered with the application, YourPay will not recognize your store request and thus reject your request and it will break the whole experience.

Store not able to process orders solution

Always remember to change the location where YourPay is expecting your request, this could be easily forgotten when you are testing from different points on your servers or you are testing from Dev and then move everything to production.

Getting UPS Rates with PHP fixing small issue

There is an great class in Google Code written in PHP that works as a wrapper to the UPS API, I started using it about a year ago and never had issues with it since I was using it with Flash/AMFPHP/PHP, but now that I am working with a new shopping cart where I need this functionality but the front end is PHP only, I noticed that I was starting to get the following error:

[php]Parse error: syntax error, unexpected $end in path…/UPSRate.php(131) : eval()’d code on line 1[php]

After investigating the issue further I was able to fix the issue by only using eval on those elements where ‘value’ wasn’t undefined.

[php]if (isset($xml_elem[‘value’])) {
$php_stmt .= ‘[$xml_elem[\’tag\’]] = $xml_elem[\’value\’];’;

Notice that these parse errors do not break the application and that is why they weren’t raising a flag in Flash but working on PHP alone we have to squash all these kind of warnings.