Admin Considerations
Once you've installed the plugin, an additional item is available in your admin's Configuration menu: One-Page Checkout Settings. The following settings are available:
| Name | Description | Version Added |
|---|---|---|
| Version/Release Date | This display-only field shows the plugin's current version and release date. | 1.0.0 |
| Enable One-Page Checkout? | Choose true to enable for all customers, false to disable (default) or conditional to enable the processing only for customers identified by Enable: Customer List. | 1.0.0 |
| Enable: Customer List | When you conditionally enable the plugin, use this setting to limit the customers for which the plugin is enabled. Leave the setting blank (the default) to disable the plugin for all customers or identify a comma-separated list of customer_id values for whom the plugin is to be enabled. Note: Starting with OPC v2.1.0, intervening blanks are allowed. | 1.1.0 |
| Update Shipping AJAX Time-out | Use this setting to adjust the timeout to use when the plugin requests an update to the shipping quotes on the "checkout_one" page. The default setting of 5000 (5 seconds) should work for most stores. If your store has enabled multiple external shipping modules (e.g. USPS, UPS and FedEx), you might need to increase this value. | 1.0.3 |
|
|
||
| Enable Shipping=Billing? | When enabled, the "checkout_one" page presents the customer with a checkbox-input to indicate that their shipping and billing addresses are the same. If you don't want that control to be shown, i.e. the billing and shipping addresses are both always displayed, set the value to false. | 1.3.0 |
ot_total). The value defaults to #ottotal > div:first-child, the selector value for the built-in responsive_classic and template_default templates. |
|
|
| Payment Methods Requiring Confirmation | There are some payment methods that require the confirmation page to be displayed for their proper operation. You can add to that comma-separated list any of the payment methods used on your store for which you'd like the customer to confirm. Starting with OPC v2.1.0, intervening blanks are allowed; starting with OPC v2.4.2, you can add credit_covers to this list to ensure that orders that are fully paid using a Gift Certificate or coupon also require confirmation. |
1.3.0 |
| Payment Methods Handling Form Submittal | There are some payment methods that handle the checkout form's submittal themselves, e.g. square_webPay. Identify those payment methods here, using a comma-separated list (intervening blanks are OK). |
2.4.0 |
| Load Minified Script Files? | Should the plugin load the minified version of its jQuery scripts, reducing the page-load time for the checkout_one page? Default: true. |
1.5.0 |
| Order Status: Slamming Control | Identify the number of back-to-back errors that your store allows when a customer is checking an order's status via the order_status page (default: 3). When the customer has reached that threshold, they will be redirected to the time_out page. |
2.0.0 |
| Login-Page Layout | When you enable the plugin's Guest Checkout and/or Account Registration, an alternate formatting of the storefront login page is displayed. Use this setting to control the 3-column layout of that modified page. The value is an encoded string, identifying which block(s) should be displayed in which column. Columns are delimited by a semi-colon (;) and the top-to-bottom column layout is in the order specified by the block-elements' left-to-right order. See below for details. |
2.0.0 |
| Enable Guest Checkout? | When enabled (i.e. set to true), customers can checkout without creating an account using the OPC's guest checkout. Note that the overall One-Page Checkout must also be enabled! | 2.0.0 |
| Guest Checkout: Require Email Confirmation? | When a guest checks out, are they required to confirm their email address? Default: true. | 2.0.0 |
| Guest Checkout: Pages Allowed Post-Checkout | Identify (using a comma-separated list, intervening blanks are OK) the pages that are allowed once a guest has completed their checkout. When the guest navigates from the checkout_success page to any page not in this list, their guest-customer session is reset. For example, if your store provides a pop-up print invoice, you would include the name of that page in this list. Default: download. Note: The default for this setting was blank (i.e. '') for OPC versions prior to v2.0.4. |
2.0.0 |
| Guest Checkout: Disallowed Pages | Identify (using a comma-separated list, intervening blanks are OK) the pages that are disallowed during guest-checkout. These pages normally require a logged-in customer prior to display, e.g. account. Do not include the login, create_account or logoff pages in this list! Default: account, account_edit, account_history, account_history_info, account_newsletters, account_notifications, account_password, address_book, address_book_process, create_account_success, gv_redeem, gv_send, password_forgotten, product_reviews_write, unsubscribe. |
2.0.0 |
| Guest Checkout: Disallowed Credit Class Order-Totals | Identify (using a comma-separated list, intervening blanks are OK) any credit-class order-totals that are disallowed during guest-checkout. These order-totals normally require a customer-account for their processing, e.g. ot_gv, the default value. Note: Starting with OPC v2.1.0, intervening blanks are allowed. |
2.0.0 |
| Guest Checkout: Disallowed Payment Methods | Identify (using a comma-separated list, intervening blanks are OK) any payment methods that are disallowed during guest-checkout. These payment methods normally have no validation of purchase — e.g. moneyorder and cod — and can, if left enabled, result in unwanted spam purchases. Default: moneyorder, cod. Note: Starting with OPC v2.1.0, intervening blanks are allowed. |
2.0.0 |
| Enable Account Registration? | Do you want your store's create_account processing to create a registered rather than a full account? Default: false. |
2.0.0 |
| Registered Accounts: Telephone Minimum Length | When a customer creates a registered account, is a telephone number required? If so, enter the minimum length of the telephone number; use 0 to indicate the the telephone number is optional. | 2.6.0 |
| Enable One-Page Checkout Debug? | When enabled, debug files named one_page_checkout-xx-YYYY-mm-dd.log are created in your /logs sub-directory, where xx is the customer_id for the checkout and YYYY-mm-dd is the date associated with the information. Use the true or full settings in combination with the Debug: Customer List setting to limit the customers for which the debug-action is taken. Setting the value to full will also set the PHP error-level for the checkout_one page's processing so that all PHP errors are logged. |
1.0.0 |
| Debug: Customer List | When you enable the plugin's debug, use this setting to limit the customers for which the debug-logs are generated. Leave the setting blank (the default) to debug all customers or identify a comma-separated list of customer_id values to limit the debug to just those customers. | 1.0.0 |
This configuration setting provides the following choices:
no-update if at least one of your store's payment methods require that no update be performed, e.g. square.update if none of your store's payment methods require no-update.refresh if your store has a combination of payment-method requirements, some which require no-update and some that don't. Note that choosing this method will result in any customer-entered credit-card information being reset if the order's shipping-method is changed.
If your store has the square module installed on an OPC installation or upgrade, this setting will default to no-update; otherwise, the default value will be update.
The block elements for this configuration setting are:
- L ... (required) The email/password login block.
- P ... (optional) The PayPal Express Checkout shortcut-button block.
- G ... (required) The guest-checkout block.
- C ... (required) The create-account block.
- B ... (optional) The "Account Benefits" block.
Default: L;P,G,C;B. See this additional-documentation page for details.
There are also a couple of constants present in the plugin's language file (/includes/languages/english/checkout_one.php) that you can use to control the checkout_one page's display. Each of these values are an empty string (i.e. no display produced) as-shipped by the plugin.
-
TEXT_CHECKOUT_ONE_TOP_INSTRUCTIONS. This constant, echoed within a
<p>tag, defines any upper-page instructions you might want to give to your customers. -
TEXT_CHECKOUT_ONE_INSTRUCTIONS. This constant, echoed within a
ptag within a<fieldset>tag, defines any lower-page instructions just above the form's submit button. -
TEXT_CHECKOUT_ONE_INSTRUCTION_LABEL. Defines the value to be used in the fieldset's
<legend>tag; if the value is set as '', no legend is generated.
The checkout_one_confirmation page's language file also has an instructional constant that you can use to customize your customers' experience: CHECKOUT_ONE_CONFIRMATION_INSTRUCTIONS. These instructions are displayed just before the page's progress-spinner and should be supplied if your store requires additional time to process.
Note: If you're going to change those constants, be sure to make a template-override copy of the plugin's as-shipped language file so the file isn't mistakenly overwritten on an update to the plugin!
The One-Page Checkout admin observer class provides updates to the admin's Customers :: Orders page's orders' listing. At the very top of the listing, the Legend is updated to identify the guest-placed icon:
and each guest-placed order is shown with that icon:
