46cl / wp-custom-fields Goto Github PK

From @nesk on July 23, 2015 15:12

We should be able to remove:

• A media in an upload box.
• A link in a post box.

Copied from original issue: 46cl/wp-boilerplate#19

From @nesk on July 23, 2015 15:5

Add CSS classes to the generated HTML elements, allowing to easily target them in CSS.

Copied from original issue: 46cl/wp-boilerplate#18

The boxes crash on corrupted data, instead of that they should be displayed as if they were provided with empty data.

From @nesk on July 23, 2015 14:38

For example, a PDF should display a nice icon with the filename below.

Copied from original issue: 46cl/wp-boilerplate#13

This is required to avoid a simple scenario:

1. A user opens the page to edit a post.
2. The page loads, then the custom fields start initializing.
3. During initialization, the user clicks on Update or Publish.
4. The custom fields stop initializing, the input used to submit their data isn't created or filled and the post is submitted with empty custom fields.
5. The custom fields data is lost.

By deferring the click events on the Update/Publish button, we could avoid this. Also, a better security would be to implement #8.

From @nesk on July 23, 2015 15:21

The $settings parameter in the wp_editor() function should be overridable.

Copied from original issue: 46cl/wp-boilerplate#24

If a color format is specified, the output is always rgb instead of being the specified format.

From @nesk on July 27, 2015 15:27

Copied from original issue: 46cl/wp-boilerplate#33

From @nesk on July 23, 2015 15:36

Copied from original issue: 46cl/wp-boilerplate#29

The API should evolve to classes, thus providing the same API whether you use sequential boxes or not. Currently, here's how you initialize a post box and sequential boxes containing a post box:

// A post box
Qscl\CustomFields\CustomFields::post($postName, $postData, $postOptions);

// Sequential boxes containing a post box:
Qscl\CustomFields\CustomFields::sequential(
    $seqName,
    $seqData,
    array(

        array(
            'type' => 'post',
            'name' => $postName,
            'options' => $postOptions
        )

    ),
    $seqOptions
);

Changing to class instantiations will clarify the API:

// A post box
new Qscl\CustomFields\PostBox($postName, $postOptions, $postData);

// Sequential boxes containing a post box:
new Qscl\CustomFields\SequentialBoxes(
    $seqName,
    $seqData,
    $seqOptions,
    array(
        new Qscl\CustomFields\PostBox($postName, $postOptions)
    )
);

From @nesk on July 23, 2015 15:32

The CSS should be improved for the classic layout and the drag&drop feature should be disabled.

Copied from original issue: 46cl/wp-boilerplate#26

From @nesk on July 23, 2015 15:33

Copied from original issue: 46cl/wp-boilerplate#27