So, the latest nightly solved the following of my problems:

http://drupal.org/node/284571 (preg_match warnings)
and
http://drupal.org/node/284572 (regular YYYY-MM-DD didn't validate)

but spawned another:

In the date filter field, now doesn't validate anymore.
I reverted back to the 18th of july version, since working with 'now' is pretty crucial to my site. Please note that old views created with now still work, though.

Comments

Forceflow’s picture

Title: 'now' doesn't validate in the 23th nightly » 'now' doesn't validate in the 23/07 nightly
Forceflow’s picture

Just tested it on a fresh drupal installation, same problem. Sorry :)

I'm no PHP-wizard, but you might have screwed some validation up with those latest fixes.

sjon’s picture

I needed this like yesterday, so I made a small change in the code that will allow 'now' to work again.
I don't have enough knowledge of the date module to know if this is the correct way to do this or not, so YMMV...

File date_api.views.inc, line 666, changed:

if (empty($value)) {

into:

if (empty($value) || ($value == 'now')) {

Regards,

KarenS’s picture

Status: Active » Fixed

'Now' goes into the adjustment field, not the date field. If you put it in the date field it will not validate. This is to get ready to add date widgets as date selectors since they won't allow a value like 'now' as valid input.

Forceflow’s picture

Terribly sorry. That wasn't clear at all for me :)

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.