New Datepicker FieldFrame extension

The first link and option is really elegant, streamlined, integrates with themeroller, and would be ideal. I agree, the other two would be kinda clunky in a matrix or field block. Thanks for even considering adding time to the datepicker and for contributing to the community.

Very pretty! I like the Milesich approach for adding time.

For some reason, when I’m going back in to the weblog entry to edit the dates, after initial input, the date fields are empty… any ideas why this is happening?

Looking in the dbase, an entry has been posted in the field id, but it’s not being parsed upon edit.

I’m using v1.04 on EE 1.6.7.

What date format have you got set? and can you give me an example timestamp from your DB. Is it a single field or inside an FFMatrix?

Initial thoughts are it’s failing to parse the datestamp to the format required.

It’s set to ‘dd/mm/yy’, ‘smoothness’ and ‘show button’.

Dbase field shows:

a:3:{i:0;a:5:{i:0;s👎"";i:1;s👎"";i:4;s:17:"test pricing only";i:2;s:3:"400";i:3;s:3:"200";}i:1;a:5:{i:0;s👎"";i:1;s👎"";i:4;s:19:"test pricing only 2";i:2;s:3:"800";i:3;s:3:"500";}i:2;a:5:{i:0;s👎"";i:1;s👎"";i:4;s:19:"test pricing only 3";i:2;s:3:"900";i:3;s:3:"300";}}

Matrix weblog input is shown in attached screenshot.

Thanks, that’s the same setup I have on my current test. But in your example no datestamps are being stored in the DB. Could you select a date in any or all the fields, save the entry (don’t us Quick Save just in case that’s the issue), then look at the DB again. If it’s still blank, the issue is when it’s saving.

You should be looking at something like this in the DB:

a:3:{i:0;a:5:{i:0;s:0:1005264000;i:1;s:0:1257033600;i:4;s:17:“test pricing only”;i:2;s:3:“400”;i:3;s:3:“200”;}
i:1;a:5:{i:0;s:0:1005264000;i:1;s:0:1257033600;i:4;s:19:“test pricing only 2”;i:2;s:3:“800”;i:3;s:3:“500”;}
i:2;a:5:{i:0;s:0:1005264000;i:1;s:0:1257033600;i:4;s:19:“test pricing only 3”;i:2;s:3:“900”;i:3;s:3:“300”;}}

Your DB copy is showing “” instead of the timestamp.

Edit: What version of FieldFrame are you using?

Yep, just tried it again using ‘Update’ and there are no timestamps in there. I’m using FF 1.3.4

Update:

I seems there’s a problem with FFMatrix saving dates (unix timestamp) under certain conditions.

If you have “Automatically Convert High ASCII Text to Entities” set to Yes, then no date will ever be saved.

The option can be found here: Admin › Section Administration › Global Section Preferences “Automatically Convert High ASCII Text to Entities” should be set to No.

If Brandon doesn’t solve it beforehand, I’ll try and dig deeper into FFMatrix and look at solutions.

OK. I can clear the site with things as they are, but I’ve no doubt the high-ASCII issue will resurface at some point in the future, by which time it will hopefully have been sorted.

Many thanks for your help in getting to the bottom of this.

Would’ve thought Brandon would want to get this cleared or at least find out why it’s happening, in case it has implications for others developing fieldtypes. Date info is pretty important. It’s probably a data validation issue somewhere, I guess.

Not working for me as a FieldFrame Matrix field within a SAEF. No dates were working in SAEFs in FieldFrame until the upgrade to FieldFrame 1.3.5

Hopefully all fixed in the latest version v1.0.5

The zip file has the extension placed under /extensions/fieldtype/…, not /extensions/fieldtypes/…, which is where my fieldtypes are located. I think that’s the default location, too (plural instead of singular).

Yep, you’re right - thanks for letting me know. Have changed in the zip now.

Great extension, thanks! Any idea if you’ll be adding a time picker to this?