[eluser]Ajaxboy[/eluser]
So in conclusion, as it is apparent when you include ajax.php - then in line 46 it handles over the job to ajaxfw.php, but it seems that it wasn't doing that and was passing that point hence producing that behavior, so that is why using 'ajaxfw.php' fixes the issue. In previous versions of Cjax you would of always use 'ajaxfw.php' but then to make it easier use was added the ability to use 'ajax.php' and here is where this originates, if you included 'ajax.php' in previous versions of cjax, you would of gotten that issue anyways. I'll see if more checks can be added to prevent this behavior.
