After a bit of debugging it turns out the problem stems from the paypoint-secpay merger and the fact that OSCommerce is a poorly supported hunk of junk.

During a typical transaction paypoint will ask the user for their card details, and if the details check out it sends a request back to OSCommerce telling it that the transaction was a success.  It will then display to the user whatever your server outputs.  Thus your customers should see the “Thank you for your order” page appear under a url of “https://www.secpay.com/java-bin/ValCard”.

When oscommerce receives the “the transaction succeeded” message from secpay it looks at the ip address the message came from, and tries to resolve it to a hostname to see if it came from secpay.com.

Since the merger the ip address that paypoint are using (in this case it was 81.93.226.30) doesn’t resolve to secpay.com, in fact it doesn’t resolve to anything.  If php can’t resolve an ip address to a hostname then it gives up and returns the ip, thus oscommerce was trying to check that ‘secpay.com’ was the same as ’81.93.226.30′, which it isn’t.

To fix this I changed the before_process() method in the secpay payment module to look like so:

function before_process() {

      if ($_POST['valid'] == 'true') {
          if ($remote_addr = $_SERVER['REMOTE_ADDR']) {
	      // Check that the request came from one of the secpay / paypoint servers
    	      if (strpos($remote_addr, '81.93.226') !== 0) {
        	    tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $HTTP_POST_VARS[tep_session_name()] . '&payment_error=' . $this->code, 'SSL', false, false));
          }
        } else {
          tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $HTTP_POST_VARS[tep_session_name()] . '&payment_error=' . $this->code, 'SSL', false, false));
        }
      }
    }

Ignoring for a second the horrible use of php3/php4 conventions, the method now checks to see if the sender’s ip address begins with 81.93.226, as paypoint seem to own that range.

Hopefully this will save someone else the headache

jQuery.fn.limitMaxlength = function(options){

	var settings = jQuery.extend({
		attribute: "maxlength",
		onLimit: function(){},
		onEdit: function(){}
	}, options);

	// Event handler to limit the textarea
	var onEdit = function(){
		var textarea = jQuery(this);
		var maxlength = parseInt(textarea.attr(settings.attribute));

		if(textarea.val().length > maxlength){
			textarea.val(textarea.val().substr(0, maxlength));

			// Call the onlimit handler within the scope of the textarea
			jQuery.proxy(settings.onLimit, this)();
		}

		// Call the onEdit handler within the scope of the textarea
		jQuery.proxy(settings.onEdit, this)(maxlength - textarea.val().length);
	}

	this.each(onEdit);

	return this.keyup(onEdit)
				.keydown(onEdit)
				.focus(onEdit)
				.live('input paste', onEdit);
}

And here’s an example of it in use, limiting all textareas in the document and updating a p element with the id of charsRemaining with… the number of characters remaining. It also sets the textarea bg color to red when the user tries to exceed the maxlength.

$(document).ready(function(){

	var onEditCallback = function(remaining){
		$(this).siblings('.charsRemaining').text("Characters remaining: " + remaining);

		if(remaining > 0){
			$(this).css('background-color', 'white');
		}
	}

	var onLimitCallback = function(){
		$(this).css('background-color', 'red');
	}

	$('textarea[maxlength]').limitMaxlength({
		onEdit: onEditCallback,
		onLimit: onLimitCallback
	});
});

And here’s a jsbin paste with a quick demo. Although there is a lot more code in this version it’s a lot more flexible as it allows you to decide how to inform the user of how many characters there’re remaining. It also means that it’ll take any characters already in the textbox into account when the document loads.

Update 2010/04/09: Fixed a few bugs & typos
Update 2010/08/01: Removed problematic comma & added live(‘input paste’) – thanks Surya and Len!

Up until recently Kohana3 was using a home-grown module for unit testing – It was ok, but lacked some of the more advanced features of independent testing suites – however now the project has now adopted PHPUnit as its official test framework!  PHPUnit is one of the more popular testing suites for PHP, it has full support for Fixtures, Mock Objects, Code Coverage and a lot of other cool stuff.

The module only requires a few changes to the bootstrap in order to integrate Kohana with PHPUnit, and afterwards you can run tests from the cli, IDE or our custom web runner.  All available tests are loaded from Kohana’s cascading filesystem and can be filtered using PHPUnit’s –group switch.

Go and git it while it’s hot!

For example – Say I want to change the Controller class so that it initiates the session in the constructor (It might be better to initiate the session in a hook of some kind, but it serves as a decent example here).

The default controller class is stored in

system/libraries/Controller.php

To extend it I simply create the following file:

application/libraries/MY_Controller.php

And then I can simply create a class like so:

[sourcecode language="php"]

Class Controller extends Controller_Core
{
function __construct()
{
parent::__construct();

//Init Session
Session::instance();
}
}
[/sourcecode]

And the class is extended!

Best of all, because Kohana allows you to transparently extend files all of your controllers which extend Controller will automatically use your modifications as well as the system's version of Controller.

note – you can only really extend a library once. There are ways to get around this restriction, but it’s not really worth it.

You could also totally override the class by making a file called

application/libraries/Controller.php

In which you’d place
[sourcecode language="php"]

Class Controller_Core
{
function __construct()
{
parent::__construct();

//Init Session
Session::instance();
}
}
[/sourcecode]

If you do replace a core library, then make sure that you either remove all references to parts of the controller which are no longer available, or that you copy across the changes.

There are lots more tutorials available at http://learn.kohanaphp.com

Anyway, there’s much more cool stuff that kohana can do, so I’d deffinitely reccomend you give it a try

Alex

P.S. Did I mention it’s free?

There’s an updated version of this script here

Save this snippet in a js file:

$(document).ready(function(){
	$('textarea[maxlength]').keyup(function(){
		var max = parseInt($(this).attr(’maxlength’));
		if($(this).val().length > max){
			$(this).val($(this).val().substr(0, $(this).attr('maxlength')));
		}

		$(this).parent().find('.charsRemaining').html('You have ' + (max - $(this).val().length) + ' characters remaining');
	});
});

Just download and include jquery like so:

And then include the js file containing the above snippet

Then, to limit a textarea do this:

If you want to show the user the ‘You have x characters remaining’ message, then append an element with the ‘charsRemaining’ class, like so:

You have 255 characters remaining

You have to make sure that the p and textarea elements share the same parent, else the message won’t be updated.

Alex

UPDATE: Thanks for the parseInt() tip Jason
There’s an updated version of this script here