Beta

Implementation of previous beta items

• Advanced Module Import/Export
• Improved module search

Features above work constantly now and have been implemented.

Beta

Date and time fields

Date Time Management:

Allows choosing time in date fields on custom and system modules.

Backlog

Set time on add/edit module items

1) Provide ability to set time on date properties in the admin.

Fields are:

• system fields

• Release Date
• Expiration Date
• Event Start Date
• Event End Date

• custom fields

• any field with type = "Date Time"

2) Set default time for the date fields above if time not set - use 00:00:00 as default time when saving any of datetime properties above.

Backlog

Save time on import/export items

Use time from the date fields in the excel columns to set date time in the timezone of the site.

Fields are:

• system fields

• Release Date
• Expiration Date
• Event Start Date
• Event End Date

• custom fields

• any field with type = "Date Time"

If not set - use 00:00:00 as default time.

Backlog

Save time on create/update item (user submitted)

1) Save selected time when creating/updating module item via user submitted items.

2) Change generated input form (via toolbox) from date to datetime-local input

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local

If not set to the datetime field - use 00:00:00 as default time.

Backlog

Event calendar redo for date time

Modify calendar JS to use time part of the event start and event end date instead of relying on forcing 00:00:00 to the start date and 23:59:59 to the end date.

Backlog

Liquid output for displaying timezone

Add new property to request object:

"timezone" :

{

    "label" : "string",

    "offset" : int

}

Where label is a string value of the timezone name and offset is the difference in hours between UTC and current timezone

Example Output:
"timezone" :
{

    "label" : "(UTC-06:00) Central Time (US & Canada)",

    "offset" : -6

}

Example Liquid Usage:

{{request.timezone.offset}}

Would give value: -6

Backlog

Duplicating of existing module

Duplicate module with:

• settings
• default properties
• custom properties
• layouts

Allow selecting new name and url when clicking duplicate button.

Duplicate button located on Module Settings tab.

http://prntscr.com/o3wjp2

Plan restriction for duplicate Custom Module: Pro+

Backlog

WYSIWYG and ACE editor for form autoresponder with switcher

Add WYSIWYG and ACE editor options to the Form -> Settings -> Autoresponder body.

System Flow:

When user saves Settings - last selected editor should be saved as well.

When user comes to the form setting page - last chosen editor should be applied to the Body field.

If no editor was saved for the Form setting section - ACE editor should be chosen by default.

Chosen editor should be saved to the particular form, not for all forms in general.

When user clicks save the whole Settings section:

• If WYSIWYG editor chosen AND previously was chosen ACE - show confirm message: Switching to WYSIWYG may corrupt some of your data. Confirm?
  - if clicked OK - continue saving process.
  - if clicked cancel - reject saving process.

Bug

(HOTFIX) Calendar toolbox builder - default options depended in Advanced Search flag

If Advanced search feature flag is enabled:

• All - value = "0"
• Ungrouped - value = "-1"

Old logic (if flag is off) :

• All - value = "-1"
• Ungrouped - value = "[[hiddenRootItemID]]"

http://prntscr.com/nux3hw

Bug

(HOTFIX) Calendar for Advanced search feature flag beta param

Modify calendar js and include file to use beta feature flag param.

Set param to 1 if Advanced search feature flag is on.

Bug

(HOTFIX) Add Image Bug (not adding actual uploaded image path)

When adding an image to an image field using the image manager it would add an incorrect image reference.

Bug

URL Redirect - when using .html

Fix URL redirect to recognize such url’s ("/myurl.html" and "/myurl") as different urls.

The fix allows creating redirect like

"/myurl.html" => "/myurl"

Bug

BUGS: User-Submitted Custom Module Items

BUG 1:
Not sure that user-submitted CM items are honouring site timezone for release date and expiry date IN THE WEB FORM RESPONSE - actual dates in the admin and when later rendering on site are correct.
(I’m testing with a Sydney timezone set)
Release date is always different.
Expiry is different when the date is set in the Create Item form, but not when ‘number of days till expiry’ is used or when left as default/no date set.

BUG 2:
User-submitted items do not honour the expiry date ‘number of days’ value set in the modules default properties.

BUG 3:
Expiry date fields are generated in the Create/Update Item forms even if expiry date is disabled from the CM default properties. (although they are removed if turned off from the Settings > Site User Permissions - but I’d think it should work the same in both cases?)

BUG 4:
Expiration Date input in the Create/Update Item forms is added as a type=“text” input - suggest changing to a type=“date” (as per custom properties dateTime fields)"