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