New Datepicker FieldFrame extension

Just to follow up on the timepicker feature, AnyTime, which is a combined date/time picker – used to be only for Prototype, but is now available for jQuery here. I’ve been using the older version in an SAEF for an events calendar and it works well. You may want to take a look at it.

Nice - Thanks for the link

Never mind. I went with another solution.

Still interested, but the lack of documentation makes implementation difficult.

Franklin,

As it’s a fieldframe field, it’s predominately of benefit to the admin Publishing and Editing of entries, and also via SAEF. So makes the JQuery Datepicker appear on the data entry for date fields.

Then to display the date on your website you simply display the variable in your EE template as you’ve named it e.g. {my_date}. This defaults to the date format you’ve defined in the FieldFrame settings. You can also add custom formatting like so: {my_date format=”%j %F, %Y”}

There are links to the different formats you can apply and the JQuery UI skins in the first post.

That’s about it.

Peter

I would totally love to see a version of this with the AnyTime picker mentioned above, or any other combined date/time solution, as an option. Maybe a single fieldtype with options for “date picker”, “time picker”, “both”?

I’m trying to sort my weblog entries based off of a TBZ Date field. However, it doesn’t seem to work no matter what I try.

{exp:weblog:entries weblog="products" limit="30" orderby="store_release" sort="desc" category="{segment_2_category_id}"}

{exp:weblog:entries weblog="products" limit="30" orderby="{store_release format='%Y-%m-%d'}" sort="desc" category="{segment_2_category_id}"}

@Jaxbulls:

In theory the first should work (the second won’t as EE won’t parse the variable).

What does this output?

{exp:weblog:entries weblog="products" limit="30" orderby="store_release"}

What’s {segment_2_category_id}? Or more specifically where is this stored as a weblog field or a category custom field?

The segment_2_category_id is a plugin to grab the category based on a URI segment http://loweblog.com/software/low-seg2cat.

I’ve tried the first method like you said but it seems to sort in some random fashion, not at all respecting the dates I put in.

Here are my store_release dates and the order of how they are being sorted…

10/31/2000 07/31/1999 07/31/1998 11/30/1997 11/30/1996 04/30/1989 01/31/1985 01/05/1983 12/31/1984 06/30/1979 03/31/2010

Just installed this on a client site - beautiful - thanks so much.

Just installed on a version of EE 1.6.9 with Pixel & Tonic’s Matrix 2.0.6 and when setting a Matrix Cell to the TBZ Date Field Type the Calendar CSS doesn’t load when viewing the Matrix Field within the Publish screen.

However, when viewing the Publish screen for a weblog that’s applying the TBZ Date Field to a stand alone field the CSS loads as expected.

Any idea where I would need to look to resolve?

Hi Michael, I’ll have to replicate with the latest matrix and get back to you. I’m assuming the css link doesn’t even appear in the html?

I’m assuming the css link doesn’t even appear in the html?

Hey, thank you for getting back to me.

Yes, this seems to be the issue.

Hi there,

I’m using this fieldtype in a SAEF and it works great, thanks. But I have a Matrix field which has quite a few columns, so the width of each individual field is important in order for it to fit within the page width.

I noticed that this TBZ Date Picker field input seems to have an inline style of 140px - I’ve just changed this by editing field_width on line 45 of ft.tbz_date.php to a smaller value.

But in order to save doing this (even though only a very minor ‘hack’), it would be great if there was a field setting within the custom field page for this field, that allowed you to specify this width. Either that, or have no inline style at all so we can adjust this (on SAEF’s) ourselves in CSS. As it stands, it’s fine and very minor, but means it’s something I’ll need to remember when upgrading in future.

Anyway, just a suggestion.

Thanks.

Has anyone got any tips regarding validation for this fieldtype in a SAEF?

I need to compare dates etc and would usually do some something like:

var date = document.getElementById("field_id_46").value;

However, this doesn’t seem to work for the TBZ field.