[TYPO3-shop] handleScript

John Nicholas J_nicholas at excite.com
Wed Nov 19 22:11:30 CET 2008


Additionally the only thing I can tell that effects how the next page 
loads is the submit button in the template as

<input type="Submit" name="products_customized_payment" value="Pay / 
Order" onClick="document.forms[0].action='###FORM_URL_FINALIZE###';">

which renders in the output as

<input type="Submit" name="products_customized_payment" value="Pay / 
Order"onClick="document.forms[0].action='store/cart.html?tx_ttproducts_pi1%5BbackPID%5D=21&amp;cHash=c5503959c5';">

I tried changing name="products_customized_payment" to a few other 
values like "products_payment" based on what _control is looking for but 
that just made it loop back to the first page of the checkout.

John Nicholas wrote:
> This doesn't really address my question. The issue isn't authorize.net 
> related. The question is why setting any content in $content isn't 
> displayed or otherwise effects what happens when a person hits the next 
> button even though die() commands show that the code is being run.
> 
> if the handlescript $content value isn't meant to be displayed (which 
> appears to be the case in the old DIBs example and the 2checkout 
> example) what is it meant to be in there. If it isn't related to the 
> $content variables contents, what else effects how this is processed?
> 
> Franz Holzinger wrote:
>> John Nicholas a écrit :
>>> Please help me clarify how handleScript works.
>>>
>>> It looks to me like if a handleScript is defined in typoscript the 
>>> processPayment method of class.tt_products_control.php this line is 
>>> called
>>
>> Try to understand handlescript_2checkout first. This is known to be 
>> working. I do not know if authorize-net does or needs modifications. 
>> Maybe you can adapt the code like the other extension.
>>
>> - Franz
>>
>>
>>
>>


More information about the TYPO3-project-tt-products mailing list