The OmCore road map

#35Adding pages, the page's parent to default to the selected page.

At present, when adding a new page to the site tree, the page's parent option is blank. This means that, unless a page is then set with a parent, the page will be placed in the root of the selected navigation group.

As it is a much simpler process to reset a page's parent setting then to have to use the site browser to select a page's parent, this option should be updated so that the new page's parent option will automatically populate with the currently selected page in the site tree. This way, to add a child page, you simply have to select the page in the site tree under which you wish to place the new page.

#20Rework content type options in site tree

When adding new content to a page, the select menus which list the content types are still structured using the old systems naming conventions. I.e. Site manager > Text editor. These need to be updated so that they're consistent with the new system's structure. I.e. Rename 'Registrants' to 'Customers'.

#37Bespoke data for modules

At present, modules can only store the data which the module has been developed to cater for.

When editing items in a module a new tab will allow extra fields to be placed on it, such as text fields, select menus, text editor etc. Once placed on the tab, the fields will appear when editing all items in the module. This data can then be incorporated into content types for presentation in the front end.

For example, you may want an extra photo for your products, or to link each product to a news article.

#36Section class names

At present page's can be assigned class names. This allows content of the page to then be targetted using CSS assigned to the class name. If you then want another page to also adopt the styles you simply assign it with the same class name.

This technique can be used to visually divide a site into sections. For example, you may want different sections of your site to be dinstinguished using colours, one section using red headings, and another using blue. To do this using page class names can be cumbersome as it requires each page to be assigned the class name.

Section class names will be an extension of the page class names, whereby the class name assigned to a page can be set to be inherited by the page's decendants. This way you only need to assign the class the root page of the section.

#2Item history

Previous versions of content will be stored allowing you to view historical information on who has edited the item and add the ability roll back data. It also adds a safety measure in the event of data loss.

#1Lock items when editing

There is currently a risk that if 2 users edit the same item at the same time it would result in some data loss. The solution will involve items becoming 'locked' to other users when being edited.

#38PNG resizing to support alpha channels

Currently if a PNG is uploaded to the system and automatically resized then any alpha channel is replaced with a flat black colour.

#41Match form fields to customers database columns

The problem

The customers database contains a range of columns for storing customer information. Forms in OmCore have the option to save new user submissions as new customers. If the form's field names do not exactly match the column names of the database then the data will not be saved. At present there is no way for the creator of the form to know the names of the columns which are available to use, and there may be the requirement to use field names which don't match those in the database but for the data to still be saved within a specific column.

The solution

The solution will be to allow associations to be set up between the form's field names and the customer table's column names. Here's how:

1. A select menu will list all of the columns in the customers table.
2. Selecting a column will display another select menu, adjacent to the first, which lists the form's fields.
3. Selecting a form field will create the association between the form field and the previously selected column.
4. On creating an association a new column select menu will be displayed to allow for another association, if required, to be set up.

When creating the form it will then be possible to simply look at the columns listed in the select menu to identify the names of the columns in the database. By matching the form's field names to those in the customers table there is no need to have to create associations in the first place.

#42New registrant confirmation

The problem

Currently the activation email sent to new registrants, using the registration form, is hard-coded in the system.

The solution

A new “Confirmation email” tab of the Registration Form content type, in the site tree, will allow the activation email's subject and body content to be edited using a text field and text editor respectively. The twig template system will allow dynamic content, such as username, password, first/last name data, to be inserted into the email.

#43Customer Activity Log

Currently all form submissions are logged against each customer, these are presented on the Activity tab when viewing a customer's details in the customers module.

We intend to extend this and create a generic Activity Log that will track a range of customer activities including registration, opt in/out, purchases, and form submissions.

These will be presented in a an easy to read table listed in date descending order.