Beta

Features moved out of Beta

These features work consistently now and have been implemented into the CMS:

• Advanced Search
• Date Time Management

NOTE: Any feature flag will go through this flow:

• Round #1 (sprint release) – released in beta features (disabled by default so it won’t crash anything on the live sites.
  Partners are able to see if it operates properly on those sites and report any issues for us to fix.
  Partner is able to turn off the feature himself instantly.
• Round #2 (1 or 2 sprints after round #1) – feature flag goes to internal section and set to true (checked).
  Partners are not able to uncheck it but can send a support ticket in case of some issues and we will disable it from our end and fix it
• Round #3 (1 or 2 sprints after round #2) – feature flag will be deleted.
  Old logic will be removed from the code.
  The result is that feature adopts the new behavior on a permanent basis.

Beta

New Liquid engine &nICE v2.0

New Liquid engine & nICE 2.0

+ nICE v2.0:

The ability to use style options like bold, italic, colors, etc in nICE editor interface.

New styles interface is available for all content except for module item properties that don’t have a field type of ‘multiline’ or ‘WYSIWYG’ (ie: date/time fields, single line string fields, etc).

NOTE: This feature requires valid HTML for proper nICE 2.0 operation in edit mode.

+ New Liquid engine:

IMPORTANT: After enabling this feature, please check all site's custom liquid and JS implementations.
In cases where you might output the collection variables as JSON (like ajax search result) the new Liquid engine renders the JSON object with camelCased property names.
Example:

The output will be different for old and new liquid engine:
http://prntscr.com/oh7ytj

Also, if you are using the {{params}} variable make sure you are using it via {{this.params}}. The names of the custom params will also be in camelCase http://prntscr.com/oh82n5

Forum discussion on the topic of params: https://forum.treepl.co/t/new-liquid-engine-changes-to-referencing-parameters-in-custom-layouts/517

This feature flag will be available in beta for 2 sprints and then also will be auto-enabled for all sites.

Beta

Multi-level Categories

Advanced multi-level categories

The feature allows creating multi-level categories.

+ New ‘ItemCategoryIdList’ property added to Liquid scope:

New property stores comma separated list of category IDs (existing category property stores list of category Names)

Existing: {{this['ItemCategories']}}

New: {{this['ItemCategoryIdList']}}

+ Convert Categories to nested categories

On appstart if categories wasn't previously converted, for each category:

• Get category name
• Split it by "/"
• Create new nested categories from split values

+ New interface when creating categories/subcategories

Design - http://prntscr.com/oh6ht2

Categories now sorted in the tree structure.

By this button: http://prntscr.com/nod8lh the user is able to create a new category.

The user is also able to create/remove/rename the category/subcategory clicking on this button: http://prntscr.com/nodeyz .

User is able to change the name of the category/subcategory: http://prntscr.com/noddvd .

If the user created/changed the name of the category/subcategory and clicks anywhere but not on this button: http://prntscr.com/nodg1b changes should not be saved.

+ Ability to create/edit categories using the new interface when within a module item

Design - http://prntscr.com/oh6i7v

If user wants to create/edit category tree by clicking here: http://prntscr.com/npvq9l the flow is the same as on the settings page.

If user wants to assign the category to the module there should be the dropdown: http://prntscr.com/npvqod where the level number will be indicated with (----).

+ Default Parent category setting

For modules where you have access to its properties ("Edit Module">"Item Properties">"Default Properties") There will be the ability to specify the parent category to be used when creating/editing module items.

The default selection is the Root category level (value -1). if set to any category, than only the subcategories of the set category will be available to the module items (in both the Category field and the pop-out side panel as a tree of categories when clicking ‘Add new category button’.

+ Change import/export format for categories.

Old format example:

• Cat 1,Cat 2,SubCat 1

New format example:

• /Cat 1;/Cat 2;/Cat 2/SubCat 1;

Change method type from "Get" to "Post"

+ Change logic for category filtration:

• if filterBy is ‘itemCategories’

• Read filterValue as fullName
• find category by fullName
• find items by ItemCategoryIdList property of the module using retrieved category id.

• if searching by ItemCategory - apply same logic as for filterBy

+ Addition of new component tag of type "categories"

Component pattern:

{% component type:"categories", parentCategory:"[[parentCategoryId]]", levelsDeep:"[[numberOfLevelsToRender]]", collectionVariable:"[[variableName]]" %}

• parentCategory (not required param) - id of the category to start selecting subcategories from.
• Default value for parentCategory = -1. Means start selecting categories from root.
• levelsDeep (not required param) - number of levels in-depth starting from parentCategory that need to be retrieved.
• Default value for levelsDeep = -1. Means render all levels in-depth.

Example:

{% component type:"categories", parentCategory:"111", levelsDeep:"2", collectionVariable:"myVar" %}

Renders virtual layout by pattern below:

<option value="[[itemContext.fullName]]">[["----" x (itemContext.level-1)]][[itemContext.name]]</option>

Liquid output example (of “myvar”):

{

"items": [

{

"NestingLevel": 2,

"FullName": "Cat 2/SubCat 1",

"Id": 112,

"Name": "----SubCat 1"

},{

"NestingLevel": 2,

"FullName": "Cat 2/SubCat 2",

"Id": 113,

"Name": "----SubCat 2"

}

]

}

NOTES: On generation of ‘search module form’ modification shown in ACCEPTANCE CRITERIA - see further below.

Replicate the same to ‘create module form’

Replicate the same to ‘edit module form’

+ Component Toolbox shows category tree

In the toolbox (for custom module, blogs, events, etc) when selecting filterBy ‘itemCategories’ - display options as flat tree in filterValue field in the format described below:

• <option> label: "Category" or "---- Sub Category" or "-------- Sub Sub Category" depending on the level of the category (the deepest level has the most "----" prefix in front of the category name).
• <option> value: "/category/sub category"

Backlog

New Email Accounts

Add Email accounts tab on live site edit page (in portal.treepl.co)

Design - http://prntscr.com/oh730f

Flow:

• Check if live site domain exists in Treepl’s Open SRS account.
• If exist – show email CRUD layout
• If not – try create domain in the Open SRC account

• On success - show email CRUD layout
• On fail – show error popup message and try again button.

Email CRUD layout provides ability to:

• Create email
• Create domain alias
• Create email alias
• View list of email accounts and domain aliases
• Shows storage of the particular email account
• Delete email accounts
• Delete domain alias
• Delete email alias
• Reset email password

Backlog

Contacts Import/Export flow

Import/Export flow.

Fields:
all contact fields:

• Id (ignore on import)
• First Name
• Last Name
• Email
• Address
• City
• State
• ZipCode
• Country
• Site
• Phone
• Status
• Notes
• Date Created
• Date Updated (ignore on import)
• Secure Zone
• Secure Zone Expiration Date
  Example:
  http://prntscr.com/o1wy67
  if there is no date in Secure Zone Expiration Date but there is secure zone name in Secure Zone field:
  - on create CRM contact; set 9999-Dec-31
  - on edit CRM contact; do not edit existing expiration date

Notes:

Only ‘Secure Zone’ and ’Secure Zone Expiration Date’ cells will be imported for those additional secure zone rows added under a contact’s record (with no email address present). All other cells will be ignored in these rows.

Backlog

Admin Roles - Import Contacts

Extend restrictions list for admin roles.
New option under ‘Contacts’:

• Can Import Contacts

If ’Can Import Contacts’ = false - disallow importing Contacts action for Admins with such roles.

Existing configured roles have this disabled by default.

Backlog

Multiple Workflows enabled on Business plan

Unlock Workflow notification Create / Read / Update / Delete operations for Business plan to enable multiple workflow capability. Now restricted only to having different Workflow Emails for those notification.

(Multiple Workflow Emails remain only on Pro/Pro+ plans)

Backlog

Ecommerce menu items

Set all sub items in Ecommerce menu as inactive:

eCommerce

• Products
• Catalogs
• Discount codes
• Gift vouchers
• Taxes
• Shipping options

Backlog

Data Source Property - Default Empty Option

Original issue:
https://forum.treepl.co/t/data-source-property-default-empty-option/473

For Custom Module Data Source fields, it was not possible to be set back to null/empty after a selection was assigned.

Now an empty ‘Please select’ option is available.

Backlog

Re-index module button

Added ability to re-index only one particular module http://prntscr.com/oh898g

Useful for selectively re-indexing specific modules only or to resolve possible issues with specific module search.

Bug

Force disabling from search engines for all trial sites

Force addition of <meta name="robots" content="noindex, nofollow"> meta tag (regardless of page property "Disable from search engines") for any page request under subdomain of *.treepl.co or *.trialsite.co

Bug

BUG: SEO Priority Default Setting

Original bug summary:

https://treepl.co/public-backlog-state/request/bug-seo-priority-default-setting

Custom Modules default SEO Priority is only visually applied in admin view and does not actually apply until SEO tab is saved.

Solution:

Apply the Default Priority field value to any newly created item (http://prntscr.com/nvztgl ):

- Front-end form

• always

- Admin add item form

• always

- Import process

• if priority column wasn't specified or cell is empty

Bug

BUG: {{this.member}} data does not output to system Invoice email

Original bug summary:

https://treepl.co/public-backlog-state/request/bug-raw-this-member-endraw-data-does-not-output-to-system-invoice-email

{{this.member}} data does not output to the system Invoice email layout.

Bug

Custom module - Content Template changed upon front-end update

Steps to reproduce:

1. Create form for updating item from front-end
2. Go to custom module settings and change default content template http://prntscr.com/o4qaoz
3. Go to item and set any template (not default and not the one that is selected as default in module settings in step 2).
4. Go to front-end and click button Update

Expected:

• Template should not be changed

Actual:

• template was changed http://prntscr.com/o4qaym

Bug

Advanced search - doesn't search in blog

Fixed the issue that reindex process wasn’t indexing the items that where located in “folder/group” items (like posts in blogs or pages under some page folders).

Bug

BUG: Spaces generated in form code

Original bug summary:

https://forum.treepl.co/t/bug-spaces-generated-in-form-code/474

Generated form code for Event and Payment fields had incorrect spaces in the HTML syntax.

Bug

Update item from front-end would clear info when update

Steps to reproduce:

1. Create module and item
2. Generate update item form
3. Remove from the html code any fields except of itemId
4. Place form to the page
5. Submit form from front end

Expected

• All fields sending via the form updates the item properties. All properties that AREN’T added to the form should NOT be updated

Actual

• All properties that AREN’T added to the form ERASES the content of those item’s properties.