After installing the date-7.x-2.0-rc1.zip without any errors or messages, users cannot create a new Date content type. The user clicks "Add Content", selects the "Date" content type, and fills out the fields (/#overlay=node/add/date).

When the user clicks the "Save" button, the "Create Date" form displays - but not as an overlay - again without any of the user-entered information (/node/add/date). No date page is created and no error message is displayed.

If user completes the form again (the one that displayed after the first attempt), a blank page appears.

(screenshots attached)

Using Drupal 7.7, PHP 5.3.3, Database MySQL 5.0.77-log

CommentFileSizeAuthor
#1 date-7.x-2.0-rc1_add-event-issue.jpg25.12 KBh2pm

Comments

h2pm’s picture

h2pm commented
StatusFileSize
new date-7.x-2.0-rc1_add-event-issue.jpg25.12 KB

Second attempt to upload screenshot...

rublev_green’s picture

rublev_green commented

having the same problem :(

h2pm’s picture

h2pm commented

I'm wondering if there is a way to go back. I suspect the answer is "no", but we now have a production (live) website for a large organization that cannot post their many events they sponsor each month.

karens’s picture

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

I can't replicate any problem in the latest dev code. Try that and see what happens. If you still have trouble there see if you can see the same problem on a fresh installation with just Date module. If you can, I need steps to reproduce. If you can't, there is something else going on here (some other module or something about your setup).

h2pm’s picture

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

I suspect we need to update the core. We will be trying this over the weekend when traffic is lower. It might be nice if module updates include a core version dependency. I don't remember seeing any but I could have missed it. Thanks for replying so quickly KarenS.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Status: Active » Postponed (maintainer needs more info)

Setting back.

rublev_green’s picture

rublev_green commented

Yep, after updating to 7.10 problem went away

karens’s picture

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

A good first step on any problem is to be sure you are using the latest version of everything. There were some function name changes in core around 7.8 and we use the new function names. Unfortunately I can't find any easy way to warn you that you need core to be current, but you should always be using the current version of core anyway, really.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented

We could add a dependency on system >=7.10 in the .info file.

karens’s picture

karens commented

I tried that before and it broke the modules page. Apparently I did it wrong or misunderstood how it should work.

arlinsandbulte’s picture

arlinsandbulte commented

Just thinking out loud:
The breakage might be due to having D7.9 or less with Date module already installed. When a version dependency of 'system >=7.10' is added to Date while it is already installed, problems might erupt.
IIRC, the situation is similar if a module dependency is added to a module that is already installed, and I think there is a core issue about that somewhere.

h2pm’s picture

h2pm commented

Took me a while to get back to report the resolution. It is fixed by upgrading to v7.10. We try to avoid upgrading to new core because system failure has a greater impact than just a module. In this case, just the calendar was affected. We are now running into a statistics (core module) problem that might be in that module or it might only show up in that module.

Anyway, this is fixed.

Status: Fixed » Closed (fixed)

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