BACKLOG

Favorites

1) Add/remove from favorites actions

Add two GET URLS (public api), one for “add” and one for “remove”, for logged in users with `itemId` as parameter (id of module item that should be added to favorites)

2) Add component type:"favorites":

{% component type:"favorites", source:"[[moduleIdentifier]]", itemId:"[[itemId]]", includeItemData:"[[includeItemData]]", limit:"[[limit]]", collectionVariable:"", layout:"" %}

• `moduleIdentifier` (required) - moduleName or moduleId.
• `itemId` (not required) - id of the module item
• `limit` (not required) Default=ALL - number of items to be rendered
• `collectionVariable` (not required) - works the same way as 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 (see design link below).
• `includeItemData` (not required)- true/false boolean. Default=false

Default sorting by `CreatedDateTime` DESC.

Single item context is:

• Id
• FavoritesInfo
  • IsFavorite
  • CreatedDateTime
  • AddToFavoritesURL
  • RemoveFromFavoritesURL

(If `includeItemData` == true, the modules typical data will be included along with the above “Favorites” data.

3) Add component to toolbox, under: “CRM” > “Favorites”

4) Add default JS and styles for favorites:

Once added to favorites - change favorite icon appearance and switch URL from ’add to favorites’ to ’remove from favorites’.

Once removed from favorites - change favorite icon appearance and switch URL from ’remove from favorites’ to ’add to favorites’.

If user is not logged in and clicks Add or Remove from favorites - redirect them to system error page with the following data:

• {{this.ErrorType}}
  • FavoritesRequiresLogin
• {{this.ErrorMessage}}
  • You need to be logged in to the site in order to add this item to your favorites list.

Apply ability to request add and remove from favorites API urls with GET param `jsonResponse=true`.

If `true` - return JSON response with error details (status code 401).

Otherwise - redirect to error page with the above described type and message.

DESIGN: https://invis.io/VEZ0HS6A8YF

BACKLOG

eWAY and Stripe improvements

1) Add to data passed to eWay:

• First Name
• Last Name
• Address
• Postcode

2) Change ”Invoice Description” to <form name>

3) Add data passed to Stripe (only for one-time payment):

• First Name
• Last Name
• Address
• Postcode

4) Change ”Description” to <form name>

BACKLOG

Show Product URL based on current catalog

On product detail show URL based on catalog that it’s contained in.

Modify component type module logic:

If filtered by `parentId` add `this.url` value based on the parent determined by `parentId`, eg:

• Item has 3 parents:
  • Parent_1 (ID 11) (shown by default)
  • Parent_2 (ID 22)
  • Parent_3 (ID 33)
• When {% component type:"module" %} for the example item this object should have
  • {{this.Url}} == "/parent1"
• When {% component type:"module", filterBy:"parentId", filterValue:"22" %} for the example item this object should have
  • {{this.Url}} == "/parent2"
• When {% component type:"module", searchScope:'{"parentId": "33"}' %} for the example item this object should have
  • {{this.Url}} == "/parent3"

BACKLOG

Customize Analytics

1) Analytics Customization

• https://prnt.sc/x8ckpz
• https://prnt.sc/x8c7mt
• delete chart
• reorder chart using drag and drop
• edit single chart (see point 2 below)
• Ability to restore analytics to default (https://prnt.sc/x8c9yz)
• ability to add chart to the analytics layout

2) Single Chart customization

• https://prnt.sc/x8c3hy
• change width via col size dropdown
• show/hide tabs buttons (for tabbed charts)
• default period of days selector
• Chart title customization

3) Add Chart to analytics

• https://prnt.sc/x8ccae
• clicking add - creates empty chart panel
• clicking add button inside - opens chart selector (https://prnt.sc/x8cddk)

4) Restrictions

Feature available on PRO Plan and higher.

BACKLOG

Copy File URL to clipboard

Add ability to get file’s URL in file manager and file manager toolbox.

• Сopy File URL (relative URL)
• Preview In New Tab

DESIGN: https://invis.io/VTYEHO7Z6NJ

From Forum

BACKLOG

Wording change on event bookings

Rename following wording in the CMS:

• Module -> Settings -> Advanced Settings
  • “Enable subscription” to ”Enable bookings” (http://prntscr.com/vxn4mi)
• Event -> Details:
  • “SUBSCRIPTIONS” tab renamed to ”BOOKINGS” (http://prntscr.com/vxmw13)
    • Table column ”Subscribed Date” to ”Booking Date”
    • Excel export table column (on import - react on both new and old name)
      - “Subscribed Date” to ”Booking Date”
      - “Allow Multiple Subscription Per Email” to ”Allow Multiple Bookings Per Email”
• Toolbox -> Events
  • Toolbox item name ”Event Subscription Form” to ”Event Booking Form”
  • Field Name ”Event Subscription Form” to ”Event Booking Form” (http://prntscr.com/vxn1ru)
• Form
  • Default user field title ”Accept Event Subscription” to ”Accept Event Booking” (http://prntscr.com/vxn41h)
• CRM -> Event bookings
  • Title ”Booking Subscriptions” to ”Event Bookings” (http://prntscr.com/vxn7gx)

BACKLOG

Drop shipping feature improvement

Feedback description:

When a visitor makes an order for several different items on one and the same order the system will create one purchase-order for each item even if they all are supplied by one and the same supplier. This obviously causes a lot of extra work for the suppliers. BC consolidated several items to one and the same purchase-order and only split the order if there were multiple suppliers to supply the items on the order.

Solution:

Consolidate several items to one supplier email for the same order instead of sending supplier email for each product.

Bambora Payment Gateway

Bambora Improvements (patch v5.8.1)

Design: http://prntscr.com/vljvo7

1) Implement Payment window modes (payment gateway settings page):

• redirect (already implemented only method)
• modal
• inline
  

Bambora Documentation:

https://developer.bambora.com/europe/...

2) Implement "immediateredirecttoaccept" setting:

When the payment has gone through you end up on a "success" page on the bambora site and you can then click to go back to the Treepl site with the receipt.
This can be passed so you don't see that page but go directly to the Treepl receipt page via the "immediateredirecttoaccept" parameter.

Bambora Documentation:

https://developer.bambora.com/europe/...

3) Language control settings

Provide possibility to select the language for the payment window.

Bambora Documentation:

https://developer.bambora.com/europe/...

4) Add transaction ID to the list view of the order (and allow search).

eg: http://prntscr.com/vikmzm

Misc

Admin UI: Orders pagination (patch v5.8.1)

Improve Pagination speed (CRM -> Orders)

Direct Billing

Invoices for portal payments (patch v5.8.2)

For direct billing with commissions:

• Add billing address and personal details fields to the CMS billing page in order to add them to the invoice.
• Make them required.
• Send Invoice to the payer instead of the Agency user.

Feedback Task

Set 404, 403 and 401 status codes when showing appropriate system pages

Implement server responses for 404, 403 and 401 statuses to set appropriate status codes and at the same time still display appropriate System Pages content.

Feedback Task

Admin Proof Read/Suggestions (Part 2)

Original Source: https://docs.google.com/document/...

12. [ ✔] In the “Form Builder” options, perhaps adjust the form ‘Type’ display names an provide a short explainer, eg
14. [✔ ] In Secure Zones, when setting “Membership Renewal Rate”, perhaps change the values from “Day, Week, Month, Year” to “Daily, Weekly, Monthly, Yearly”
23. [ ✔] On the Product settings tab, suggest changing “Max Downloads Allowed” to “Maximum Downloads Allowed” (for consistency)
30. [ ✔] For ALL module ‘Layouts’ tab, perhaps remove the redundant “Create New...” from the “CREATE NEW” dropdown option. Two example
31. [ ✔] For the Products/Catalogs “Layouts” tab, consider removing the ‘s’ from headings “Catalogs Layouts” and “Products Layouts” to just “Catalog Layouts” and “Product Layouts”
33. [ ✔] Consider adjusting “Discount Codes” menu item and headers to title-case
34. [ ✔] Consider adjusting “Gift vouchers” and “Shipping options” to title-case in the main admin menu
36. [ ✔] Under “eCommerce” > “Settings”, consider adjusting headings and labels to title-case. Also, ‘lifetime’ is one word so change “Shopping cart life time in hours” to “Shopping Cart Lifetime in Hours”
38. [✔ ] Under “Reports” > “Custom Reports”, could the list display more human readable ‘Type’ values? Ie: “Contacts and Event Bookings” instead of “ContactAndEventBookings”
40. [✔ ] Under “Reports” > “Custom Reports”, when editing a Report, under the ‘Fields’ tab consider adjusting some letter cases (“Id” should be “ID” if possible) and perhaps change “E-mail” to “Email” for consistency.
Assuming these changes will then flow through to the report column headers.

Public Request

Custom Client Notes For Custom Fields

Source:

https://treepl.co/...

Description:

New 'Notes' field against any custom field created in the admin. It would display next to the field when clients are creating Custom Module items and could provide additional info to help them when entering content.

For example: with an image field, the note might read "This image is displayed as the thumbnail on your Team Members page and ideally should be portrait orientation and at least 500px wide".

The note could perhaps be hidden under a help/info icon to keep the layout clean.

On property add/edit form:

Allow add notes (https://projects.invisionapp.com/...)

On module item add/edit form:

Display notes when hover tooltip icons (https://projects.invisionapp.com/...)

Note:

Add notes to `module` export/import flow.

Public Request

Set Custom Icons For Nested Module Items In Tree View

Source:

https://treepl.co/...

Source Description:

Provide ability to change icon of the item in tree view (http://prntscr.com/vu9h50)

• Add icon field to the `module` > `settings` page http://prntscr.com/vuhivv.
  Provide ability to choose icon from the system or custom library.
• Store icons in /admin-assets system folder. Store folder outside FTP folders.
• Provide ability to add icon to the icons custom library (on Admin menu configurator page). Design: https://invis.io/S6ZFRJWRNJG
  Suggested icon dimensions and extension: 24x24px, SVG
• Change icons display logic on module items tree view
  • if module has custom icon - show it instead of "File" or "Folder" icon
  • else - show icon as previously:
    - if module is Parent module - "Folder" icon
    - if module is Child module - "File" icon

Feedback Task

Improve GDPR control, Contacts and advanced CRM groups

1) Add new Group to `Settings` -> `Misc`

• GDPR (“Allow listing CRM contacts data” True/false boolean)

2) Logic

If ”Allow listing crm contacts data” == true - discard "Allow listing my contact data in the CMS" checkbox behavior and always allow use all contact data:

• via components
  • {% component type: "CRMContacts" %}
  • {% component type: "CRMCustomGroup" %}
  • {% component type: "CRMContactCustomGroup" %}
• in the admin CRM data pickers

3) Components logic extending

Add includeSecureZonesInfo: "true" param to {% component type: "CRMContacts" %}

If not set - default value is false

Also add it to the toolbox.

If true - add following object to item context (similar to what we have in {{request.currentmember}}):

securezones": [

    {

        "id": 1,

        "name": "Member Only Area",

        "landingpageid": null,

        "createddatetime": "2020-10-20T14:59:54.347",

        "updateddatetime": "2020-11-12T16:07:27.113",

        "expirydatetime": "9999-12-31T06:00:00",

        "ExpiryOption": null,

        "ExpiryAfter": null,

        "AccessType": 0,

        "Plans": null,

        "CountPaidSubscribers": 0

    },

Feedback Task

Admin UI changes

Task list:

• Add site Name and User Name to the header (https://invis.io/N5ZHIBBCKZJ)
• Add notifications indicator with description in tooltip http://prntscr.com/vvmpzk
• Fix datasource search in datasource pickers (search by `contains` rule instead of the `name starts with` - https://prnt.sc/vv8pm7)
• Sort datasource items alphabetically in datasource pickers (https://prnt.sc/vv8pau)
• Add button that will trigger sort all module tags alphabetically (https://prnt.sc/vv8q36)
  Add confirmation popup in order to prevent accidentally sorting.
• Add loader and notification on:
  • Import module items
  • Export module items
  • Duplicate module item
  • Designs:
    - https://invis.io/FJZHI9XDE3B
    
    - https://prnt.sc/vv907c - blinking circle and message that shows what process is currently working
    
    - https://prnt.sc/vv910x - message that shows when you try to close the tab where background process is working
    
• Add to `Settings` -> `Misc` ability to switch off warning message (https://prnt.sc/vv92oq) when you switch between wysiwyg and ACE editors (https://prnt.sc/vv934e)
  Default value is false
• Improve tree view of Gallery/Slider modules on all sites:
  - remove `url` and `template` columns
  - add `image` column

Public Request

"Already Taken" URL Validation

Source:

https://treepl.co/...

Description:

Validation warning for general URL conflicts before saving item. ie: for Pages and other items not influenced by the Advanced URL Manager.

1) Update `Settings` -> `Misc` in group “Admin Panel Settings” with new setting “Disable autocomplete for already taken URL slugs” (default is ‘false’)

2) Logic

If `true` - do not add `-1` to the slug on save.

Throw validation error message "Warning: Duplicate URL"

If false - logic should be as it was earlier.

Public Request

Add Default Styling For Pagination

Source:

https://treepl.co/...

Description:

Currently pagination outputs raw unordered list.

Apply some default formatting to remove the bullets from the list and make it horizontal. Also by default it would be nice to truncate the pagination with “…” and show the last page if there are over 5 pages.

If we really want to get fancy we could make the default styling along these lines.
https://prnt.sc/vv8ivx

1) Component param

Add param to component type `module` and `module_of_member`

• styledPagination : "true"
• default value is false
• if true - show new pagination structure instead of old one

2) Toolbox

• Show under ”Display Pagination”
• if checked - show new pagination structure instead of old one
• Hide if ”Display pagination” is false
• Set default value to true.
  But reflect in component string only if display pagination is true

Applies to the following modules:

• Custom module (Groups and Item lists)
• Blogs (Groups and Item lists)
• Gallery/Slider (Groups and Item lists)
• FAQ's (Groups and Item lists)
• Banners (Groups and Item lists)
• Authors
• Events (Groups and Item lists)
• eCommerce (Catalogs and Product lists)

Public Request

Small UI tweak: Add Icons To Items Under "Content" Section

Source:

https://treepl.co/...

Description:

Implement the icons in “Content” section that are already under the components insertion list.
https://prnt.sc/vtq0wq

All other icons on the 2nd level should remain the same.

Apply it to all default menus. Leave custom menus as is.

Design:

https://invis.io/P2ZFPCZZGAX

Public Request

Pages/Template/General Editing Window

Source:

https://treepl.co/...

Description:

Make the editing area fill the vertical space in the browser window.
https://prnt.sc/vv8k25

Public Request

Recent Item Section

Source:

https://treepl.co/...

Description:

A ‘Recent Items’ section to quickly go back into last page/module you were in, without having to navigate back to that page.

Functionality

• Store history in session storage.
• Add to visited pages recent item history. If the page is already in the history - move it up in the history list (instead of adding duplicate history item).
• Remember 10 last visited pages.

DESIGN

https://projects.invisionapp.com/share/...

Feedback Task

Grouping product in toolbox improvement

Show `this.id` as first option of ”Filter Value” field for following components in toolbox (show it before datasource loading process occurs)

Ecommerce:

• Related Products
• Grouped Products
• Product Attributes
• Item Quantity Field
• Add to Cart Button
• Buy Now Button

IF it's selected or NO item selected - show "{{this.id}}" as value

http://prntscr.com/vpx6xu

http://prntscr.com/vpx8no

Feedback Task

Forms email aggregator

Add new setting to `Form` -> `Settings`:

• Send Secure Zone Login Details Email (default: true)
• If enabled - don't send ”Secure Zone Login Details” system email on secure zone subscription form submit

Add new setting to `Form` -> `Settings`

• Send Confirm Email Notification (default: true)

Add liquid variables of ”Confirm Email Notification” to the scope of the following system emails:

• Invoice
  • this.EmailConfirmationUrl
  • + Secure Zone Login Details variables
• Secure Zone Login Details
  • this.EmailConfirmationUrl
    (set empty string as value if no confirmation required [ie: if user is already confirmed])

Feedback Task

CRM -> Bookings: Export to Excel to be filtered by form name?

Source

https://forum.treepl.co/...

Improve Bookings export (https://prnt.sc/vv97ic)

• Improve ”Form Name” selector (multiselect)
  • all forms (default)
  • manually subscribed
  • form list...
• Add ”Event” selector (multiselect)
  • all events (default)
  • event list...

Update exporting logic so it will retrieve bookings based on selected forms and events

BUG

Infinity redirect on login to Portal

Fix infinity redirect on SSO login to Portal

BUG

Toolbox bug in event group Component

https://forum.treepl.co/...

BACKLOG

PORTAL:

Portal restructure

1) Rename Menu items

Change following:

• ‘My Details’ to ’My Settings’
• ‘Backlog’ to ’Public Backlog’

Split Menu in two parts. Set to bottom menu following items:

• Public Backlog
• Documentation
• Pricing For Resellers

Change Icons for

• My Settings
• Pricing For Resellers
• Projects / Services
• Support

2) Restrictions

Restrict commissions for Agency role only

Show prices that include commissions on the Treepl CMS sites in direct billing page

DO NOT include commissions if clicking pay from the portal.

3) FTP credentials tab

Create FTP under trialsite.co subdomain

Show host and username under ’FTP credentials’ tab

https://prnt.sc/vk4elt

BACKLOG

PORTAL:

Direct Billing (commissions)

1) Add “Commissions” tab to ’My Settings’

Design: https://invis.io/SDZC33JMHBA

Settings:

• Default Commission Value (validate numbers only, range: 0 - 900)
• My PayPal Email
• Resend Verification button
  • show only if current paypal email is not verified.
  • clicking on the button should resend ’paypal email verification’ email

Once form is saved - send ’paypal email verification’ email with the confirm button.

Once confirm button is clicked - mark paypal email as verified.

• If error occured while confirmation - show system page with error text
• else if OK - show success page and link to trial sites list page.

DO NOT SEND commissions to paypal emails until they are verified (trigger Payment error)

2) Add commission tab to site edit page

Add tab that will allow to setup commission for the site for monthly and annually subscriptions.

Settings:

• Commission Type (dropdown)
  • Percentage (default)
  • Value
• Commission Value (validate numbers only)
  • ranges for ‘Value’ type:
    0 - [value that gives 5000 in Your client Pays]
  • ranges for ‘Percent’ type:
    0 - [percent value that gives 5000 in Your client Pays]
  • default value from the ’MySettings’ -> ‘Commissions’ -> ’Default Commission Value’

Calculated summary should follow logic as described in this spreadsheet (for display purposes use 4.4% fee per transaction since it is the biggest one that may be charged):

Spreadsheet

Algorithm

• When receiving payment - determine the [transaction fee percent].
• Calculate [treepl part] as:
  [Original treepl price] * (1-[transaction fee percent]) - 0.30 (per transaction value part of the fee)
• Calculate [reseller's part] as:
  [received amount] - [treepl part] - 0.25 (standard fee for sending money from one paypal account to another)
• Send [reseller's part] to the PayPal Email:

• if ’Payment Error’ occurs:
  send system email to support@treepl.co:
  Subject: “Commission sending error”
  Content: Should contain [reseller's part] price, PayPal email, error info, date, site id and url
• else:
  Send an Invoice to the payer

Design:

Design

BACKLOG

PORTAL:

Branded subdomains

1) ‘My Settings’ -> ‘Domains’ tab

Add Domains tab to My Settings page

Design: http://prntscr.com/vlj9g3

Provide ability to:

• add domain:
  Create hosted zone in this step.
  Once created successfully - show ’Success’ state.
  Otherwise ‘Pending’ state.

• delete domain
  

2) ’My Settings’ -> ‘Domains’ tab -> ‘domain details’ page

Show 3 tabs:

• Custom records

• Here you can add/edit/delete any A, CNAME, MX, TXT records that you want

• NS and SOA records

• Read-only tab for display purposes only.

• Treepl Sites records

• Read-only tab for display purposes only.
• Shows all records that Treepl Portal creates for all Treepl sites under this branded domain.

3) Restrictions

Restrict access to ’Partners’ and ’Agencies’ only.

Allow ’Partners’ and ’Agencies’ to have:

• 1 branded subdomain for ’Partner’
• up to 3 branded subdomains for ’Agency’

Disallow ’My Settings’ -> ‘Domains’ tab for portal users

4) Add user role indication

Provide role indication icon and tooltip near user email.

Design: http://prntscr.com/vlj6j8

BACKLOG

Bambora Improvements

1) Implement Payment window modes

Design: http://prntscr.com/vljvo7

Implement Payment window as:

• redirect (already implemented only method)
• modal
• inline

Bambora Documentation:

checkout-integration

2) Implement "immediateredirecttoaccept" setting

When the payment has gone through you end up on a "success" page on the bambora site and you can then click to go back to the Treepl site with the receipt.
This can be passed so you don't see that page but go directly to the Treepl receipt page via the "immediateredirecttoaccept" parameter.

Provide ability to choose this flow in bambora payment gateway settings and implement the appropriate logic.

Bambora Documentation:

checkout#operation-sessions

3) Language control settings

Provide possibility to select the language for the payment window.

Bambora Documentation:

checkout-settings

4) Add transaction ID to the list view of the order.

Provide ability to search by it http://prntscr.com/vikmzm

BACKLOG

Admin UI: CRM -> Orders pagination improvement

Admin UI speed improvement on CRM -> Orders page.

Improve pagination in order to return order list faster.

BUG

{% component type: "shopping_cart" %}
Layout and collectionVariable params behavior fix

If you add `collectionVariable` param to the component the layout doesn’t render in the following cases:

• When Layout param is missing (should render default layout)
• When layout param is present but value refers to the layout file

NOTE:

You may have such kind of components in you code ({% component type:"shopping_cart", collectionVariable:"shoppingCartData" %}) that by mistake may miss the layout:"" param that stops component from rendering the default layout but still show no default layout (because of the current bug) .
You need to add missed layout:"" param to such components in order to fix incorrect implementation of the component.

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

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