warning: mktime() expects parameter 6 to be long, string given in .../modules/tablemanager/tablemanager.module on line 975.

This warning pops up on display of my table.

My dates are in the format yyyy/m/d. (Dates come out ok except in the header as in someone else's issue. It changes Date to 31st December 1969.)

Comments

pobster’s picture

pobster commented

Argument 6 is the year, this will be tough for me to debug without more information. Can you perhaps provide me with a sample piece of csv which will generate this error. Please bear with me on this though as I don't have a proper 5.x environment for testing.

Thanks,

Pobster

--------------------------------------------
http://www.justgiving.com/paulmaddern
--------------------------------------------

pobster’s picture

pobster commented

Hmmm... "User unknown (in reply to RCPT TO command)"... Your email is bouncing?

Anyways...

What you've sent me isn't CSV...

CSV stands for "Comma Separated Values" and literally is;

Paul,31,http://www.arcadegeek.co.uk
Lola,12,http://www.cats.com
Sheba,9,http://www.dogs.com

I've just tested the import csv facility with dates and they do indeed work fine... I really need you to guide me through what it is you're doing to get this error, so I can rule out that you're not just doing something wrong?

Tell me from the start, create a table with THESE headings. Import THIS CSV and it'll give THIS error... Currently I'm struggling to see what's going on? I used the same yyyy/m/d format as you suggested?

Pobster

protoplasm’s picture

protoplasm commented

Sorry. CSV was sent to you in a second email that immediately followed the first, but apparently my ISP must been having their issues again. There's nothing wrong with the import of CSV. All goes well until you access the tablemanager in content management. The table displays fine, but with the box warning at the top of the page. There is a glaring error with a wrong date that is inserted into the header. Instead of EndDate, I get 31st December 1969.

CREATE TABLE `tablemanager_data` (
`id` int(11) NOT NULL auto_increment,
`tid` int(11) NOT NULL default '0',
`uid` int(11) NOT NULL default '1',
`data` text NOT NULL,
`format` int(3) NOT NULL default '1',
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=9368 ;

--
-- Dumping data for table `tablemanager_data`
--

INSERT INTO `tablemanager_data` VALUES (1, 2, 1, 'a:14:{i:0;s:2:"ID";i:1;s:7:"EndDate";i:2;s:3:"URL";i:3;s:12:"Manufacturer";i:4;s:4:"Line";i:5;s:7:"Pattern";i:6;s:8:"Designer";i:7;s:5:"Title";i:8;s:6:"Quant.";i:9;s:4:"Item";i:10;s:4:"Size";i:11;s:5:"Notes";i:12;s:4:"Bids";i:13;s:5:"Total";}', 1);
INSERT INTO `tablemanager_data` VALUES (2, 2, 1, 'a:14:{i:0;s:1:"1";i:1;s:8:"2007/4/3";i:2;s:67:"http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=180101295362";i:3;s:16:"Gladding, McBean";i:4;s:10:"Franciscan";i:5;s:9:"Starburst";i:6;s:12:"George James";i:7;s:41:"4 Franciscan Starburst 9"" Plates Vintage";i:8;s:1:"4";i:9;s:6:"Plates";i:10;s:3:"9""";i:11;s:0:"";i:12;s:1:"9";i:13;s:7:"$66.50 ";}', 1);
INSERT INTO `tablemanager_data` VALUES (3, 2, 1, 'a:14:{i:0;s:1:"2";i:1;s:8:"2007/4/3";i:2;s:67:"http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=230110476492";i:3;s:15:"Sascha Brastoff";i:4;s:0:"";i:5;s:0:"";i:6;s:15:"Sascha Brastoff";i:7;s:55:"Huge Sascha Brastoff ""STAR STEED"" Pattern Candlestick";i:8;s:1:"1";i:9;s:11:"Candlestick";i:10;s:0:"";i:11;s:0:"";i:12;s:1:"5";i:13;s:7:"$52.26 ";}', 1);
INSERT INTO `tablemanager_data` VALUES (4, 2, 1, 'a:14:{i:0;s:1:"3";i:1;s:8:"2007/4/3";i:2;

protoplasm’s picture

protoplasm commented
Status: Active » Closed (fixed)

This problem was 'resolved' by just removing that first line of data with column information from the csv's. The warnings eventually disappeared. I'm closing my issue with this problem.