BACKLOG

File Manager:
Files/folder lazy loading

Improve file manager to use lazy loading functionality (to show only those elements that are visible on screen) in order to prevent long loading of the files and folders when there are a lot of files and/or sub-folders.

Once user scrolls the active area, show following elements and hide previous so browser would not be overloaded.

BACKLOG

Custom Shipping Layouts Bug

eCommerce JS should not overwrite the <options> layout entirely.
Option layout should be taken from the ’data-cms_cart_shipping_option_name_layout’ attribute that is located on the <select> tag.

If no data attribute would be found - js will use default option name layout.

Back-end:

Default layout should be improved by adding ’data-cms_cart_shipping_option_name_layout="{itemName} ({itemPrice})"’ to the select tag http://prntscr.com/tcue19

BACKLOG

3rd Party Shipping Integration:
Order States and Tracking Info Management

1) Add two system fields to the ’Order’ item in the admin (after Invoice Date http://prntscr.com/tb49jp):

• AWB Number
• Tracking URL (as an active link)

Also added to the ‘Order’ liquid object.

2) Provide ability to edit some Order details: http://prntscr.com/tb48qa

• Status Type (rename label to Status)
• Invoice Date

3) Add new admin panel page: ‘Ecommerce’ > ‘Settings’:

Move here Shopping cart life time setting from Misc settings (https://prnt.sc/sw1toc)

4) Order Statuses should be reworked:

DESIGN http://prntscr.com/u6s8kg.

Add ’Manage Statuses’ Tab to ’eCommerce’ -> ‘Shop Settings’ page

Provide Ability to Create, Update, Delete Status and change their order in the dropdown on the ’eCommerce’ -> ‘Shop Settings’ -> ’Manage Statuses Page’ (http://prntscr.com/u6s8s9)

Add/Edit contains following fields:

• Status Name (required)
• Type (not editable. For display purposes only)
  • Custom (default)
  • New
  • AwaitingPayment
  • PendingCharge
  • PaymentCanceled
  • Paid
• Workflow (multi-select)
  • Not Set (default)
  • --- list of workflows ---
• Notify Customer
  • boolean (default false)

Provide following delete logic:

• Only Statuses with Type=’Custom’ could be deleted.
• Don't show delete button and don't execute delete operation on statuses that has type other than ’Custom’

Pre-create following statuses (set all to: Workflow=Not Set, Notify Customer=False)

• New (selected when order is created)
• Awaiting Payment (selected when create order via checkout form)
• Pending Charge (selected when two step card payment successfully placed funds for the order on hold)
• Payment Canceled (selected when: admin canceled the pending charge payment, or, pending charge payment was expired and as a result was canceled)
• Success (selected when CMS retrieves a message from payment provider that payment was successfully processed)
• Payment Failed (selected when CMS retrieves a message from payment provider that payment failed)

Remap all orders with current enum statuses as follows:

• AwaitingPayment => Awaiting Payment (Type=AwaitingPayment)
• Succeed => Success (Type=Paid)
• Failed => Payment Failed (Type=PaymentFailed)
• New => New (Type=New)
  

5) Add new system email (‘Email Notifications’ > ‘System Emails’):

• ‘Order Status Changed’
• Order Status
  • dropdown of all order statuses.
  • based on the selected status, show associated ’System Email Details’ and ’Content’ fields.
  • store ’System Email Details’ and ’Content’ fields data for each Order Status separately.
  • store this set of system emails on FTP in separate folder:
    • /Content/SystemEmails/OrderStatusChanged/[[order-status-name]].html
    • each time when new custom order status will be created - create [[order-status-name]].html file
    • each time when custom order status name will be changed- changed [[order-status-name]].html file
    • apply FTP synchronization to these files (update file content will update Content field of the email)

Liquid scope for "this":

• order
• oldOrderStatus
• customer
• siteUrl

eg:
Dear {{this.customer.firstname}},
The status of your order (#{{this.order.invoiceNumber}}) has been changed from {{this.oldOrderStatus}} to {{this.order.status}}.

6) Add functionality to the order status change event:

When changed (manually or via backend flow logic) - get new status settings and

• send ’Order Status Changed’ system email if ’Notify Customer’ setting is True
• send all selected workflows that are selected in the ’Workflow’ setting (if there is a workflow selected)

BACKLOG

3rd Party Shipping Integration:
(BASE LOGIC)

1) Shop Measurements Setup

Add the following settings to the ’eCommerce’ -> Settings’.

Determines the unit of measure to be applied to the Shipping options and Products Width, Height, Depth and Weight for the calculation of shipping price.

Preset kg and cm for all sites in Database by default.

Options:

• dimension:
  • cm (default)
  • in
  • mm
  • m
  • ft
  • yd
• weight:
  • kg (default)
  • lb
  • oz
  • g

2) Shipping Option Integration Setup

Modify the shipping option Details form according to the following fields order:

• Name
• Currency / Country
• Type (new extended list)
  • User Defined
  • FedEx
  • UPS
  • USPS
  • Canada Post
  • Australia Post
  • New Zealand Post
• Tax Code
• Price

Once any type with Shipping Integration selected- hide ’Price’ fields and show additional fields specific to the selected shipping provider:

• Origin Zip/Postcode (string)
• Shipping Provider Services (dropdown)

unique fields for the particular shipping provider including api access params.
BC Example for each shipping provides:

• FedEx: http://prntscr.com/tb948g
• UPS: http://prntscr.com/tb95vr
• USPS: http://prntscr.com/tb965b
• DHL: http://prntscr.com/tb96i2
• Canada Post: no example. See API requirements and capabilities that we could provide.
• Australia Post: http://prntscr.com/tb96r4
• New Zealand Post: no example. See API requirements and capabilities that we could provide.

3) Shipping option integration on front-end UI

Design: http://prntscr.com/u6s6cf

When shipping option that has shipping provider integration is selected, show additional input field: “Destination Zip/PostCode”

• If shipping provider accepts any other additional fields that affects the cost - show them (For example: “Address is residential” field for UPS Air https://prnt.sc/talnkb, https://prnt.sc/talo94)
• Once zip is entered - request available shipping Options from the shipping provider via API and show them under ’Destination Zip/PostCode’
  (here is an example of shipping options retrieving for FedEx https://www.fedex.com/lite/lite-ship.html?locale=en_us&cntry_code=us#address)
• If there are several options available for the destination - provide the ability to choose one.
• If there are only one option available - preselect it.
• if no options available - show message "No shipping options available for this destination".
• if any error occured - show error message.

4) Shipping option display based on order rules

Shipping options that have shipping provider integration should follow the same rules as currently works for ’User Defined’ shipping options (Shipping Option -> Settings tab).

This includes:

• measurement constraints
• price constraints
• limit delivery to country
• exclude if purchase from catalogs

5) Shipping Price Calculation Rules

Once shipping provider returns the options and their prices - extract ’shippingTaxRate’, ‘shippingPrice’ based on the response data (if no tax set in the CMS the tax info will be taken from the shipping integrator if provided).

Then recalculate base shipping price by adding any ’Handling Charge’ and ’Additional Per item Handling Charge’.

And then recalculate ’shippingTaxPrice’, ‘shippingTotal’ and all other related prices like it works for ’user defined’ shipping options.

Set resulting values to the liquid object of the shopping cart.

Return to UI prices that already includes ’Handling Charge’, ’Additional Per item Handling Charge’ and ’taxPrice’. Basically the ’shippingTotal’ (https://prnt.sc/talnkb)

6) Checkout form improvement based on the shipping providers integration

Set zip code field to disabled (it is not allowed to be changed) and pre-filled by the value chosen on the shopping cart step (similar to how country is pre-selected based on the country selected on the shopping cart and not allowed to be changed).

BACKLOG

3rd Party Shipping Integration:
Liquid component tag for shipping providers additional fields

Add new component tag for "shippingProvidesFields":

{% component type:"shippingProvidesFields", collectionVariable:"", layout:"" %}

• collectionVariable (not required) - works the same way as in other modules.
• layout (not required) - path to FTP file that will contain layout content to be parsed.
  • If specified empty string - do not render anything.
  • If not specified at all - render default virtual layout.

Item context: empty

Default virtual layout:
<div data-cms_cart_shipping_provider_fields_holder></div>

BACKLOG

3rd Party Shipping Integration:
(FedEx)

Implement Shipping provider API according to BASE LOGIC API: https://www.fedex.com/en-us/developer.html

BACKLOG

3rd Party Shipping Integration:
(UPS)

Implement Shipping provider API according to BASE LOGIC API: https://www.ups.com/upsdeveloperkit?loc=en_US

BACKLOG

3rd Party Shipping Integration:
(USPS)

Implement Shipping provider API according to BASE LOGIC API: https://www.usps.com/business/web-tools-apis/documentation-updates.htm
and
https://www.usps.com/business/web-tools-apis/rate-calculator-api.pdf

BACKLOG

3rd Party Shipping Integration:
(Canada Post)

Implement Shipping provider API according to BASE LOGIC API: https://www.canadapost.ca/cpo/mc/business/productsservices/developers/services/rating/getrates/default.jsf

BACKLOG

3rd Party Shipping Integration:
(Australia Post)

Implement Shipping provider API according to BASE LOGIC API: https://developers.auspost.com.au/

BACKLOG

3rd Party Shipping Integration:
(New Zealand Post)

Implement Shipping provider API according to BASE LOGIC API:
https://www.nzpost.co.nz/business/developer-resource-centre

BACKLOG

2 Factor Auth for admin portal

1) Implement 2FA for the Treepl SSO service (Use google authenticator)

2) enable 2FA on edit account (partner portal): http://prntscr.com/u6s3zj

3) each time on login to portal or any site

• show QR code and code field on separate page after successful login (if 2FA not set up for the current user)
  http://prntscr.com/u6s4y8
• show code field on separate page after successful login (if 2FA is set up for the current user) (without QR code)

4) add ability to enable 2FA for the site on site details and show indicator on sites list

• similar checkbox setting as on edit profile
• show if 2FA is enabled for the site

5) for site admin users (if 2FA for the site is enabled) each time on login:

• show QR code and code field on separate page after successful login (if 2FA not set up for the current user)
  http://prntscr.com/u6s4y8
• show code field on separate page after successful login (if 2FA is set up for the current user) (without QR code)

BACKLOG

Replace old order.totalHtmlPrice and remove property

Replace all occurrences of ’totalHtmlPrice’ to ’totalPriceHtml’ within order or shopping cart objects in following places:

• System emails:
  • Supplier Notification
  • Invoice
  • OfflineCreditCardPayment
• Forms:
  • Checkout
• System Pages:
  • offline-credit-card-payment
  • order-receipt
  • shopping_cart

ATTENTION:

Custom includes, layouts or snippets where totalHtmlPrice has been used as part of any custom logic will not be replaced. It needs to be replaced to totalPriceHtml by the partner manually.

BACKLOG

Payment gateways:
Paypal

1) Create support for Paypal Payment gateway.

2) Gateway logic should support following flows of capturing price:

• ‘Instant payment’ (charge money right away)

Places for logic to be implemented in:

• ‘Settings’ -> ’Payment’:
  Provide ability to setup API credentials for Paypal
• Page rendering function:
  Setup auto-add Paypal payment scripts in <head> section (similar to how it's done for eway and stripe)
• Payment form submit processor:
  Setup charging process via Paypal API using token retrieved from formData

Forum Backlog: https://webinone.com/public-backlog-state/coming-next/paypal-payment-gateway

BACKLOG

Payment gateways:
Authorize.net

1) Create support for Authorize.net Payment gateway.

2) Gateway logic should support following flows of capturing price:

• ‘Instant payment’ (charge money right away)
  

Places for logic to be implemented in:

• ‘Settings’ -> ’Payment’:
  Provide ability to setup API credentials for Authorize.net
• Page rendering function:
  Setup auto-add authorize payment scripts in <head> section similar to how it's done for eway and stripe
• Payment form submit processor:
  Setup charging process via Authorize.net API using token retrieved from formData

BACKLOG

{% break %} and {% continue %} not working in liquid 2.0

Example:

{% for item in (1..10) %}
{{item}}<br>

{% if item == 6 %} THIS SHOULD BREAK HERE! <br>{% break %} {% endif %}

{% endfor %}

<br>

<hr>

<br>

{% for item in (1..10) %}

{% if item >= 6 %} THIS SHOULD CONTINUE HERE! <br>{% continue %} {% endif %}

{{item}}<br>

{% endfor %}

Expected: https://prnt.sc/s7gxh0

Actual: https://prnt.sc/s7gyj1

Source:

https://forum.treepl.co/t/bug-break-not-working-within-if-statement-in-forloop/963

BACKLOG

Add module ID/alias to the Liquid item object

Extend module item object by adding following properties:

• Module_ID
• Module_Alias

BACKLOG

Increase File Manager Upload limit

Set the maximum length of content in a request to be 300MB in the File Manager.

Update the validation message when trying to upload more than 300MB.

BACKLOG

Banner system module release and expiry date

Upgrade module settings for ’Banner’ system module so it will have ’release’ and ’expiry’ date enabled by default.

BACKLOG

Show 404 Page when file is not found

Modify CMS error handler so if URL that leads to a file (.pdf, .doc, etc.) is not found - display 404 System Page.

BACKLOG

Add invoice number column to CRM -> Order list

Add new column on the CRM > Orders page: “Invoice number”

Example: https://prnt.sc/s7h68k

BACKLOG

Download from media type

Add Download button alongside media type fields and in the File Manager:

https://drive.google.com/file/d/1GFcEG2gjC5tNrcM8F_YX3N8EbebbSQXS/view?usp=sharing

BACKLOG

Data Source for system modules extending

Allow to select module for Data Source property from the FULL list of modules (system and custom modules)

Bug

Module archive fix

Fixed ‘module_archive’ component for items that belong to the current month (previously they were skipped).

Bug

Bug from forum - not correct code for Event Group

https://forum.treepl.co/t/possible-bug-in-event-group-component/1205

Toolbox generates incorrect code for event groups. Should be like this:

{% component source: "Event group", layout: "Detail", type: "module" %}