A couple of things...

[aloebridge123]

Receipt Page
Having run a few test orders I notice that my receipt page looks bland and boring - how can I amend this to reflect the site.

I've opened Act_Reciptprimary.html in Dreamweaver but everything appears 'hidden' making it difficult to amend...

Any help much appreciated.

Prob 2 - I know you'll not like it Google Checkout.
Now I know there is no full integration at this stage - however I was following brightlight's workaround (as i'll be happy with that for the moment)
I've updated both of the files as advised - and attached them below but I received the following error when placing a test order:

"Error executing the on-line credit card plug-in script. syntax error at (eval 42) line 158, at EOF"

Any ideas on what I need to change to get it working?

Thanks in Advance..
www.youraloestore.co.uk

<!-- Template for Netbanx OCC HTML template --> 
</FORM><!-- Terminate the parent template form --> 


<form name="formOCC" method="POST" action="https://checkout.google.com/cws/v2/Merchant/XXXXXXXX/checkoutForm" accept-charset="utf-8"> 

NETQUOTEVAR:OCC_VALUES 

</form> 

<FORM METHOD=POST ACTION="NETQUOTEVAR:OCC_URL"><!-- Create a bogus form to keep the parent template happy --> 
<!-- End of template for Netbanx OCC -->

# This script is called by an eval() function and it will already 
# have the following variables set up: 
# 
#    Expects:        $::sOrderNumber        - the alphanumeric order number for this order 
#                    $::nOrderTotal            - the total for this order (stored in based currency format e.g. 1000 = $10.00) 
#                    %::PriceFormatBlob   - the price format data 
#                    %::InvoiceContact        - the customer invoice contact information 
#                    $::sCallBackURLAuth    - the URL of the authorization callback script 
#                    $::sCallBackURLBack    - the URL of the backup script 
#                    $::sCallBackURLUser    - the URL of the receipt script 
#                    $::sPath                    - the path to the Catalog directory 
#                    $::sWebSiteUrl            - the Catalog web site URL 
#                    $::sContentUrl            - the content URL 
# 
#    Affects:        $::eStatus             - the status of the transaction: 
#                        $::FAILURE     - Failure 
#                        $::ACCEPTED - Accepted 
#                        $::REJECTED - Rejected 
#                        $::PENDING  - Pending 
#                    $::sErrorMessage        - error message if any 
#                    $::sHTML                    - the HTML to display 
# 
#  $Revision: 1 $ 
# 
#--------------------------------------------------------------- 

use strict; 

$::eStatus = $::PENDING;                                # The OCC plug-in runs in pending mode.  This script does not 
                                                                # perform the transaction.  Rather, it forwards the customer to 
                                                                # the OCC site for completion. 
my (%VarTable); 

## Shared Script, different HTML templates; 

$VarTable{$::VARPREFIX . 'OCC_URL'} =                # insert the OCC web site URL into the HTML template 
    $sProcessScriptURL; 
# 
# build up a string of all of the values that must be passed to OCC 
# 


# 
# amount is translated to decimal places 
# 
my $nNumDigits = $::PriceFormatBlob{"ICURRDIGITS"};    # read the currency format values 
my ($nAmount, $nFactor, $sAmount); 
if(defined $nNumDigits) 
    { 
    $nFactor = (10 ** $nNumDigits); 
    } 
else 
    { 
    $nFactor = 100; 
    } 
$sAmount = sprintf("%d.%02d", $::nOrderTotal / $nFactor, $::nOrderTotal % $nFactor); 



my $sHiddenValues; 
$sHiddenValues .= "<input type=\"hidden\" name=\"ordernumber\" value=\"" . $::sOrderNumber . "\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"item_name_1\" value=\"Aloe Products\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"item_description_1\" value=\"Your Aloe Store\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"item_quantity_1\" value=\"1\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"item_price_1\" value=\"" . $sAmount . "\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"item_currency_1\" value=\"GBP\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"_charset_\">\n"; 
$sHiddenValues .= "<input type=\"hidden\" name=\"checkout-flow-support.merchant-checkout-flow-support.continue-shopping-url\" value=\"https://www.tv-wall-brackets.co.uk/cgi-bin/os000003.pl?SEQUENCE=3&ACTION=Finish&ORDERNUMBER=$::sOrderNumber\">\n"; 


# 

if (!$bAuthorize)                                            # if in pre-authorize mode, set the flag 
    { 

    } 

if ($bTestMode)                                            # only include the test mode flag if it is on 
    { 
    $sHiddenValues .= "<input type=HIDDEN NAME=\"TESTMODE\" value=\"1\">\n"; 
    } 
# 

$VarTable{$::VARPREFIX . 'OCC_VALUES'} =            # add the OCC values to the template 
    $sHiddenValues; 

my $sLinkHTML = 'occlink.html'; 
if(defined $::g_pPaymentList) 
    { 
    $sLinkHTML = $$::g_pPaymentList{ActinicOrder::PaymentStringToEnum($::g_PaymentInfo{'METHOD'})}{BOUNCE_HTML}; 
    } 
@Response = ACTINIC::TemplateFile($::sPath . $sLinkHTML, %VarTable); # build the file 

if ($Response[0] != $::SUCCESS) 
    { 
    $::eStatus = $::FAILURE;                            # return a plug-in error 
    $::sErrorMessage = $Response[1]; 
    return ($::SUCCESS);                                    # always return success if the script runs 
    } 

@Response = ACTINIC::MakeLinksAbsolute($Response[2], $::sWebSiteUrl, $::sContentUrl); 
if ($Response[0] != $::SUCCESS) 
    { 
    $::eStatus = $::FAILURE;                            # return a plug-in error 
    $::sErrorMessage = $Response[1]; 
    return ($::SUCCESS);                                    # always return success if the script runs 
    } 

$::sHTML = $Response[2];                                # grab the resulting HTML 
# 
# process the test mode warning 
# 
my ($sDelimiter) = $::DELPREFIX . 'TESTMODE'; 
if ($bTestMode)                                            # only include the test mode block if we are in test mode 
    { 
    $::sHTML =~ s/$sDelimiter//g;                        # remove the delimiter text 
    } 
else                                                            # not in test mode - remove the block 
    { 
    $::sHTML =~ s/$sDelimiter(.*?)$sDelimiter//gs;    # remove the test mode warning blob (/s removes the \n limitation of .) 
    } 

return ($::SUCCESS); 

# 
# End of OCCScriptTemplate.pl 
# 

Note this is the HTML API integration, not the XML API integration.

[TraceyG]

Hi,

Having run a few test orders I notice that my receipt page looks bland and boring

This is mainly to make it into a printable page for customers who don't want to waste ink on printing irrelevant information and images etc.

I've opened Act_Reciptprimary.html in Dreamweaver but everything appears 'hidden' making it difficult to amend...

Act_ReceiptPrimary.html only contains the HTML for the surrounding area of the receipt page. With the Dreamweaver Integration in v7 you have to generate the pages offline and then copy and paste the offline url into Dreamweaver to view the page, however, because the receipt page is generated by perl files you won't be able to do this as you can't run perl offline.

Your best bet would be to make a copy of your current Act_Primary.html file and use the copy for your receipt page. You can then strip out the bits of HTML that you don't want to be included on the receipt page. To include a new layout as a primary template you will have to add the new layout to the 'PrimaryTemplates.ini' file found in your site folder. You can then select it via 'Design | Options | Layouts | Receipt Page Layout | Select button'.

Prob 2 - I know you'll not like it Google Checkout.

I'm afraid that I can't help you with this but maybe someone else who has implemented it can give you some pointers.

[aloebridge123]

Thanks Tracey - I'll have a go at adapting the receipt page.

With regards to the other question re google - anyone else able to help?

[RuralWeb]

With regards to the other question re google - anyone else able to help

It has been done and the instructions posted on the forum about 2 years ago

[aloebridge123]

I was following brightlight's workaround (as i'll be happy with that for the moment)
I've updated both of the files as advised - and attached them below but I received the following error when placing a test order:

"Error executing the on-line credit card plug-in script. syntax error at (eval 42) line 158, at EOF"

Hi,

Thanks for your response, but i followed the work around and received the above error message when I tried to implement it and just wondered if anyone could shed any light on it?

Regards
www.youraloestore.co.uk