Import feature Issue

Hello.

I have several content types defined in my October CMS project, using Tailor blueprints. The import/export functionality works as expected, except by a couple of fields that never get included (not even listed in the GUI) during the import or export process. Both are date/time fields (datepicker), and belong to a mixin content type, that is later used in several other content definitions.

These are the blueprints:

The mixin:


uuid: 3db896b6-10c0-46ff-bbb9-75e8280f8ffc
handle: Content\BasicData
type: mixin
name: Basic Data

fields:
    status:
        tab: Meta Data
        label: Status
        type: dropdown
        options:
             published: Published
             draft: Draft
             pending: Pending Review
        emptyOption: -- no status --
        default: draft
        validation:
                    -required  
    language:
        tab: Meta Data
        label: Language
        type: dropdown
        options:
             es: Spanish
             en: English
        emptyOption: -- no language --
        default: en
        validation:
                    -required
    pub_date:
         tab: Meta Data
         label: Publish Time
         type: datepicker
         mode: datetime
         default: now
         validation:
                    -required
    rev_date:
         tab: Meta Data
         label: Revision Time
         type: datepicker
         mode: datetime  
         default: now 
         validation:
                    -required

Example content type:


uuid: 0195da16-262d-425a-997e-8cc243dd2522
handle: Content\Question
type: stream
name: Question of the day
drafts: false

navigation:
    icon: icon-question
    parent: Content\BlogPost
    order: 109

fields:

    basic_data_fields:
        tab: Meta Data
        type: mixin
        source: Content\BasicData
    date:
        tab: Meta Data
        type: text
        label: Month and date
        validation:
                    -required 
    author:
        tab: Meta Data
        label: Author
        type: entries
        maxItems: 1
        source: Content\Author  
    main_image:
        tab: Meta Data
        label: Main image
        type: fileupload
        mode: image
        maxFiles: 1
    content:
        tab: Content
        label: Full text
        type: richeditor
        span: adaptive
        validation:
                    -required

Any suggestions will be greatly appreciated.

It seems there is a bug in October CMS export functionality.

Steps to reproduce:

  1. Create a basic Tailor blueprint (stream), with one field of type “datepicker” and execute migration.

  2. Enter the backend and insert some records in the previously created content type.

  3. Click the “Export” button. The date field is not even available in the list of fields. Only the internal fields appear (id, slug, etc.).

The date/time field is not even available when filtering the columns of the corresponding content type.

Just to follow up here: You’re right, datepicker support is limited in Tailor at the moment.

A datepicker field has been registered in OC v3.3.15. This adds a list column, scope and registers the field in the database as a timestamp. Adding it as a column also includes it in the export and import screens.

Thanks for the update.

I will wait for v3.3.15 then.