Standalone editor and Dates not working

Standalone editor and Dates not working

wannbergwannberg Posts: 11Questions: 3Answers: 0
edited February 2015 in Bug reports

Not sure if I have something wrong with my code, but this is the scenario:

I populated a section of my page with data in which I am using the standalone editor to edit. The issue is when I edit a date field, the date doesn't show up in the editor form. If I change the editor field to type text, it populates the editor form and then if I change it back to type date then the form field doesn't show up again.

It appears that a type of date doesn't work with standalone editor.

<div class="col-sm-4">
                        <div><span>Due: </span><span data-wo-field="workorder.due" ><?php echo $row->workorder->due ?></span></div>
                        <div><span>Priority:</span><span data-wo-field="workorder.priority"><?php echo $row->workorder->priority ?></span></div>
                        <div>Created: <span ><?php echo $row->workorder->opened ?></span></div>
                </div>

Doesn't work

fields: [
                {
                    label: "Due Date:",
                    name: "workorder.due",
                    "type": "date",
                    "dateFormat": "mm\/dd\/yy",
                    "dateImage": "images\/calender.png"
                },

Works as text field

 fields: [
                {
                    label: "Due Date:",
                    name: "workorder.due",
                    "type": "text"

                }

Replies

  • allanallan Posts: 54,914Questions: 1Answers: 8,608 Site admin

    Odd, I've just tried this and it appears to working okay. Are you able to linked me to your page so I can debug it?

    Thanks,
    Allan

  • wannbergwannberg Posts: 11Questions: 3Answers: 0

    I sent an email with the page code

  • allanallan Posts: 54,914Questions: 1Answers: 8,608 Site admin

    For anyone else who comes across this discussion, there is an error in Editor 1.4.0- in how jQuery UI dates are handled if you attempt to set a field value immediately after creating a new instance.

    The fix will be in 1.4.1 :-)

    Allan

This discussion has been closed.