Blind Date - use human readable dates in the CP & SAEFs

Brian,

debug output is below:

Field Name: entry_date Time Given: 2009-12-24 11:41 Timestamp: 1261676460 Date from Timestamp: 2009-12-24 11:41:00 AM

Field Name: expiration_date Time Given: 2009-12-24 11:41 Timestamp: 1261676460 Date from Timestamp: 2009-12-24 11:41:00 AM

Also I just redownloaded the non-debug version from the link on the 1st page of this thread. installed it and noticed that it reports as version 1.2.7 rather than the 1.3 on the zip file. Is that correct?

cheers for your help mate

Tom

Hi Tom - you’re right that was 1.2.7 in the original post. I’ve fixed that so the file is now 1.3 on the 1st page.

Tom I”m going to go to PMs so we can work through this without having to keep bumping the thread.

Thanks!

This may have already been asked, and if so I apologize, but I was wondering if there was a way to retroactively update dates in the system? My client has been adding calendar entries and the time stamps are breaking the functionality. I found your plugin today and, while it works perfectly on new entries added, the old ones are still incorrect. I may have to go correct them by hand, but I figured I’d check first to see if its a possibility.

Thanks!

Sorry Brandon - this extension won’t do what you need :(

No problem, I didn’t think so. It’ll help going forward though, so thanks for that.

Thanks SO MUCH for this Extension, Brian!! Had to build a SAEF for an event calendar today and was trying to jump through all sorts of hoops with jQuery to properly format jQuery UI Calendar Picker Widget input into an entry_date field. Your Extension solved ALL my problems!!

This is a very good extension, thanks for creating it!

One thing I want to know is there a way to limit it to just certain weblogs. I have events and the only true thing I need Blind Date for. I did not see anything in the settings but maybe I can hack the extension. I do need a little direction of how difficult it would be to make it specific to one weblog and where to find it in the code.

Right now it applies to everything. You would need to add an option to the settings page, and then check for that vs which weblog you’re posting into. I don’t have the time to add to or modify this extension, but you’re welcome to do so - if you do it would be great if you could share what you’ve added. Thanks dvancouver.

Hi Brian

For some reason Blind Date isn’t working for me right now with my SAEF. I’m getting the following error:

The following date isn’t in a recognizable format. Please change the syntax and try again: 30/05/2009

It’s a perfectly okay european date format.

Does Blind Date not accept the following format? 30/06/2009

Cheers

Jim

Blind Date relies on the PHP function strtotime() to work its magic. The strtotime function says this:

“The function expects to be given a string containing a US English date format and will try to parse that format into a Unix timestamp…”

I think the problem comes in because with that format it can’t be sure what you’re asking for: 6/9/09 and 9/6/09 can be the same date or different dates, depending on where you’re from.

Doing some research it looks like it is possible to pull in a timezone into the function and use that in the calculation, but I currently don’t do that and it requires PHP 5+ which I am hesitant to require. I’m not sure it would cure your problem even if we supplied that. Try this - if you add on your three letter timezone code at the end of the date, does it work? So for me it would be:

06/30/2009 EST (That’s for Eastern Standard Time).

I believe there are three letter codes for all time zones, not just US ones?

Hi Brian

Many thanks for getting back to me so fast. I’ve actually changed the format that the date picker uses to be dd-mm-yyyy and it’s working great!

Issue solved.

Cheers and have a great weekend.

Jim

You too 😊

I am wondering if any thought has been given to adding a by weblog setting?

At this point I’m in a holding pattern with this - I don’t really have any time to put into it. You’re welcome to add anything to it you like and if it doesn’t have a backdoor to Fort Knox or something I’d put it into the public version.

I really should make it less confusing to use, but I was initially waiting for 2.0 to come out to see if this would all be made redundant anyway…