This isn’t an issue on your end (I don’t think) but the backend display is off when I view the saved entry. I’m using DST for both my account and the site.

Sue Crocker - 18 March 2007 02:55 PM

This isn’t an issue on your end (I don’t think) but the backend display is off when I view the saved entry. I’m using DST for both my account and the site.

Hmm that’s pretty funky. Are the dates in the field correct, or the dates shown in the JS calendar?

You’re correct though Sue - I’m not doing anything with the calendar itself, just modifying the date before it gets entered.  If you manually enter a similar date, it should display the same issue - that would be a good test.  It might be worth starting a thread in tech support for this issue?

I’m going to do just that.

I have fixed a bug that would cause Blind Date to incorrectly shift the adjusted hour on some servers. The new version is 1.2.2, and is in the original post.

Happy dating

I’m a tad slow I think. What exactly are we supposed to enter in the settings fields?

DEA - 25 March 2007 04:25 PM

I’m a tad slow I think. What exactly are we supposed to enter in the settings fields?

By default you don’t have to use any of the settings at all - it works on all date fields in the system.  The settings are for behavior different than the default behavior.

By default, if no year is given in a date field, the current year is used (2007 right now).  By default, if no time is given in a date field, 12:01 AM is used. Otherwise it just uses whatever you put into the field.

The settings are for changing that default behavior.  If you want to force a future date for a certain field, put the field name you’d like to force into the future in the “Thinking Long Term? (force future date)” field.  For example, say you have a field named ‘application_deadline’ that should always be a date in the future. You put that field name in the “Thinking Long Term” setting field.  Then if someone enters either no year, or a previous year, it will change that year to the upcoming year.  If today is March 25, 2007, and someone enters March 26, 2007 then it leaves it alone - but if they put March 26, 2005, the resulting date would be March 26, 2007.

Any field name you put in “punctual to a fault” will be forced to use 12:01 AM for the time, no matter what time is actually entered.

Any field name you put in “disastrously late” will be forced to use 11:59 PM for the time, no matter what time is actually entered.

Any field name you put in “fashionably late” will use whatever time is entered into that field, but if no time is entered, will use 11:59 PM (remember the default behavior is to use 12:01 AM).

Does that make sense?  None of them are mandatory settings - but if you want a certain field to behave differently than normal, that’s what they’re there for.

Hey, thanks for this very helpful. Am going to mess with this right now. Now if the SAEF Calendar could only be a show/hide div. That’s another day…

Hmmm, I’m getting the same error Sue identified a few posts back I think. It seems to only happen when trying to update the expiration_date field; changing the entry_date works fine.

DEA - 28 March 2007 12:42 AM

Hmmm, I’m getting the same error Sue identified a few posts back I think. It seems to only happen when trying to update the expiration_date field; changing the entry_date works fine.

DEA are you using the newest version? 1.2.2?

Could you give the exact error? Are you sure it is the same?:

Thanks

Hey there, here it is:

DEA, can you try updating the extension to 1.2.3 attached to this post, and let me know if that fixes it? Thanks!

EDIT: I’m removing 1.2.3 here to avoid confusion.

Thanks. I’ll have to wait to get home now. I’ll updated as soon as I do and let you know.

OK, just tried it and am getting the same error back.

I’m going to send you a PM with another file. For some reason I can’t recreate the issue on my local install here, so I see the issue but can’t test any changes I make…

I’m getting these errors:

I removed directory info.  I tried 1.2.2 and 1.2.3 - This is such a great contribution - I’d love to get it working!

EDIT: I see now my errors are almost identical to DEA’s - sorry about that!

BTW, I’m doing this from a SAEF and it is actually submitting the entry correctly.

Sorry for the delay - I’ve got a new version (1.2.4) up that corrects the problem both DEA and ruraldreams have posted.  Those notices were happening if you installed the extension and never submitted any settings in the CP (even if they were all left blank).  Should be all fixed up now