removeDate not working

Hey Deborah,

Have you looked at this for possible syntax ideas?

https://www.interactivetools.com/forum/forum-posts.php?postNum=2240342#post2240342

Jerry Kornbluth

Yes, Jerry, I did see that post - thanks. Some good-to-know code there.

My need for this project is simply that I don't want to display any records after the 'removeDate'.

The CMSB documentation page defines 'removeDate' as:
"Record won't be displayed on website after this date. This allows users to have content automatically "expire" from website after a certain date and time."

Hmm.

Hi Deborah,

I just tested the removeDate feature on a record in a multi-record editor3.50 installation (it's the latest I have) and it worked for me

When the remove date is set to before today, the 'never remove' checkbox is not checked, and that record is saved, that record's information disappears from my front end list page after I refresh the list page.

Are you running the same or a later CMSB version? Could your cache be keeping an earlier version of the page?

Jerry Kornbluth

Hi Deborah,

I can confirm that you're not missing something obvious; it should be working as you have it, so there must be something else at play. Along with what Jerry has suggested, something you can try is switching the "<" for ">" in your where statement above so you get something like this:

// load records from 'featured_events'
list($featured_eventsRecords, $featured_eventsMetaData) = getRecords(array(
'tableName' => 'featured_events',
'limit' => '4',
'where' => '(NOW() > removeDate)',
'allowSearch' => false,
));

If the first query returns all records, then this should theoretically return 0 records. Whether or not this happens in your case could help us narrow down the issue.

Thanks,

Hi Daniel,

I didn't need a where clause on my list page, it just worked as it was supposed to.

My load records code is similar but without the limit and the where

Does needing a where have anything to do with the

'limit' => '4',

Best,

Jerry Kornbluth

Jerry - thanks for your thoughts.

I'm not using a "never remove" checkbox.

This install's CMSB version is 3.51.

Cache cleared (good idea), but no change.

Thanks again!

Daniel,

Just tested with the following code:

// featured_events list
list($featured_eventsRecords, $featured_eventsMetaData) = getRecords(array(
'tableName' => 'featured_events',
'limit' => '4',
'where' => ' (NOW() > removeDate) ',
'allowSearch' => false,
'loadCreatedBy' => false,
));

(realizing now I had used < instead of > for removeDate)

The above code does remove all records, even those with dates that shouldn't yet be removed, such as this record's date stored in the database:
2019-09-15 00:00:00

I seem to get "all or nothing". Shouldn't 'removeDate' take care of that filtering behind the scenes, without need of a 'where'?

~ Deborah

Hi Deborah,

That's been my experience, and my test confirmed it.

Jerry Kornbluth

Hi Deborah,

You're correct - removeDate should be handling this in the background; I just wanted to try changing the where clause to eliminate some causes. At this point, it seems like either there's something unexpected happening when we're comparing the dates, or the server time is incorrect. The latter is fairly easy to test: could you try running this code on your page and let me know the output?

print_r(mysql_fetch('SELECT NOW()',1));

Thanks,