#1 1.6b2 Approve Event Error

[Brian Z]

When trying to approve (moderate) an event in the
calendar, php exits with the following error.

1136: Column count doesn't match value at row 1

Any help would be appreciated.

[Robby Russell]

Logged In: YES
user_id=254709

i get the same error.

help!

[Aleks A.-Lessmann]

Logged In: YES
user_id=294531

There was a error in the sql file for 1.6b2. Try using the newest Version (while not there yet, it's an
improvement)

[Nobody/Anonymous]

Logged In: NO

Same error here. Just downloaded the newest ver just an
hour ago.

Very nice up to this point. I really like the event list
block.

I'll keep checking back to see if the bug is fixed

Thanks

[Frank]

Logged In: YES
user_id=432310

Just downloaded the calendar for phpnuke 5.4 and want to
thank you for your effort. It's impressive but I get the
same error.

1136: Column count doesn't match value count at row 1

My guess is that when you updated the events and
events_query databases you didn't upgrade the index.php
with the new count. I do not know enough about programming
to find and fix the problem.

Like the others I am anxious to obtain the fix.

Regards,
Frank

[Aleks A.-Lessmann]

Logged In: YES
user_id=294531

Normally, this error means the PHP Script tries to fill up
parts of the Databse that are not there.

My problem is that I do not have this problem, and I have
tested my system with the update SQL file AND the normal
calendar.sql file.

My advice would be to backup your current event database
and run the calendar.sql. If you still have problems after
doing so then I'm at a loss.

I have the Calendar running under a PHPNuke 5.4 system,
there aren't any compatibility issues that I know of.

Antoher thing you could do is take a close look at the
event database via PHPMyAdmin or something like that and
take a look at what the script is trying to write to it.
See if all columns are there or if there is a mismatch of
columns. I f the latter, then it might be the update to the
DB didn't run correctly, or that I screwed up. Please tell
me how it went and if it solved any of your problems.

Greetinx
Aleks A.

[Nobody/Anonymous]

Logged In: NO

yeah i've got the same problem too :(

what did u done wrong?

[Nobody/Anonymous]

Logged In: NO

sorry about the last post, i meant to say - "what have I
done wrong?" ...

[bob prescott]

Logged In: YES
user_id=516095

I had the same problem. Found the reason. In Calendar.sql
the table is defined by

CREATE TABLE nuke_events_queue (
qid bigint(20) NOT NULL auto_increment,
uid mediumint(9) NOT NULL default '0',
uname varchar(40) NOT NULL default '',
title varchar(150) NOT NULL default '',
story BLOB,
timestamp datetime NOT NULL default '0000-00-00 00:00:00',
topic varchar(20) NOT NULL,
eventDate date DEFAULT '0000-00-00' NOT NULL,
endDate date DEFAULT '0000-00-00' NOT NULL,
startTime TIME,
endTime TIME,
alldayevent INT(1) NOT NULL default '0',
barcolor VARCHAR(1),
cat TINYBLOB,
PRIMARY KEY (qid)
);

In admin/modules/calendar.php the table is filled by

$result = mysql_query("insert into nuke_events values
(NULL, '$aid', '$subject', now(), '$hometext', '0', '0',
'$topic','$author','$newDate','$endDate','$startTime','$endTime',
'$alldayevent', '$barcolor')");

Clearly an extra item after barcolor. I got mine to work by
padding the insert.

$result = mysql_query("insert into nuke_events values
(NULL, '$aid', '$subject', now(), '$hometext', '0', '0',
'$topic','$author','$newDate','$endDate','$startTime','$endTime',
'$alldayevent', '$barcolor', '0')");

bob prescott