Public Backlog

WebinOne announcements, releases, updates and achievements

v 3.0 Release date: 08 Jan, 2019

Full Release Notes

Backlog

Admin User Roles CRUD

Add ability to create, delete, update and view list of roles.

Each role detail layout provides a list of permissions based on the current site plan.

Backlog

Admin Users - permissions setup

Ability to set admin user role for every Admin User created.
Admin user can't setup role to themselves.

No admin user can edit/delete partner admin account.

Backlog

Admin menu configurator

Add ability to customize order, visibility and names of admin panel menu items.

Backlog

Change of custom menus and role restrictions with site plan upgrade/downgrade

  1. Plan Upgrade:
    1. Change site plan permission
  2. Plan Downgrade
    1. Change site plan permission
    2. Go through all admin user's roles and remove all permissions that is not exist in the current site plan permission
  3. New Module added
    1. Add new permission node to site plan permission
  4. Existing module deleted
    1. Remove permission node from site plan permission
  1. User Roles
    1. Go through all admin user's roles and remove permission for that module if such exists.

Backlog

Advanced admin search

Add ability to filter admin menu items by keyword

Backlog

{{this.formSubmissionData}} on thank you page

Added support for {{this.formSubmissionData}} to get access to formSubmissionData object the same way as now does {{formSubmissionData}}

{{formSubmissionData}} should also work as it does now for backward compatibility.

Custom thank you pages (by use of 'redirectURL' parameter) will also support both data tags.

Backlog

User friendly mailchimp error messages

Change "The resource submitted could not be validated. For field-specific details, see the 'errors' array." error message

http://prntscr.com/m2iqt3

To like:

"Validation error:

[Error key]: [error message]

..."

Backlog

System Pages and Emails default UI

Created folder in File Manager/FTP:

/cms-assets
Added here .css, .js, etc. that are needed for system pages and system emails.

Default system pages and emails on blank site include:

  • System pages
    • 404
    • Email Confirmation
    • Forbidden
    • Form Submission Results
    • Request Reset Password
    • Request Reset Password Result
    • Reset Password
    • Unauthorized
  • Galleries
    • Layout markup and js (with fancybox)
  • System Emails
    • Password Retrieve Email
    • Secure Zone Login Details
    • Workflow Notification
    • Confirm Email Notification
  • Forms
    • Email Notification (autoresponder)

Bug

Author column duplication in export bug

Repro Steps

  1. Go to any custom module.
  2. Enable authors in Properties section
  3. Go to items list
  4. Create item
  5. Call export
  6. Call export
  7. Call export

Expected

  • All 3 export files should contain only one Author column

Actual

  • Each next file has one more Author header column

Bug

Custom module search bug

Search by custom module form requires &paginatedModule=[[module_id]] param in order to paginate

Repro Steps

  • Go to page
  • Insert module search form via toolbox (check Display Pagination checkbox)
  • Save the page
  • Go to page
  • Click search
  • Go to second page
  • Remove &paginatedModule=[[module_id]] from the URL

Expected:

  • &prop_ModuleId=[[module_id]] is enough to determine module

Actual:

  • &prop_ModuleId=[[module_id]] is ignored, still waiting for &paginatedModule=[[module_id]]

Show more less
New Feature

Admin Menu Configurator

Ability to customize order and names of admin panel menu items.
  • Admin Panel
New Feature

Admin User Custom Restrictions

Ability to set custom restrictions for every Admin User created via roles.
  • Admin Panel
New Feature

Advanced Admin Search

Quick search of admin menu items.
  • Admin Panel
  • UI/UX
Improvement

_is_mobile_ Liquid Detection

Suggestion for {{request.request_data.is_mobile}} to become {{request.request_data.device_class}} with the output being 'mobile|tablet|desktop|...' as this will provide greater flexibility and future scalability as more device types could be added in over time. eg: 'tv|watch|glasses|car|spaceship|...'. Much like in BC we have {{globals.visitor.deviceClass}} giving us 'desktop|tablet|phone'.


The {{request.request_data.is_mobile}} just gives us a 'true|false' to whether it's mobile or not. I feel that the BC...
  • Liquid