TYPO3 Mailingliste: nicht fragen - lesen!

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

$content.= $this->paymentshipping->includeHandleScript($handleScript,
$this->basket->basketExtra['payment.']['handleScript.'],
$this->conf['paymentActivity'], $bFinalize);

which should get to this function in

function includeHandleScript($handleScript, &$confScript, $activity,
&$bFinalize) {
$content = '';
include($handleScript);
return $content;
}

which basically puts my handlescript inline. if I put a die("In the
handle script!") that text will be displayed. I can also run some code i
there. for example:

$localTemplateCode = $this->pibase->cObj->fileResource(
'EXT:tt_products/template/payment_Authorize_template.tmpl'); // Fetches
the Authorize.net template file
$localTemplateCode =
$this->pibase->cObj->substituteMarkerArrayCached($localTemplateCode,
$this->pibase->globalMarkerArray);
die($localTemplateCode)

will display the template code. since the includeHandleScript function
just returns content. I would assume that I generate a form or run the
authorization and put the results in $content. anything besides the
die() just goes to the finalize page.

After a few days of experimenting I have no idea what to do next.
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

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




_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

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
>
>
>
>
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

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;cH ash=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
>>
>>
>>
>>
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

John Nicholas a écrit :
> 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.

You must put the marker ###MESSAGE_PAYMENT_SCRIPT### into your Shop HTML
template.
Set the paymentActivity to payment or finalize.

> 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?

$content is meant to be displayed. It is the output of the payment
script. Or it can even redirect to the gateway and will hopefully come
back to the shop later again.
This script must fill in the $bFinalize parameter with TRUE, if the shop
shall do the finalization.

- Franz





_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

John Nicholas a écrit :
> 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;cH ash=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.

products_customized_payment is needed if the gateway needs an
intermediate step before or after entering of the credit card data.

This is the activity which will be done by the shop on the next step.

- Franz



_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

Currently I my handleScript does connect successfully to authorize.net
by using products_customized_payment and by setting paymentActivity to
customized. No other variations seem to actually run the handleScript code.

This leaves the finalize step of closing out the cart and sending the
emails. I have tried setting $bFinalize = true with no effect.
The DIBS and 2Checkout examples see to use $this->order->finalize or
$this->pibase->order->finalize for this but I don't see an effect from
that either.

One thing I might need to note is that nothing is being rendered at
authorize.net. My handlescript simply connects to them and uses the
result to render and error message or success message. I just need the
success message to trigger the the finalize step instead

Franz Holzinger wrote:
> John Nicholas a écrit :
>> 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;cH ash=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.
>
> products_customized_payment is needed if the gateway needs an
> intermediate step before or after entering of the credit card data.
>
> This is the activity which will be done by the shop on the next step.
>
> - Franz
>
>
>
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

What is ###MESSAGE_PAYMENT_SCRIPT### and what is it supposed to do?
Where does it go? I found one message saying it should be in
BASKET_ORDERCONFIRMATION_TEMPLATE but that is the page that I seem to be
unable to get to from my handleScript so it doesn't seem to be part of
my problem.

What is the relationship between paymentActivity in typoscript and
setting the form submit between products_customized_payment and
products_payment? From what I've seen so far, only
products_customized_payment will actually run the handleScript code but
then it will only render $content from there. Setting $bFinalize=true
looks like it should then run the finalize code but this doesn't seem to
happen.


Franz Holzinger wrote:
> John Nicholas a écrit :
>> 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.
>
> You must put the marker ###MESSAGE_PAYMENT_SCRIPT### into your Shop HTML
> template.
> Set the paymentActivity to payment or finalize.
>
>> 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?
>
> $content is meant to be displayed. It is the output of the payment
> script. Or it can even redirect to the gateway and will hopefully come
> back to the shop later again.
> This script must fill in the $bFinalize parameter with TRUE, if the shop
> shall do the finalization.
>
> - Franz
>
>
>
>
>
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products