Disappearing dates because of Date Popup?

Me too.

And more, when editing node, node reference field and edited imagefield field
disapper too...

It must be because of other module installed, being in conflict with others... :/

Szy.

I can't replicate the problem, it must be some conflict with something else that is installed. It appears you are using some module that alters the node form. It isn't the Date module doing this, you'll have to figure out what other modules might be doing it.

If other fields are disappearing too, it clearly isn't a date issue, it's coming from somewhere else.

Hey guys,

I was having the same effect since I updated my d5 installation to use date-api 2.5. After wasting several ours I end up deleting my phptemplate_date_display_combination() function on my template.php and everything goes well.

Don't know why but, since 2.5 api update, date[value][formatted] comes empty so my date_display_combination() doesn't work anymore.

In case it helps

Regards

I know, that following conclusion can look strange, but after a lot of tests (easy kind:
turning on/off lot of modules, changing widgets, changing displays) I could do, it looks
like there is something wrong in Date Popup code, what may lead to other problems.

As I have written before, I had problems in cloning nodes (with Node Clone module)
last days. Depending on configuration, used fields (CCK Link, Node Reference,
Imagefield, and Date) and widgets, I always had problems in cloning nodes: cleared
field's content in either original node or cloned one.

-> #373141: Cache is not cleared after submit, original fields disappeared too
-> #373501: Cloning nodes with taxonomy terms, breaks listing of tagged nodes

I have discovered, that content from disappearing fields' in new cloned nodes exists
in fact in database, but... Drupal cache wasn't cleared right after cloning, so it was
impossible to see it in node view!

In the same time, I started to watch these errors on my front page:

-> #373982: warning: date_format() expects parameter 1 to be DateTime, null given in date.theme #163, #164, date_api.module #625

Now, when I turned off Date Popup module - yes, I was using date popup widgets
- all is fine again. No errors on front page, no disappearing fields' content in original
nor cloned fields, no cache problems. Important - just changing popup widget
to select widget with Date Popup module still turned on - didn't help in anything.

As I said, maybe it looks strange. I don't know even if it is possible from technical
point of view (popup widget blocking cache?), but it happened to me for sure.

Szy.

PS. Karen, thank you for your great job for us.

These are all a bunch of totally different issues. The original issue implies that dates that have already been created mysteriously disappear sometimes during viewing or editing for no reason. I can't replicate that and as far as I can no one else is reporting that, so I suspect that's some module conflict specific to that particular setup.

#3 says a custom template created for an older version of the module doesn't work in the current version. That one's easy, just get rid of the custom theme or spend some time to rework it for the new code. That's not a bug, that's what happens if you create custom themes and there are changes in the themes they are based on. That has nothing to do with the original issue and it's not a bug.

#4 is talking about problems importing nodes. That problem I think is because Node clone uses drupal_execute() which has a number of problems if you're trying to import information into complex fields like date and imagefield because there is a core bug that keeps it from doing some of the complex processing that the date field does. I don't recommend using drupal_execute and I can't do anything about the problems it creates. I recommend using node_save() instead of drupal_execute(). That also has nothing to do with the original issue.

There's nothing else here that I can do anything about unless someone can find a way to replicate the original problem.

There is a problem when you have a CCK-date field which widget_type is set to "date_popup". If you disable the "Date Popup" module, you can see in the database (in the content_node_field_instance table; see the attached file), that the widget_type of the field is still set to "date_popup" (it should be "date_select", I guess ...), AND "widget_active" is set to "0" (it should be "1" because "Date" module is active). That's why the field is desactivated and the "date disappeares". You've just to reactivate the "Date Popup" module to get it back.

I just added a test for the Date popup widget to be sure it doesn't try to use it if you disable the module. That's plenty for this issue which is totally polluted, so don't reopen it, start a fresh one if there are problems in the latest -dev code.