BACKLOG

Agency Plan:
Payment + Site activation steps on site

1) Portal settings - ability to allow direct billing and site activation

In Treepl Portal on ‘Edit Site’ page add new setting: “Allow Activation on the site”

2) Billing from the admin

Add Billing button to the "gear" menu

Design

Show it only if ”Allow Activation on the site” is TRUE and the site is not paid yet

Once clicked show Billing page

Design

Link to terms and conditions:

https://treepl.co/terms-of-service

Allow user to pay for the site activation (validate the terms and conditions checkbox is checked).

Once paid - set return URL to lead to the ’Settings’ -> ‘Domains’ (1st step of the activation).

3) Domain Activation Steps

Add domain activation steps to the ’Settings’ -> ‘Domains’ page

Design:

https://invis.io/QSYWMTYD4W6

Add ability to:

• Go through all activation steps (similar to how it's already done in the portal)
• add new domain (replicate same steps as on the portal)
• change primary domain (add indicator on the domains list)
  • When clicking change domain show confirm popup ”Current domain settings will be reset. Are you sure you want to continue?”
• change domain name (Design)
• delete domain (add this function to the portal as well) [deleted domain should be able to be added back]

BACKLOG

Agency Plan:
Custom logo for individual site

1) Add Custom branding menu

Add menu item to the "Gear" menu (if current admin has role lower then agency - display menu item as disabled)

Design:

Design

2) Add Custom Branding Page

• allow to change all branding options that Partner can do in the portal
• allow to reset custom site assets (show warning popup: “Are you sure you want to reset custom branding?”
• if current admin has role lower then Agency - do not allow to open this page

Design:

Design

3) Custom Branding functionality

Change branding assets displaying logic (on login, reset password screens etc) as follows:

• try show custom logo or background image that was set for the current site
• if not found - try show custom logo or background image that was set in the portal for all sites of the current Reseller (Partner or Agency)
• if not found - show default Treepl assets

BACKLOG

Agency Plan:
Portal users

1) Add ability to invite staff to Agency user portal (portal users)

DESIGN

https://invis.io/N3YUAKE28BK

Invited user should be able to perform any action that the agency user can except for:

• Delete sites
• See ’Portal Users’ tab and invite other Portal users

Invite process should be similar to admin users invite in the CMS (create user if not exist or just invite already existed)

• if user is already invited to any agency user portal then show error message: “This user is already invited as Portal users to another Agency.”
• if user is already exist in the identity server and has role:
  • Admin user
    • force rewrite there role to Portal user
    • once they will try to login to any site where they are already marked as admin - remove that mark and release admin slot for that site
  • Any other role
    show error message: “This user couldn't be invited as Portal user.”
• send Invite email

Text for ? icon near INVITE NEW USER button: “Portal users would have same privileges that your account has except of ability to delete sites and invite new Portal users”

2) Add lazy create process on CMS sites

When Portal user passes login/verification process (via SSO) to the site that belongs to the Agency of the Portal user - add this Portal user to the DB if it's not exited there yet.

3) Portal user influence to admin users UI and restrictions

Portal user should:

• not be visible in admin users
• not take slot of admin users
• have same permissions as their Agency

BACKLOG

Agency Plan:
Functionality to store and share Modules (for Agency)

1) Implement new share module functionality

DESIGN:

https://invis.io/RAYV4SIEFGP

Show ‘Export’ button on edit module -> Settings page (see design).

Show ‘Import’ button on create new module page (in the same place as ‘Export’ button on design).

When clicking ’Export’:

• Download json file with module settings (described in Import/Export logic part of the task)

When clicking ’Import’:

• Upload file and verify that module (or each module of parent-child module linkage) doesn't have conflicts between already existed module aliases
• If conflicts found show popup:
  • When only one conflict found: “Module with name "[ModuleName]" is already exists on the site.
    Paste new name for module or click cancel.
    "[ModuleName]": [input for name]
    OK | Cancel
  • When conflicts found in both parent and child module names: “Modules with names "[ParentModuleName]" and "[ChildModuleName]" are already exist on the site.
    Paste new names for modules or click cancel.
    "[ParentModuleName]": [input for name]
    "[ChildModuleName]": [input for name]
    OK | Cancel
  • Validate that new names do not conflict with any already existed modules in the CMS via JS (OK button is disabled until there will be no conflicts) as well as via backend (show same popup once again if JS passed the validation but module was created between the time popup displaying and new names confirmation submit).
• If no conflicts found - perform Import logic
• Show loader while module is creating

2) Implement Import/Export logic

Export:

• Extract all module settings
  • Settings tab (with assigned workflow Names)
  • Properties tab
  • Layouts tab
  • Table tab
• If module has parent-child linkage
  • extract both module settings (extract child module first)
• If module has Datasource fields
  • save datasource module alias as reference in the property settings
  • Extract datasource module settings as well
  • if any property module also has datasource:
    • if datasource module is not added to the export repeat current step for it as well
    • else - skip datasource
  • if datasource module also has parent-child linkage
    • extract that linkage also

Import:

If file could not be parsed show error: “File is not valid for import process”.

Else:

• Go for each module that is stored in the file
  • Try create module (by ’Settings’ tab data)
    • if site already have module with the same alias as module from export skip module creation
      • mark module as ’skipped’ in import settings
      • if module has parent-child linkage in the import settings - mark both (parent and child) as ’linkageRejected’
    • DO NOT try to set parent-child linkage on this step (even if they should be added based on module settings)
  • Try find workflows by names:
    • if found apply workflow
    • else - skip workflow setting
• Go for each module marked as parent and has ’linkageRejected == false’
  • link child module by alias based on settings from the import file
• Go for each module that is stored in the file AND is not marked as ’skipped’:
  • update module (by Properties tab data)
  • update module (by Layouts tab data)
  • update module (by Table tab data)

BACKLOG

Default setting for availability for search engines

1) Add default configuration setting

Add setting to ’Module’ -> ‘Properties’ -> ‘Default Properties’ -> “Show new items for search engines”:

• Defines if module items should be automatically visible for search engines after create item action (default value for ”Show this page for search engines” checkbox in ’item’ -> ‘SEO’ tab).
  • Via Admin UI
  • Via Import process
  • Via Create item form from the site front-end

Location:

https://prnt.sc/ua8j6a

2) Setup default state of the new setting for system properties

Preselect ”Show new items for search engines checkbox” for the following system modules:

• Blog Post
• Page
• Page Folder
• Blog
• Event Groups
• Events

3) Add two buttons that ‘enable’ and ’disable’ all existing module items of the particular module for search engines

DESIGN:

https://invis.io/3WYTDG1PKEQ

BACKLOG

Custom Reports needing export of Secure Zone members

1) Add new type of custom report called “Contacts and Secure Zones”

SETTINGS:

- hide Form Filter when this type is selected

FIELDS:

- Contact Fields (Same as for all other report types)

- Secure Zone Membership Fields:

• Secure Zone Name
• Secure Zone Membership Status
  • Active
  • Expired
  • logic:
    if 'nowDate' < 'secureZoneMembershipExpiryDate' then ’Active’ else ’Expired’
• Secure Zone Membership Cost
  • Secure zone price taken from secure zone settings
    • country/currency setting for price should be taken from the latest order that was made via form with secure zone subscription
    • if ’Renewal Rate’ is ’Once’ - take cost from the order (order line price)
    • if no such order - display empty value
• Secure Zone Membership Currency
  • currency should be taken from the latest order that was made via form with secure zone subscription
  • if ’Renewal Rate’ is ’Once’ - take cost from the order (order line price)
  • if no such order - display empty value
• Secure Zone Membership Expiry Date
  • Expiration date that is assigned to the current secure zone membership http://prntscr.com/uz78rl
• Secure Zone Membership Renewal Rate (taken from secure zone settings):
  • Once
  • Day
  • Week
  • Month
  • Year

- Advanced CRM groups (same as on ‘Contacts only’ report type)

FILTERS:

- Add Secure Zone Membership Fields to the filters:

• Secure Zone Name (dropdown)
  • -- all secure zone names --
• Secure Zone Membership Status (dropdown)
  • Active
  • Expired
• Secure Zone Membership Cost (string)
• Secure Zone Membership Currency (dropdown)
  • -- list of all currencies allowed for the site (based on domain settings) --
• Secure Zone Membership Expiry Date (date string)
• Secure Zone Membership Renewal Rate (dropdown)
  • Once
  • Day
  • Week
  • Month
  • Year

2) Add human-friendly labels for all other types

Display these labels instead of ENUM values on reports list layout http://prntscr.com/uz6w0f

• Contacts Only
• Contacts and Cases
• Contacts and Orders
• Contacts and Event Bookings

References:

Backlog Source

Fields (BC example): https://prnt.sc/ulsji4

Results (BC example): https://prnt.sc/ulsj1l

BACKLOG

Shipping option price limitation config

Add to ’eCommerce’ -> ‘Settings’ -> ‘tax and shipping’ new setting called “Shipping option order price limitations applied to”
Location: http://prntscr.com/v0oq2r

Options (dropdown):

• subtotal with tax (default)
• subtotal without tax

Logic:

Based on the selected value - apply ”Shipping option order price limitations” accordingly:

• in JS logic in order to display shipping option or not
• in backend if shipping option set request was pushed to the server but shipping option doesn't allowed by price limitation

BACKLOG

Setup primary domain to be first in SEO canonical link helper

Improve canonical link helper:

Domain selector should show Primary domain by default (first option in dropdown)

http://prntscr.com/v9z3i7

Primary domain can be setup on domain setting page: http://prntscr.com/v9z2zx

BUG

Secure/Non Secure form submission folder form setting

Fixed ability to download secured file only in you are logged in to the admin dashboard

BACKLOG

Sitemap.xml Exclude Module List

Add multiselect dropdown field to the ’SEO’ page called “Exclude Module List”

Includes all system and custom module names to select.

Remove existing hardcoded exclusion of the ‘Page Folder’ module and preselect All following modules for this dropdown by default:

• "ItemAuthor",
• "BannerGroup",
• "Banner",
• "FAQGroup",
• "FAQQuestion",
• "GallerySlider",
• "Slide",
• "PageFolder"

Apply logic:

Do not include items of modules selected in the ’Exclude Module List’ to the sitemap.xml

Note:

The “Global ‘Show for Search Engines’” buttons will not modify those items selected in the exclusion list.

Source:

https://forum.treepl.co/t/sitemap-xml-not-adding-page-folders/1107

BACKLOG

Email Verification flow improvement

When Email Domain verification process fails - show ’Retry’ button when statuses set to failed http://prntscr.com/udjtv0.

Clicking on the button should retry the verification process on the Amazon side. States should be reset to pending.

BACKLOG

Add reply-to sender for workflows

Modify workflow emails by adding reply-to header and copy email of the CMR user that originally triggered this workflow.

BACKLOG

Secure/Unsecure form submission folder

1) Add new settings to the ‘Form’ -> ‘Settings’ page:

• Secure Uploads (default: False)
• Uploads Folder (default: /_form_submissions/)
  • Folder picker to select path to ftp folder (do not allow a paste of folder path manually)
  • Do not allow ftp root (/).

2) When form is submitted, store uploaded files (from custom fields and advanced CRM group fields) in the folder selected in the ’Uploads Folder’ setting.

Create folder if it does not exist when submitting the form.

When accessing any file - check if it's folder contains any folders set in any form’s secured folder setting:

• requested file path contains (starts with) any form's ’Uploads Folder’ setting and the form has ’Secure Uploads’ set to “true”
• if folder is secured - verify that current site visitor is a logged in admin user
• if so - allow access to the file
• otherwise - show 403 page

Source:

https://treepl.co/public-backlog-state/in-process/user-submitted-file-upload-to-specific-folder

BACKLOG

Update CRM Contact Group on ‘Update Account’ form

1) ‘Update Account’ system form improvement:

On submission of the ‘Update Account’ form - update CRM group fields that are already attached to the current contact CRM (either globally attached to contacts or custom attached to individual contact).

Form field names would be the same as they are on web forms (‘groupAlias_fieldAlias’ pattern)

2) ’Update Account’ Form in toolbox update:

In the component toolbox, under ‘Secure Zones’ > ‘Update Account Form’, in addition to the current fields, generate all advanced CRM group fields that are assigned to Contacts globally.

NOTE: All custom attached CRM groups can still be updated via the ‘Update Account’ form but all fields for that custom group should be manually added to the update account form's HTML code by the developer based on ’groupAlias_fieldAlias’ pattern for form fields names.

3) Provide ability to store files submitted via edit account form in certain folder

Add section to ’Settings’ -> ‘Misc’ -> “CRM settings”:

• Uploads Folder (default: ‘/_customer_data/’)
  • Folder picker to select path to ftp folder (do not allow a paste of folder path manually)
  • Do not allow ftp root (/)

• Secure Uploads (default ‘false’)

When user uploads file on edit account form submission:

• add folder with member id (if not existed yet)
• place uploaded file in that folder

If ’Secure Uploads’ == true then allow download files from ’/_customer_data/’ folder for the logged in admin user only.

BACKLOG

Advanced CRM groups on custom reports (+export)

1) Integrate 'Advanced CRM Groups' to the custom reports:

• Add ability to choose fields from Advanced CRM Groups attached to selected primary CRM type (entity that is chosen in 'Type' in settings tab http://prntscr.com/ugy9qk). Selected fields will then be shown on the ‘Fields’ tab.
• Provide ability to apply filter to any Advanced CRM Group's field that was shown on the ’Fields’ tab (regardless if it was chosen or not)
• Show Advanced CRM Group fields selected in the ‘Fields’ tab on the Results table. Add those fields to the export file as well.

Design: https://projects.invisionapp.com/share/9QYC4SUDCJP#/screens/427731175

2) ‘Select all’ UI improvement for groups of fields

Add ability to select all fields via one checkbox in title section as shown in design: http://prntscr.com/ugyf7c

Provide such ability to all groups (system groups and Advanced CRM Groups)

3) Improve sorting on results tab

Provide ability to sort results by any field shown on the results tab (any contact, case,advanced CRM group field).

Check that sorting and pagination are performed via server side, not via UI capabilities

4) Fix report results headers

• Remove prefixes (like Case, Contact, etc):
  • in table titles on result tab http://prntscr.com/ugyii6
  • in export file headers http://prntscr.com/ugykm6
• Make header in excel file to be bold (http://prntscr.com/ugylok)

BACKLOG

CRM import/export + advanced CRM groups

1) Include Advanced CRM Groups into the Import/Export functionality

Export:

• When Exporting any CRM entity (Contact, Form Submission, Order or Booking subscription) - collect all advanced CRM groups that are attached to the selected set of items (for example if you choose form for case export - grab only advanced CRM groups attached to items that were retrieved by the query) and extend Excel table by them
• use groupAlias_fieldAlias format for column titles

Import:

• provide the ability to import Form Submission and Booking subscription.
• use groupAlias_fieldAlias format for column titles as markers for fields that need to be updated
• when importing data:
  • if there will be no field with some fieldAlias in group with groupAlias - skip content of this column
  • if create or update operation is impossible for any entity (due to lack of required columns or empty/incorrect cell value) - skip processing this particular item and continue to the next item.

2) Implement "Get Import Template" button

• Add "Get Import Template" button.
  When clicked show popup with advanced CRM groups represented as checkbox list.
• Allow user to choose what groups should be included in the template besides native entity data.
• Add this button to Contact, Form Submission and Booking subscription
• use groupAlias_fieldAlias format for column titles

DESIGN:

https://invis.io/VMYECYV6ZGQ

BACKLOG

module_tag_list and module_category_list improvement

1) Improve performance of 'module_tag_list' and 'module_category_list' components

Use search by a separate table in order to retrieve data faster.

Add additional table that will hold the following data:

• release date
• expiry date
• active (boolean - ‘true’ if ’enabled’ AND product inventory visible etc)
• moduleId
• itemId
• tagname or categoryId

Update this table on:

• module item add
• module item edit
• module item delete
• reindex module
• reindex site

Redo 'module_tag_list' and 'module_category_list' logic so it should search its data based on the table above instead of searching by regular site search.

Sorting and indexing should be performed via SQL instead of via the C#

BACKLOG

Export of orders

Add ability to call export for Orders

- Green for order data. Data goes on the 1st row.

- Red for order lines data. Product data goes starting on the 2nd row (1st row is empty for them) and goes down until all order lines will be output

Column Headers:

• Order ID
• Order Name
• Currency/Country
• Status
• Member Email
• Invoice Number
• Invoice Date
• Weight Measurement
• Dimension Measurement
• Shipping Address
• Total Cost
• Amount Paid
• Pending Collection
• Shipping Cost
• Discount
• Gift Voucher
• Created Date Time
• Product
• Attributes (use pattern: http://prntscr.com/uizc1s)
• Weight
• Width
• Height
• Depth
• Units
• Unit Price
• Tax Rate
• Total Price

BACKLOG

Exporting Subscribers from Events

Add export Event Subscribers functionality on 'Events' -> ‘Edit Event’ -> 'Subscriptions' tab (https://prnt.sc/sbawkq)

Resulting excel should have the same columns as the table has on that page.

BACKLOG

Rounding Formula for Taxation Engine

Implement rounding algorithm that will be based on:

1) Bankers Rounding: when rounding applied to a number that has 0.5 in the decimal component of the price (represented in cents)

2) Error Compensation Algorithm: for all other roundings (similar to the one that BC had: https://docs.worldsecuresystems.com/user-manual/e-Commerce/Taxes/working-with-the-improved-taxation-engine)

Represented algorithm should be applied to the following prices separately: (names are taken from this table https://docs.google.com/spreadsheets/d/1mUVUDVayY8lj2LhzrUQTIOQ_G660Vbcj5PyiOMG4wpg/edit?usp=sharing)

• Product item in cart 'item.unitTotalPrice' and 'item.unitTaxPrice'
• Product item in cart 'item.totalPriceExcludingTax' and 'item.totalPrice'

Following data should be calculated as SUM of already rounded 'item' data (so additional or separate rounding should not be performed)

• subTotalPrice
• grandTotalPrice
• totalPrice
• totalPriceExcludingTaxAndGiftVoucherAmount
• totalPriceExcludingTax

Example of algorithm:

• https://docs.google.com/spreadsheets/d/1ploqTNaw53LmORFwljXqGWiy193KYs3i0qhVo_HHJUs/edit?usp=sharing

BACKLOG

"Tax Never Applies" option for price

Add checkbox to the price instances near tax dropdown, called: “Tax Never Applies: (default= false)

Logic:

When checked - tax should not be added to the order line that represents this product (or shipping option) when tax selected on the shopping cart.

Add this checkbox for:

• module item price (for consumer and wholesaler) - http://prntscr.com/ul2nxv
• shipping option price - http://prntscr.com/ul2ohc

Also add it to Products import/export data

BACKLOG

Shipping and tax improvements

Add new tab to the 'Ecommerce' -> 'Settings’, called “Tax and Shipping”

Add following settings (DESIGN https://invis.io/JGYORI2PC2A):

“Country/Currency select”
(Choosing value from this select to load settings specific for that particular country/currency pair)

• Tax applies to (multiselect dropdown list)
  Determines if taxes should be applied to selected entities or not
  - shipping options (selected by default)
  - gift vouchers (selected by default)
• Auto-select tax if only one option available (boolean - default value ’true’)
  Determines if the single tax in the tax dropdown be automatically selected when a user comes to the shopping cart and/or changing country.
• Hide tax selector if only one option available (boolean - default value ’false’)
  Determines if the tax dropdown be hidden by JS if there is only one tax option available.
• Enable tax dropdown (boolean - default value ’true’)
  Determines if {% component type: "tax_codes" %} component renders the tax dropdown or not.
  Also determines if server-side validation should require it or not.
• Shipping Countries (multiselect dropdown list - default empty list)
  • -- list of all countries --
    Also provides the ability to select all options. So the user can easily select all and then deselect the few not needed.
  • Logic:
    determines what country list will be shown when rendering the component {% component type: "countries" %}
    - if value is empty - show all countries. Otherwise show only selected countries
    - if {% component type:"countries", allowedCountries:"US,AU" %} has ’allowedCountries’ param - use its list of countries instead of shop setting (component param overrides shop settings).
• Choose Default Country (dropdown - default = null)
  • -- list of all countries selected in Shipping Countries dropdown --
  • Logic:
    Determines what country should be automatically selected when a user comes to the shopping cart.
• Make shipping country required (boolean - default ’false’)
  Determines if country dropdown can be deselected or not

BACKLOG

Do not skip selected shipping options

When shopping cart updated after changing quantity - if shipping options that was selected previously are still available - leave it selected.

When any of the following processes occured:

• add product to cart
• change product quantity
• remove product from cart
• add/remove discount code
• add/remove gift voucher

DO NOT reset selected shipping option if after shopping cart update that shipping option is still available.

BACKLOG

When Sorting items via ‘sortBy’/‘sortOrder’ - skip weighting

Improve sorting of module items functionality on {% component type: "module" %} and {% component type: "module_of_member" %} via a new parameter for the component:

• ignoreWeighting: "true" (default value ‘false’)
  • if value true:
    skip sorting by weight before sorting by 'sortBy' (if 'sortBy' is empty then alphabetical sort should be applied - remove "sorting by weight first" logic also)
  • if false:
    apply current sorting algorithm (first by weight then by name ASC).

Add this new parameter to the toolbox for:

• Custom modules
  • List of items
  • List of member's items
• Gallery/Slider
• FAQ`s
• Banners
• Authors
• Events
• eCommerce
  • Catalogs list
  • Products list

BACKLOG

‘CRMCustomGroup’ component type alias to ‘CRMContactCustomGroup’

Create an alias of 'CRMCustomGroup' that will trigger the same functionality that 'CRMContactCustomGroup' (including all component properties).

So {% component type: "CRMCustomGroup" %} will do the same as {% component type: "CRMContactCustomGroup" %}

BACKLOG

Group products JS and liquid logic

Product Grouping on Detail Layout improvements:

1) Add to all product detail layout custom forced wrapper (only if product has any grouped products):

<div class="cms-product-wrapper" data-cms_product_wrapper="{{{{this.Id}}}}" data-cms_layout_name="{model.Layout}"></div>

2) Add JS that will request, via AJAX, the selected sub-product or main product once the appropriate option has been selected in the dropdown rendered via the component.

Render layout based on the 'layoutName' and 'productID' sent in the request and with the following liquid variables:

• this
• si
• siteinformation
• request
  

3) Add ‘this.URL’ to the liquid context of each item in {% component type: "grouped_items" %}.

Add ‘this.URL’ to the <option> element as 'data-product_url' attribute.

4) Provide custom event ’onProductLayoutChanged’ that could be used by any site owner's JS once layout will be changed via AJAX.

Product Grouping on List Layout improvements:

1) Fix component type module so it returns only main Product (if it is part of the Grouped products list) and don't return Grouped sub-products.

Only MAIN product should be listed via {% component type=module %} (and type=module_of_member).
Sub-products should not impact the pagination and should not be listed except if those components have ‘isSearchResult: "true"’ or ’searchScope’ param in which case include subproducts in the search results.

2) Add custom wrapper to list layout if it contains any grouped products (if layout contains {% component type: "grouped_items" %}) and if the 'object' param is set to 'item' http://prntscr.com/tzf1n2 (wrap same as in detail layout above)

NOTE:

If you are using component type module with 'object: "collection"' then you should add wrapper from point 1 inside your for loop manually in order to allow product grouping logic to work.

3) Provide custom JS event 'onProductLayoutChanged' and JS for layout reload (similar as described for the detail layout above).

4) Fix group order

Order of items that are listed via component should be the same as sorted in the admin.

Example of BC product groups:

Catalog where all products stored:
https://zaycev.worldsecuresystems.com/books/fiction

Main product:
https://zaycev.worldsecuresystems.com/books/fiction/main-prod

Sub products:
https://zaycev.worldsecuresystems.com/books/fiction/sub-prod-1
https://zaycev.worldsecuresystems.com/books/fiction/sub-prod-2

jQuery example of event handler:

$('body').on('onProductLayoutChanged', function(){
    <!-- some code -->
});

BACKLOG

Feature flags changes (v5.6)

Apply following changes to feature flags:

Remove flag from the system:

• Advanced URL manager

Move to internal flags AND set enabled

• New liquid engine & nICE 2.0
• Advanced payment flow

BACKLOG

BONUS: Customer Submitted Content - Add workflow for when items are edited

Provide ability to setup workflows in ’Module’ -> ‘Settings’ -> ‘Site User Permission’ (http://prntscr.com/rl85f0) for the following actions:

• Add item by site user:
  Current workflow list should be transformed into this setting. Move multi-select under ’Allow add new items’ option.
• Edit item by site user:
  New multi-select of workflows.
• Delete item by site user:
  New multi-select of workflows.

Provide ’customWorkflows’ field to be processed on module item create/update/delete site user forms.

Logic of this field should be exactly the same as for customising workflows for web forms - where by it overrides workflow/s selected in form settings

Source:

• https://forum.treepl.co/t/custom-module-user-input-workflow/867
• https://treepl.co/public-backlog-state/request/customer-submitted-content-add-workflow-for-when-items-are-edited

MISC

Admin Proof Read/Suggestions (Part 1)

Here is a Google Doc with all admin wording suggestions.

Minor text changes in most cases.

https://docs.google.com/document/d/1qg5mZaZl0h7AFb8YFyGsjKMAsEDysBjGTQzhxqyHSUY/edit?usp=sharing

1. [ ✔] When editing a Menu item, the ‘ID Name’ field should perhaps be just ‘ID’

2. [ ✔] In the Component toolbox, perhaps remove the words ‘Get’ from the beginning of the Item Form options

3. [ ✔] In the Component toolbox, when getting a search form, there is the FORM CODE and the COMPONENT CODE, but it’s not particularly clear these are two links, or the Form code link might be missed. Suggest separating these 2 links a bit more or perhaps even having 2 headings, eg

4. [ ✔] In the Component toolbox, perhaps use correct apostrophes in the FAQ section

5. [ ✔] In the Component toolbox, use lowercase ‘o’ in ‘of’ under the “Banners” and “Authors” sections for consistency with all other options

6. [ ✔] In the Component toolbox, under “Events”, use capital letter for ‘Event Groups’, ‘Event’ and ‘Form’.

Perhaps rename “List of event’s groups” to “List of Event Groups”

7. [✔ ] In the Component toolbox, under “eCommerce”, suggest using title-case throughout for consistency

8. [✔ ] In the Component toolbox, under “CRM”, suggest rewording options for consistency

9. [✔ ] In the File Manager, when clicking the “Add New” button, it could probably just say “Folder” and “File” instead of repeating “Add new folder/file”

10. [✔ ] In the File Manager, the upload file drop zone could be made a little clearer by adding “to upload” after “click here” link

11. [✔ ] In the File Manager, in the context menu of a folder/file, perhaps the “Secure Zone” option should just read “Secure”

13. [✔ ] In the Form “Settings”, perhaps add an ‘s’ to “Workflow” and “Secure Zone” labels (since multiple items can be selected).

And, below this, the term “Autoresponder” is probably more widely used instead of “Auto-response” (not a big deal though)

15. [✔ ] In Secure Zone “Members” tab, the “Emails” column header should probably just be “Email” (without the ‘s’)

16. [✔ ] As above, the same change for “CRM” > “Contacts” list

17. [✔ ] In “CRM” > “Contacts”, when adding a new contact, perhaps change “E-mail” field label to “Email” for consistency

18. [✔ ] In “Form Submissions”, perhaps change the column heading of “Date Submission” to “Submission Date” or “Date Submitted”

19. [ ✔] In “CRM” > “Orders”, when viewing the “Payments” tab, perhaps use a capital ‘C’ in “Amount Captured” column heading (for consistent title-case use)

20. [✔ ] In “Email Marketing” > “Email Campaigns” in the ‘Settings’ tab, for the “Schedule Delivery” option, perhaps change to just “Delivery”.

21. [✔ ] In “Email Marketing” > “Mailing Lists”, under ‘Subscribers’ tab, perhaps adjust “Emails” column heading to just “Email”

22. [ ✔] In “Email Marketing” > “API Provider”, adjust page heading to use a capital ‘P’ for “provider”

24. [✔] On the ‘Catalogs’ tab when editing a Product, perhaps add heading above the selection boxes to make it a little clearer what’s what

25. [ ✔] On the ‘Inventory’ tab when editing a Product, perhaps use title-case for the ‘Added to shopping cart’ label making it ‘Added to Shopping Cart’ (for consistency)

26. [ ✔] Similar to point 24) above, perhaps add headings to the selection boxes

27. [ ✔] Under ‘Grouped Items’ tab when editing a Product, perhaps use title-case for the “Main product” checkbox label (for consistency)

28. [ ✔] Under the ‘SEO’ tab for ALL module types, perhaps reword and title-case the “<head> section extra” label, possibly: “<head> Section Additions” or “Additional <head> Code”

29. [ ✔] In ALL module ‘Settings’ page, use title-case for the ‘Site User Permissions’ checkbox labels. And perhaps change “Auto-response” heading to the more widely used “Autoresponder”

32. [ ✔] For ALL module “Table” tab, consider using title-case for the ‘Add new column’ heading so it reads “Add New Column” (in the side panel when adding a column)

35. [✔ ] Under a Shipping Options “Settings” tab, consider adjusting the “Show Shipping option to” label to title-case so it reads: “Show Shipping Option to”

37. [ ✔] Under “eCommerce” > “Settings” → ‘Manage Status’ tab, consider adjusting for title-case

39. [ ✔] Under “Reports” > “Custom Reports”, when editing a Report, the help bubble for “Settings” and “Form Filter” need adjusting.

For “Settings”, it still refers to the previous naming of “Make Public” but should now be “Make Sharable”

41. [ ✔] Under “Settings” > “Domains” and ‘Site Domains’ tab, consider adjusting for title-case in the sidebar for editing ‘Currency and Format’ and ‘Country’

42. [ ✔] ...as above, also in the ‘Email Domains’ tab when adding a new domain, adjust for title-case

44. [ ✔] Under “Settings” > “Admin Users”, column header and edit field label say “E-mail” consider changing to “Email”.

Also note edit panel heading to title-case

45. [✔ ] Under “Settings” > “Admin Menu Configurator”, consider adjusting headings and buttons for title-case

46. [ ✔] Under “Settings” > “Setup Analytics”, consider correcting “Id” to “ID”

48. [ ✔] Under “SEO” rename the “Pages search engine settings:” label to be more clear (since this option enables/disables ALL module item content, not just Pages).

Something like “Global ‘Show for Search Engines’” with maybe even a paragraph under this heading, or a help bubble, describing what it does exactly,

BACKLOG

Fix truncate liquid string filter

Fix liquid ‘truncate’ filter so if second param is NULL (http://prntscr.com/ui7qip) then apply "..." string as suffix.

And if second param is an empty string "" (http://prntscr.com/ui7r3k) then apply an empty string "" as suffix.

Source:

https://forum.treepl.co/t/request-withdrawn-implement-truncate-words-liquid-string-filter/491

BACKLOG

Improve pay by cash and offline payment namings

1) Rename 'offline-credit-card-payment' system page (https://prnt.sc/spcfi5)

- Change name and URL to 'deferred-order-payment'.

2) Rename Offline Credit Card Payment system email (https://prnt.sc/spcg1w)

- Change name to 'Deferred Order Payment'.

- Change value of the 'this.offlinePaymentPageURL' according to the new URL of 'deferred-order-payment' system page.

- Change Subject to ’Pay Order #{{this.order.id}}’.

3) Change offline credit card payment namings (https://prnt.sc/spcer0)

- Change 'Offline Credit Card Payment' to 'Deferred Order Payment'.

- Change 'Send Offline Credit Card Payment' to 'Send Deferred Order Payment Email'.

- Change 'Pay By Credit Card' to 'Pay Order'.

BACKLOG

Add ability to track offline payment

1) Provide ability to track offline payment for the order

- Rename 'Paid By Cash' (http://prntscr.com/ui8sv8) to 'Add Offline Payment'.

- When clicking on it the sidebar panel appears http://prntscr.com/ui8u0m.

- Make 'Payment Type' a dropdown to be active and provide the following options (instead of 'Offline'):

• Cash (default)
• Cheque
• EFT
• Money Order
• Other
• Credit Card

Add additional fields to the payment form:

• Payment Date (datetime - defaults to current date/time)
  - Renamed ’Date’ label to ’Payment Date’ http://prntscr.com/ul7wju
• Notes (textarea)
  - For custom purposes. Just store the data and show on view and edit mode http://prntscr.com/ul7tf2

Once payment added - it's type should be shown in the table http://prntscr.com/ui8x7v

Rename all existing ’Offline Payment’ types to 'Cash'

BACKLOG

Add "ID" to customizable columns

Add ability to choose 'ID' property for the custom columns http://prntscr.com/tjg8az.

If selected - show item ID in the list view table according to the custom columns display rules.

BACKLOG

Override quantity field with Product Minimum Units

1) Add validation for shopping cart ’change quantity’ and product ’add to cart’ actions:

• validate that total quantity after add or change action is between Minimum Units and Maximum Units http://prntscr.com/tjp1fc
• if Minimum Units is empty - default value is 1
• if Maximum Units is empty - default value is infinity

2) Show error messages once validation is not passed:

• quantity > Maximum Units:
  ERROR: Quantity entered is too large, please enter a smaller quantity.
• quantity < Minimum Units:
  ERROR: Quantity entered is too small, please enter a larger quantity.

3) Change default layout (/cms-assets/layouts/ecommerce_item_quantity/default.layout)

From:

<input type="number" data-ecommerce_product_quantity_field="{{this.id}}" value="1"/>

To:

<input type="number" data-ecommerce_product_quantity_field="{{this.id}}" {% if this.minimumUnits > 0 %}min="{{this.minimumUnits}}"{% endif %} {% if this.maximumUnits > 0 %}max="{{this.maximumUnits}}"{% endif %} value="{% if this.minimumUnits > 0 and this.params.quantity == null %}{{this.minimumUnits}}{% else %}{{this.params.quantity | default: 1}}{% endif %}"/>

4) Fix bug: ’this.params’ object is not filled by custom params.
As a result such record {% component itemId: "{{this.Id}}", type: "ecommerce_item_quantity", quantity:"10" %} isn't rendered with quantity = 10 when it should.

Source:

https://forum.treepl.co/t/over-ride-quantity-field-with-product-minimum-units/1104

BACKLOG

Add SKU code as default column for the product

Example: https://prnt.sc/slw24j

Update defaults only. If custom columns have been implemented do not update.

BACKLOG

‘Products’, ‘Shopping_Cart’, ‘Order’ object extending

Add following properties to the 'Product' (order line), 'Shopping_Cart' and 'Order' objects:

• taxCode
• taxCodeHtml
  • Product (order line)
  • Shopping_Cart
  • Order objects
• unitRecommendedPrice
• unitRecommendedPriceHtml
• unitRecommendedTaxPrice
• unitRecommendedTaxPriceHtml
• unitRecommendedTotalPrice
• unitRecommendedTotalPriceHtml
• onSale
  • Product (order line) object

BACKLOG

Property (type media) - apply URL partial encode for liquid

Improve module item liquid object for ‘Media’ type properties in {% component type: "module" %} and {% component type: "module_of_member" %}:

If property type is 'Media' - launch the following algorithm to its value:

• extract file name from file path (file name is between last "/" and "end of string" OR "?")
• apply URL encode to the name
• join path and name back together
• place the value back to the property

The value of the 'Media' property still should be un-encoded on edit item form in the admin.

Also update "copy to clipboard" links so they return encoded filename https://prnt.sc/uu6ljx

Eg: So if an item would have a value like "/pdf/myPdf#2.pdf?downloadable=1" it will be encoded like "/pdf/myPdf%232.pdf?downloadable=1" and placing {{this.myPdf}} into the href attribute of the link will not break the file accessibility. For example: <a href="{{this.myPdf}}">Download PDF<a>

BACKLOG

Add module ID/alias to the item object (LIQUID)

Extend module item object by adding following properties

• Module_ID
• Module_Alias

BACKLOG

Add {{this[‘LastUpdatedDate’]}} to properties list (toolbox)

Add {{this[‘LastUpdatedDate’]}} to properties list in ’Module’ -> ‘Layout’ -> ’Properties’ toolbox.
It exists, just not listed.

https://prnt.sc/mm2pop

BACKLOG

Duplicate Workflows functionality

Provide ability to duplicate Workflows to copy workflow instance:

• with the same list of ’Recipients’
• linked to the same ’Workflow Email’

BACKLOG

Add browser Cache control headers

Add this header to all file requests (max age of 7 days):

“Cache-Control: private, max-age=604800”

BUG

date liquid filter fixes

Fix/implement following patterns for date filter (that is based on http://strftime.net/):

1) Implement %w pattern:

• Weekday as a decimal number, where 0 is Sunday and 6 is Saturday.
  Example: {{ "now" | date: "%w" }}

2) Fix %v pattern for VMS date format: http://prntscr.com/ttaz4n

• format should be like http://prntscr.com/ttbayy
  Example: {{ "now" | date: "%v" }}

3) Implement %Z pattern:

• should show name of the timezone set for the site (use same values as for liquid's {{request.timezone}} object)

4) Fix %z pattern:

• shows +00:00 but should be -05:00 (if the site timezone is set to -5) (use same values as for liquid's {{request.timezone}} object)

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://treepl.co/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" %}

BACKLOG

Payment Flow For Europe:
Two-step card payments

1) Add new setting to the form settings (show only if at least one of the selected payment gateways support Two-step card payments)

• Payment Flow
  • Instant payment (default)
  • Two-step card payments

2) Payment gateways with Two-step card payments support:

• Stripe
• Bambora

3) Current payment flow logic is Instant payment.
Once Two-step card payments selected and if payment gateway supports Two-step card payments - setup and apply following payment flow logic:

• documentation (from Stripe)
  - https://stripe.com/docs/charges/placing-a-hold
  or
  - https://stripe.com/docs/payments/capture-later
• Once user submitted a payment form - place required funds on hold.
• Creating order, email notifications etc should be created/sent similar as for Instant payment flow but set cost to pending amount value. Set payment state to pending. Set Order state to pending charge.
• Add ability on order -> payments to proceed hold payment https://prnt.sc/ruktxm
  • If clicked and payment proceed successfully - set payment state to Success
  • otherwise - set payment state to canceled and Order state to Payment Canceled.
• If hold is expired (7 days period of hold) - then force change payment state to canceled. Order to Payment Canceled.
• Add cancel button. Release the hold funds and payment state to canceled. Order state to Payment Canceled.
• Failed order could be fixed via adding cash payment record or via deferred payment flow.
• If order consists of downloadable products only - force process Instant payment flow

4) Add Amount captured column on the Order -> Payments table http://prntscr.com/tfci79

BACKLOG

Payment Flow For Europe:

Stripe for EU (SCA via 3D Secure)

1) Implement Strong Customer Authentication (SCA):

(SCA) is a regulatory requirement in effect as of September 14, 2019, that impacts many European online payments.
It requires customers to use two-factor authentication like 3D Secure to verify their purchase.

2) Add setting to stripe Payment Gateway (Enable 3D Secure)

Enabling this setting will force payment form to trigger Payment Intents flow with support of 3D Secure rather then Charges

3) Create new system page: Checkout payment (/checkout-payment)

4) Payment Intents flow will not ask you for card details on the form but once the form is sent - it should redirect you to Checkout payment system page.

In case you are paying for Event, secure zone subscription or general payment:

• order should be created after payment is confirmed
• secure zone subscription should be applied after payment is confirmed
• event subscription should be added after payment is confirmed

5) If shopping cart total price was changed after user comes to Checkout payment system page - show validation error on submit:

“Price of the shopping cart was changed.
Please go back to the <a href="/shopping_cart">Shopping Cart</a> page, verify the data and re-submit the form.”

BACKLOG

Payment gateways:

Bambora Payment gateway

1) Create support for Bambora Payment gateway.

Use Norway and Switzerland logic version:

https://developer.bambora.com/europe/checkout/getting-started/create-payment

2) Gateway logic should support following flows of capturing price that should be configured via gateway settings (similar as for stripe):

• Instant payment: charge money right away
• Two-step card payments: place money on hold allowing to charge manually via order

3) Show error message if domain is not verified (endpoint is not valid error from bambora) on charging:

“The payment can't be processed. This domain is not verified by Bambora. Please contact their support in order to get the domain verified.”

BACKLOG

Custom Reports:

Builder

DESIGN http://prntscr.com/thh497

1) Add page and menu item: ‘Reports’ > ‘Custom Reports’

Provide ability to:

• Add new report
• list reports (with pagination 20 per page)
• Show only reports marked as public or that were created by the current logged in Admin User

2) All functionality with Custom Reports is available starting from Pro plan.

3) Reports Builder:

SETTINGS

Save the report by name and set as public option that allows you to share the report with other admin users. If Make public set to false - you are the only one who will see this report.

TYPE

The type determines what fields should be collected for Fields and Filters steps and what entities should be collected for the final report.

- Contacts (default)

- Contacts and Cases

- Contacts and Orders

- Contacts and Event Bookings

FORM FILTER

Select a form (from all available web forms) to filter only those cases,orders or event bookings that belong to this form.

Show section only if type is one of:

- Contacts and Cases

- Contacts and Orders

- Contacts and Event Bookings

---------

FIELDS

Select Fields to be seen on report as column headers

• Fields For Cases:
  • Case Id
  • Form name
  • Date Submission
• Fields For Orders
  • Order Id
  • Form name
  • Date Submission
  • Currency
  • Country
  • Total Cost
  • Amount Paid
  • Pending Collection
  • Shipping Address
  • Shipping City
  • Shipping State
  • Shipping Zip Code
  • Shipping Country
  • Invoice Number
  • Invoice Date
  • Status
• Fields For Booking Subscriptions
  • Booking Subscription Id
  • Form name
  • Booking Date
  • Allocation
  • Price
  • Event Id
  • Event Name
• Contact fields
  • Contact
  • First name
  • Last Name
  • E-mail
  • Address
  • City
  • State
  • Zip Code
  • Country
  • Site
  • Phone
  • Status
  • Notes
  • Type
• Form fields (show only if certain form was included for report)
  • <list of all selected form's custom fields>

---------

FILTERS

• Field (to filter by)
  • <all fields available from the report type>
• Condition options (depending on Field value type)
  • Equals
  • NotEqualTo
  • LessThan
  • GreaterThan
  • LessOrEqual
  • GreaterOrEqual
  • Contains
  • DoesNotContain
  • StartsWith
• Value (depending on Field type)
  • if the field is general string or number type - show text field
  • if it's a dropdown or radiolist - show dropdown

Ability to add additional filtering rules

---------

RESULTS

Generate sortable and paginated results table.

Ability to export to Excel file.

BACKLOG

Custom Reports:

Export

Provide ability to export Custom report to Excel file.

Columns should be the same as the report.

BACKLOG

Import/Export of prices, attributes and inventory

Export format:

Add all system properties of the product after default properties and before custom properties

Product area should be defined as (http://prntscr.com/rhxeho):

• (1) first line - info of the product and its relations
• (2) all lines under with the same SKU code before end of file or another SKU code (SKU code should be same and present in all lines of the product data)

Add following fields for specific-serialized relations:

• Parents [name of the parent module]. eg: `Catalog`
  • Value: [parent item urls separated by `;`].
    eg:
    `/catalog-1/sub-catalog;/catalog-1;/;`
• Sale Price
  • Value: [country]-[currency]/[sale-price],[quantity for threshold option №1]/[price threshold option №1],[quantity for threshold option №2]/[price threshold option №2];
    eg: AU-AUD/30.00,2/26.00,5/22.00;AU-USD/20.00,10/18.00,100/16.00;
    
    NOTES:
    If no [currency] specified - use Currency-By-Country-Defaults.json mapper as default currency for country definition
• Retail Price
  • Value: [country]-[currency]/[sale-price];
    eg:

  AU-AUD/30.00;AU-USD/20.00;
  
  NOTES:
  If no [currency] specified - use Currency-By-Country-Defaults.json mapper as default currency for country definition

• Tax Code
  • Value: [country]/[tax_name or "Never"];
    eg:
    AU/Never;US/AZ;
    
    NOTES:
    If [tax_name] not set to the country or [tax_name] === ”Never”, do not apply tax
• Grouping Product Codes
  • Value: [product_sku_code][Is_main_product];
    eg:
    sub_prod_1;main_prod*;sub_prod_2;
    
    NOTES:
    If [Is_main_product] == "*" then this product IS main. Otherwise this product IS NOT main.
    
    If several products shown to be main - use last one as main and ignore others.
• Grouping Product Display Name
  • Value: [product_display_name];
    eg:
    Sub product 1;;Sub product 2;
    
    NOTES:
    Can be empty.
• Related Products
  • Value: [product_sku_code];
    eg:
    HAYNM5AXVB;sub_prod_1;HMDP9271;
• Low Stock Notification
  • Value: number
    eg:
    50
    
    NOTES:
    Greater than or equal to 0
• Enable Inventory Control
  • Value: (boolean) true or false
    eg:
    Y or TRUE
    N or FALSE or empty
• Can Pre-Order
  • Value: (boolean) true or false
    eg:
    Y or TRUE
    N or FALSE or empty
• Hide if Out of Stock
  • Value: (boolean) true or false
    eg:
    Y or TRUE
    N or FALSE or empty
• Attributes
  (ignore this cell value if product ALREADY EXIST AND has GENERATED VARIATIONS AND "Variations Enabled" cell != FALSE)
  • Value: (complex pattern described below, intended to be on one line)
    
    [attribute name][is_required]
    |
    [attribute_type]
    |
    [is_inventory_item]
    :
    [option_name]
    |
    [option_image_path]
    |
    [country]-[currency]
    /
    [option_price_1]
    |
    [country]-[currency]
    /
    [option_price_2]
    ,
    [option_name]
    |
    [option_image_path]
    |
    [country]-[currency]
    /
    [option_price_1]
    ,
    [option_name]
    ||
    [country]-[currency]
    /
    [option_price_1]
    ; (repeat)
    
    NOTES:
    If no [currency] specified - use Currency-By-Country-Defaults.json mapper as default currency for country definition
    
    [option_name] CAN'T contain following symbols
    - |
    - ,
    - '
    - *
    
    If [is_required] == * then this product IS required. Otherwise it’s not.
    
    [attribute_type] is one of the following:
    - 5 or DropDownList
    - 6 or CheckBoxList
    - 7 or RadioList
    
    [is_inventory_item] - determines if current attribute is inventory attribute, one of:
    - Y or True - (boolean) true
    - N or False - (boolean) false
    
    [option_image_path] and option prices are not required and can be skipped in format string.
    
    Example string:
    Test attr checklist*|6|N:option checklist 1|/img.jpg|AU/10|US/5,option checklist 2|/img.jpg|AU/20|US/15,option ck 3|;Test attr Dropdown List*|5|Y:option droplist 1|/img.jpg|AU/10|US/5,option droplist 2|/img.jpg|AU/20|US/15;Test attr radiolist*|7|Y:option radiolist 1|/img.jpg|AU/10|US/5,option radiolist 2|/img.jpg|AU/20|US/15;ddfdsd*|5|Y:aasas||AU/20|US/15,xasas||AU/20|US/15
    
    
• Wholesale Sale Price
  • Value: (pattern described below, intended to be on one line)
    
    [country]-[currency]
    /
    [sale-price]
    ,
    [quantity for threshold option №1]
    /
    [price threshold option №1]
    ,
    [quantity for threshold option №2]
    /
    [price threshold option №2]
    ; (repeat)
    
    NOTES:
    If no [currency] specified - use Currency-By-Country-Defaults.json mapper as default currency for country definition
    
    Example String:
    AU-AUD/30.00,2/26.00,5/22.00;AU-USD/20.00,10/18.00,100/16.00;
• Recurring Type
  • Value: one of (numeric or string value)
    - 1 or Once
    - 2 or Daily
    - 3 or Weekly
    - 4 or Fortnightly
    - 5 or Monthly
    - 6 or Quarterly
    - 7 or Half Yearly
    - 8 or Yearly
• Hide if Out of Stock
  • Value: (boolean) true or false
    eg:
    Y or TRUE
    N or FALSE or empty
    
    NOTES:
    If TRUE and no variations was created earlier - generate all variations and edit them by the values within columns Variations Code, Enabled, In Stock, Pre-Order determining variation by attribute options combination in the column Variation Options.
    If FALSE - discard variations.
• Variation SKU Code
  This column and columns below are assigned both to initial (global) product and to it’s variations.
  - Value for the first row assigned to the global product settings.
  - Values in the row/s below (that relate to initial product) are assigned to each variation row.
  • Value: string (unique SKU code, should be empty for product row but required for variation row)
    If not set - ignore entire variation row data.
    
    Eg:
    HAYNM5AXVB
• Enabled
  • Value: (boolean) true or false
    eg:
    Y or TRUE
    N or FALSE or empty
• Variation Options
  • Value:
    [option_of_attribute_1]
    ;
    [option_of_attribute_2]
    ; etc.
    
    NOTES:
    Determines what variation should be edited by the fields:
    - Variations Code
    - Enabled
    - In Stock
    - Pre-Order
    
    If such combination not found in the product - ignore changes in this row for the following columns:
    - Variations Code
    - Enabled
    - In Stock
    - Pre-Order
    
    eg:
    HAYNM5AXVB;sub_prod_1;HMDP9271;
• In Stock
  • Value: number (greater than or equal to 0)
• Pre-Order
  • Value: number (greater than or equal to 0)

BACKLOG

Liquid security issue on form submission

Add algorithm that will protect user-submitted content of liquid and JS injection in all form submissions and when user adds or edits a module item, for all text fields.

• IF Module -> Settings ->Site User Permissions -> Requires Approval == disabled https://prnt.sc/sq0ga9
  AND
• IF it contains any of the following substring:
  • {%
  • %}
  • {{
  • }}
  • <script
  • <style
  • </script>
  • </style>
• do the following:
  • if any liquid symbols was found
    • remove tags from the content
    • wrap all content with value here
  • then replace
    • <script to the <script-is-not-allowed
    • <style to the <style-is-not-allowed
    • </script> to the </script-is-not-allowed>
    • </style> to the </style-is-not-allowed>
  • run current item create/edit logic
• else
  • run current item create/edit logic
• If user edits the item and Module -> Settings ->Site User Permissions -> Requires Approval == enabled
  • Disable item after performing the changes

IMPORTANT:

Validate text value length AFTER the wrapping if it has occurred. So if original value fits the single line text field but once wrapped it doesn't - the validation error should be shown.

Example:

<div>

<h1>Some title</h1>

{{this}}

<script>location.href = "https://some-fishing.site"</script>

<style>body{display: none !important;}</style>

</div>

Replace with:

<div>

<h1>Some title</h1>

{{this}}

<script-is-not-allowed>location.href = "https://some-fishing.site";</script-is-not-allowed>

<style-is-not-allowed>body{display: none !important;}</style-is-not-allowed>

</div>

BACKLOG

Datasource Field:

When focus a field - get first 50 datasource items

Improve Datasource Form control:

• perform search by focusing the field (trigger empty search if keyword is not set or empty)
• Show 50 items of found results
• Add search icon that will submit search request by entered keyword
• Add remove icon that will erase entered keyword and will submit empty search request

BACKLOG

Recaptcha v3 validation JS fix

Fix for general form

Fix for payment form

CMS generated javascript changes to avoid conflicts with payment JS. No Partner/front-end changes required.

BACKLOG

Advanced CRM:

Custom Fields Groups CRUD Page

Add page for Custom CRM groups list (http://prntscr.com/thh86e).

Provide ability to add, edit, delete the Custom CRM group.

Provide ability to use pagination for Custom CRM groups.

Add/Edit form should contain following fields:

• Form name (string)
• Apply To (dropdown) - list of entries allowed to applied CRM group to:
  • Contact: would be listed here http://prntscr.com/thh8eg
  • Order: would be listed here https://prnt.sc/syn4d6
  • Form Submission: would be listed here https://prnt.sc/syn5ld
  • Booking Subscription: would be listed here https://prnt.sc/syn6nx
• CRM fields (panel with list of custom fields with ability to create/update/delete field. Similar to form fields builder)
  Allowed field types:
  • DateTime
  • CheckboxList
  • DropdownList
  • DropdownList (multiple)
  • ListboxList
  • RadioList
  • Boolean
  • Multiline
  • String
  • Upload
  • DataSource
  • Number

Design: http://prntscr.com/thh7y7

BACKLOG

Advanced CRM:

Custom CRM Field Groups attaching rules and linkage

There should be 2 types of custom crm groups linkage

Global setting:

• Determines what groups are marked as Attached to ALL CRM contacts.
• Represented as list of groups.

Individual Contact record Attachment:

• Determines group to certain contact linkage. 1 to 1.
• Represented as list of Groups-to-Contact records.

Saved custom crm group values for the contact should be saved as group-field-contact-value records.

group-field-contact-value records should not be deleted on unassigning Global setting or Certain Contact record Attachment from the crm contact.

Description

• If custom CRM group is attached to Contacts via global setting then each contact should view that group in the bottom of the contact details page
• If custom CRM group is attached to the certain Contact record via:
  • form submission
  • adding via button on contact detail view http://prntscr.com/orpcbb
    • Then view that groups in the bottom of the contact details page.

Linkage entities (each should have EDIT entity button and "Add Custom Fields" button https://prnt.sc/orpcbb):

• Contacts
• Form Submissions
• Orders
• Booking Subscriptions

Group Displaying Rules:

• Display custom group for the entity IF
  • Current entity type was added in the "Apply to" property of the CRM group settings.
  • OR
  • Custom group was checked in the "Add Custom Fields" setting of the current entity https://prnt.sc/orpcbb
• "Add Custom Fields" settings https://prnt.sc/orpcbb should be all unchecked by default.
  Admin user is the only one person that could check any of those custom groups.

BACKLOG

Advanced CRM:

Attach Custom field groups to web forms

Provide ability to choose Custom CRM Groups and attach them to the form.

http://prntscr.com/thh94m

Default layout builder should build all fields of each group similar to the form's custom fields.

Name should be:

[[GroupAlias]]_[[FieldAlias]]

Example:
Group alias: AccountInfo
Field alias: Position
Field: <input type="text" name="AccountInfo_Position">

BACKLOG

Advanced CRM:

Add custom CRM field groups to CRM record

CRM contact detail page should contain new button:

“Add Custom Fields”

Clicking on that button should show panel that allows to select existing custom CRM forms.
When selecting a form and click save - that custom CRM group should be attached to the Contact (Certain Contact record Attachment).

http://prntscr.com/thhakq

BACKLOG

Advanced CRM:

Liquid component tag for custom CRM fields

Add new component tag component type:"CRMContactCustomGroup":

Pattern:

{% component type:"CRMContactCustomGroup", groupAlias:"[[groupAlias]]", fieldAlias:"[[fieldAlias]]", entityType:"[[entityType]]", entityId:"[[contactId]]", collectionVariable:"", layout:"" %}

• groupAlias (required) - alias of the custom CRM group.
  • All group fields with their values should be set to the {{this.fields}} array of objects if fieldAlias is not set. Otherwise {{this.fields}} should contain only one element, being the object for the specified field set via fieldAlias.
• entityType (not required) - determines the CRM entity type to retrieve custom group for. Values can be:
  • form_submission
  • event_booking
  • order
  • contact (default, if no type set for the component)
• entityId (not required) - determines the CRM entity to retrieve custom group for
  • if entityType is contact
    • If field is empty - try use current logged in CRM contact id. - If no logged in users found return empty context item
    • If CRM contact has isDataUsingAllowed not equal to true than return empty context item
  • else
    • If field is empty - return empty context item
• fieldAlias (not required) - alias of the CRM group field. Should be used to find a particular group field value for the CRM contact (determined by entityId and the group determined by groupAlias).
• collectionVariable (not required) - works the same way as other modules.
• layout (not required) - path to FTP file that will contain layout content for the data.
  • If specified empty string - do not render anything.
  • If not specified at all - render default virtual layout.

Item context:

{
    "Alias": "",
    "Fields" :
    [
        {
            "Name" : "",
            "Alias": "",
            "Value" : ""
        },
        ...
    ]
}

Default virtual layout:

{{this.fields[0].value}}

BACKLOG

Advanced CRM:

Toolbox - Liquid component tag for custom CRM fields

Add new item to toolbox:

• CRM
  • CRM Contact Custom Group

BACKLOG

Advanced CRM:

Plan restrictions

All functionality with advanced CRM custom groups should be available starting from Pro plan.

Add to menu:

• CRM
  • Advanced CRM Groups

BACKLOG

CRM Records as Datasource:

System property for allowing using crm contact records

Add new system property to CRM Contact record:

isDataUsingAllowed (bool)

• label: Allow listing my contact data in the CMS
• default value: false
• can be set to true via edit account form
  (Add this field to the edit account form html that generates by toolbox)
• can NOT be set to true via admin panel

CRM records that has this checkbox ticked ON will be allowed to:

• be assigned to module items (should help with the GDPR since this checkbox allows user to disallow using his record just by unchecking the checkbox on the profile page).
• be used by liquid component for retrieving and listing contacts.

• Add this property to the form builder, allowing to set it to TRUE on registration forms (http://prntscr.com/q89aht)

BACKLOG

CRM Records as Datasource:

Module item custom property - CRMRecord

Add new Module item property type:

CRM record

• property allows to assign any CRM record that has "isDataUsingAllowed=true"
• holds id of crm contact record (similar to datasource).
• switching "isDataUsingAllowed" to false should trigger removing that crm record id from all module items that have properties of CRM record type with that saved id.

BACKLOG

CRM Records as Datasource:

Liquid output of CRM records

Add new component tag component type:"CRMContacts":

Pattern:

{% component type:"CRMContacts", filterBy:"", filterValue:"", limit:"", offset:"", sortBy:"", sortOrder:"", collectionVariable:"", layout:"" %}

Component should filter, sort and return list of CRM contacts that has isDataUsingAllowed equal to true ONLY

• filterBy (not required) - CRM Contact property name to perform filtering by.
• filterValue (not required) - value to perform filtering by param set in filterBy. Similar to module component filtering.
• limit (not required) - number of tags to be rendered (Default value is 10)
• offset (not required) - number of contacts in the result list to skip retrieving start from (Default value is 0)
• sortBy (not required) - any contact system properties (Default value is FirstName)
• sortOrder (not required) - ASC or DESC (Default value is ASC)
• collectionVariable (not required) - works the same way as other modules.
• layout (not required) - path to FTP file that will contain layout content for the data.
  • If specified empty string - do not render anything.
  • If not specified at all - render default virtual layout.

Default virtual layout:

<ul>

{% for contact in this.items %}

<li>{{contact.FirstName}} {{contact.LastName}} - {{contact.Email}}</li>

{% endfor %}

</ul>

Item context:

{

"items" :

[

{

"id": 0,

"email": "",

"firstname": "",

"lastname": "",

"address": "",

"city": "",

"state": "",

"zipcode": "",

"country": "",

"site": "",

"phone": "",

"status": "",

"notes": "",

"createddatetime": "",

"updateddatetime": "",

},

...

]

}

BACKLOG

CRM Records as Datasource:

Toolbox - Liquid output of crm records

Add new item to toolbox

• CRM
  • CRM Contact List

BACKLOG

Ability To Parse JSON With Liquid

1) Add new component tag: component type:"json":

Pattern:

{% component type: "json", source_type:"[[source_type]]", source:"[[source]]", layout:"[[layout]]", collectionVariable:"[[collectionVariable]]" %}

• source_type (required param):
  • path
  • url
  • string
• source (required param):
  • path - any path to FTP file that contains JSON as content. Example: '/some/path/filename.json'
  • url - any internal or external URL that returns JSON response. Example: 'https://some.domain/some_api/'
  • string - JSON string. Example: '{"some" : "value"}'
• collectionVariable (not required) - works the same way as in other components.
• layout (not required) - path to FTP file that will contain layout content for the data.
  • If specified empty string - do not render anything.
  • If not specified at all - render default virtual layout.

Default virtual layout:

{{this}}

{{this}} variable contains the parsed json object.

If parse error occurred {{this}} will be NULL

2) Component added to Toolbox (https://prnt.sc/s2pmv2):

• Liquid Data
  • JSON Data

=================

Public Backlog item:

• https://www.treepl.co/public-backlog-state/request/ability-to-parse-json-with-liquid

BACKLOG

Extend URL slug max length

Allow slug max length to be 254 symbols instead of current 200

BACKLOG

Add shipping address to order (system fields)

1) Add shipping address as system fields to the order in the admin

Extend order model by adding shipping address as system fields http://prntscr.com/tet3te

Separate address to the following fields and allow editing via order edit operation:

• Shipping Address
• Shipping City
• Shipping State
• Shipping ZipCode
• Shipping country

2) Extend Order liquid object

Extend Order liquid object by adding following fields:

• shippingAddress
  • addressLine
  • city
  • state
  • zipCode
  • country

So they could be listed like

• {{this.order.shippingAddress.addressLine}}
• {{this.order.shippingAddress.zipCode}}
• etc

BACKLOG

Last sorting state saving for the module list view

Remember the latest sorting field and sorting direction for each module on list view http://prntscr.com/t97vsn

Once admin user comes back to the module items list view in the admin - the sorting should be the exact same as it was saved earlier.

BACKLOG

Re-send Invoice

1) Provide ability to re-send invoice email from the admin dashboard (on edit order page) to:
- Order creator/customer (‘Email Invoice’ button)

- Custom email (‘Send Test Email’ button): once clicked - shows text field to enter email address (pre-filled by current admin email)

BETA

Feature flags updates for v5.4

For Trial Sites:

Flags moved to internal section AND set to enabled:

• Advanced payment flow
• Advanced URL manager
• New liquid engine & nICE 2.0

For Live sites:

Flags move to internal section AND set to enabled:

• Advanced URL manager

BETA

Make reCaptcha to be required for users not logged in

1) Feature flag: Anti-spam protection

Enables logic restriction that doesn't allow to submit any web form for not logged in users if the form doesn't include reCAPTCHA (v2 or v3)

Apply restriction as part of validation if

• form has no payment fields (if has - no need for forced reCAPTCHA)
• user is not logged in (if user is logged in - no need for forced reCAPTCHA)

2) WARNING:

The flag will be force enabled in 5.5 release (but it still could be temporarily disabled for certain sites on demand).

So change your forms accordingly for 5.5 release.

And in 5.6 this logic will be applied permanently.

Bug

Url (and all other system properties) names should be restricted for custom properties of the module

When creating custom properties, for any module, using a name of any system property the property should not be created since such alias in use.

System should say “Property with specified name already exists”

THIS FLOW SHOULD WORK FOR ALL SYSTEM PROPERTIES

Bug

Verified domains to be case insensitive

Validate email domains using case insensitive comparison:

https://prnt.sc/t6vj5q

Bug

{{this}} in Snippet is incorrect

Snippet should contain the same object within this variable that is accessible outside snippet.

1. Create snippet and write {{this}} http://prntscr.com/sos6mn

2. Create a Page and output that snippet http://prntscr.com/sos7qe

3. Create another page and write {{this}}

Expected:

The only difference between those 2 pages should be only in additional “params” property available in snippet this output http://prntscr.com/sos9nf

Actual:

Properties of this object shown incorrectly http://prntscr.com/thgqkk

Bug

Treepl main CSS link position

Fixed to be prepended to the head section instead of append.

https://forum.treepl.co/t/treepl-ecommerce-css-link/1063