Updating an existing event node to set a new upcoming date.

Set the month, date, year time for event Start Date.

Got error

<code>

  • warning: checkdate() expects parameter 3 to be long, string given in
    /hermes/bosweb/web226/b2264/sl.rgoya/public_html/shchc/modules/event/event.module
    on line 1685.
  • The specified date is invalid.

</code>

Also same error when Start Date is unchecked. Same in IE and Ffox.

Added to event.module line 1685:

<code>
$form['#value']['year'] = "2008";
</code>

but then got error "Invalid Date" so had to also add:

<code>
$form['#value']['day'] = "26";
</code>

Then updated event was entered in calendar system without errors.

Tried also saving as revision, same errors.

Using latest version 6x-2dev downloaded today after receiving same errors on earlier version.

Comments

decibel.places’s picture

decibel.places commented

A little more info:

I took out my hacks and was able to create a new event node no problem

I noticed when I was editing the pre-existing event that the Start date was set to January 00 when I loaded the node for editing (not it's previous date), while the new event showed the current date and time

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Postponed (maintainer needs more info)

So, it works if your "hacks" are not in the module? Or not?

decibel.places’s picture

decibel.places commented

My problem was updating an event whose original date had passed

I found it with date January 1 and no year and time 00 00 and I was unable to update it until I forced the hacks

I added the hacks to force the values on the existing node

Then I removed the hacks for general use and the module has been working fine including creating new event nodes and editing pre-existing ones

I have since been able to update another event node with an expired time so I do not know what caused the problem

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Postponed (maintainer needs more info) » Fixed

Ok, I mark this "fixed". I've no idea why you couldn't update that node. the module doesn't care about past/not past events.

decibel.places’s picture

decibel.places commented

I agree - it has not happened since, and nobody else reported same

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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

llaslo’s picture

llaslo commented

I actually had this same error:

warning: checkdate() expects parameter 2 to be long, string given in ...

except I had no 'hacks' to the module -- it was a clean install. What I found was that that the error popped for the initially added event. Once I deleted that event through Administer-->Content and then created a new event, the error was gone and has not recurred. If anyone else has the problem, try just deleting the problem event and creating a new one.

ptam’s picture

ptam commented

Please suggest how to solve past date problem in event module.
Past dated event can be created .