I'm have several CCK types all using the same date field. When I add a new node, it's storing the current month/year rather than the selected month/year. I can go in and edit the node and fix the date, but new ones are always getting the current date.

Comments

sdecabooter’s picture

sdecabooter commented

I have the same problem.
Seems to have started occurring after i upgraded from rc5 to rc6.
I used devel to reinstall all date modules, removed my CCK field and replaced it with a new one, but the problem is still there.
When i add a new node, no matter what I select in the date field, it's saving the current date.

Even when the To date is set to Optional, the date is still stored.
In my content type table, both field_date_value & field_date_value2 contain the value 2008-12-00T00:00:00 (granularity is set to month & year)

ipswitch’s picture

ipswitch commented
Priority: Normal » Critical

I'm not exaclty sure how this works. I do know that this issue is critical for me because me users can't enter any conent right now until this is resolved. I see that KarenS has responded to issues submtted after this one but no comment here so I'm not exactly sure where this issue stands.

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

You need to start by moving to the very latest -dev version of the code to see if your problem is already fixed. If it's still a problem there, then I need complete information on how to reproduce your situation because I'm not seeing it.

ipswitch’s picture

ipswitch commented

Installed the latest dev version and the issue persists. This affects existing CCK Date fields (tried date and datetime) as well as new ones. When I preview the node, the current month/year appears regardless of the selected value. I can change it on the preivew and the correct date is saved. Likewise, I can edit the node and correct the date and it stores correctly so it seems to only happen when creating a new node. Please let me know any additional details needed to troubleshoot this issue.

karens’s picture

karens commented

There are three kinds of date fields with six kinds of widgets and each of those combinations has dozens of possible ways all the other settings can be set up, timezone handling, granularity, etc, and all of these things are further affected by the modules you have installed (are you using Date Repeat? Date Popup? Calendar?). When I say I need to be able to reproduce your setup, I need to know exactly what kind of field you created, what kind of widget you used, what settings you selected, what your environment looks like, your verison of PHP, what your site and personal timezones are, and a step by step explanation of what you did that I can reproduce. I can't possibly test every possible combination of setup options to see if I somehow manage to stumble across the situation you're seeing.

I am totally unable to reproduce this problem so there is something in your setup or the kind of field you're using that is causing this.

ipswitch’s picture

ipswitch commented

I've likely just fouled up but, for the life of me, I can't track it down. Was working fine before I updated to the latest version of Date.

using latest version of:
Date
Calendar
CCK

Drupal 6.6

MySQL 5.0.67
PHP 5.2.6

Web Server Apache 2.2.9

Custon CCK types using any date field. Widget type = select list
I've tried adding both Date and Datetime and had the same result (current month always added).
I have granularity set to year and month (magazine issues).

I'm also using a custom input format of: F Y (year month)

thank you for your help

ipswitch’s picture

ipswitch commented
Status: Postponed (maintainer needs more info) » Active

I think I was supposed to have changed the status back to "active" after my last post and I don't see that I can change it without posting a comment.

ipswitch’s picture

ipswitch commented
Status: Active » Fixed

Latest dev version fixed this issue.

sdecabooter’s picture

sdecabooter commented

I updated to latest dev release, but this doesn't fix the issue for me.
I posted my most recent findings in #345099: date cck field won't let node be saved properly

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.