I have a node with a date field, and some radio buttons.

I have the radio buttons as the only editable ones but when I try to change one, I get this error.


    * Rental Date is not a valid date.
    * warning: array_shift() [function.array-shift]: The argument should be an array in /home/.axle/luclimbing/cliffmonkeys.com/includes/form.inc on line 852.

The web site is www.cliffmonkeys.com

I cannot open access to the area effected publicly but if you register I will promote you to a level that can access it if you need to view it. Le me know what other info might be needed.

Comments

markfoodyburton’s picture

markfoodyburton commented

Mm, so the date field is not supposed to be edited?
Odd... In principle the module simply doesn't touch fields that are not marked as editable, so if the initial value is valid, then it should still be valid. I assume the initial value is valid?

Cheers

Mark.

ellanylea’s picture

ellanylea commented
Title: Error when editing a field » Required date makes editablefields Views Update not valid

This could be similar:

I'm using a Views to display CCK-type "schedule" which has text fields, select lists, and date fields. Some of the text fields and select lists are listed and editable in the Views.

In the Views, when I make changes to the editable fields and bulk update the Views, I get this error message:
* Work Date is not a valid date.

If I add the 'Work Date' field to the Views and update the Views, I still get the same error. If I make 'Work Date' editable then update the Views, the error goes away and the changes are submitted.

The initial value is valid. I have no problems editing the node itself.

The 'Work Date' field is required. If I make it not required, the Views submits as well without errors.

Hmm, date validation problem?

hampshire’s picture

hampshire commented
Version: 5.x-1.0 » 5.x-3.3

This problem still exists. I am using 5.x 3.3 and have 3 fields I need to change on several hundred nodes and can not do so. The date field is not one of the fields I am trying to update but it is a required field and always has been so it should already be present on all existing nodes.

markfoodyburton’s picture

markfoodyburton commented

I'm sorry to be slack on this, but I've not looked at the 5.x code for ages. Now I've done the 6.x code, I now understand why so much of the 5.x code is broken, but retro-fitting the fixes will be impossible - it relies on so much of the 6.x infrastructure....

I'm sorry :-(

If you manage to patch round this problem, let me know and I'll happily commit the patch :-)

mjetpax’s picture

mjetpax commented

I was getting a similar error when filtering by the date field in Views. I kept getting "not a valid date". I was able to resolve this issue. It turned out to be my error. In the option field for the date filter I had typed [ now ] without apostrophes (the brackets are a visual aid, they represent the text field borders). Once I replaced this with [ 'now' ] the error went away.

replace now with 'now'

Hope this helps.

mjetpax’s picture

mjetpax commented

Ok, now I feel stupid..... it ended up being that I need to uncheck required field in cck for the date field after all. Which I initially tried, but, the fix didn't manifest itself until I went into the View and zero-ed out the date filter fields for year, month, day and saved. Or maybe it was just the act of saving the View. I really don't know. Apparently [ now ] or [ 'now' ] doesn't matter one way or the other.

:} <--egg on face.

hope this helps.

hampshire’s picture

hampshire commented

Yeah making the field not required allows editing. The way I did it was just add the date field to the view as editable even though I was not going to edit it and that worked fine. This module does save a lot of time since I can edit about 600 fields on one page instead of have to go to 200 seperate pages.

acidpotato’s picture

acidpotato commented
Status: Active » Closed (won't fix)

Closing legacy issue. Reopen as needed.