I've programatically alllowed documents to be created for a client with a release and expiry date. It's worked fine for ages.
I've recently discovered that recent documents that have been set an expiry date (remove at date property) in properties are not unpublishing the document at the specified time and are still published 2 days after it was supposed to be removed.
I.e Today is 20th May 2013
Remove At : 18th May 2013 still populating the field (so it must not have been unpublished at all)
I had a similar issue that was down to Event Handlers trying to fire that were dependent on there being a user. When 'publish at' and 'remove at' fire events there is no user associated with them (as Umbraco itself, as the system, is performing the publish) so my code was failing silently and prevented the publish/remove at functionality from working correctly.
Not sure if this is of any use to you, but hopefully it'll point you in the right direction!
Sorry for not replying sooner with my progress but it sorted itself out the following day from the looks of it it was just a massive server delay so umbraco wasn't getting the correct time took a couple of refreshes of the browser to get back into sync.
@Andreas i meant that when I manually put values of Publish At and Release At Dates into umbraco (the scheduling dates) - the button functions were working fine
Expiry Date not working?
I've programatically alllowed documents to be created for a client with a release and expiry date. It's worked fine for ages.
I've recently discovered that recent documents that have been set an expiry date (remove at date property) in properties are not unpublishing the document at the specified time and are still published 2 days after it was supposed to be removed.
I.e Today is 20th May 2013
Remove At : 18th May 2013 still populating the field (so it must not have been unpublished at all)
Why is this?
Its not working manually as well
Do you mean the scheduling dates? And that manually unpublishing does not work?
Hi Paul,
I had a similar issue that was down to Event Handlers trying to fire that were dependent on there being a user. When 'publish at' and 'remove at' fire events there is no user associated with them (as Umbraco itself, as the system, is performing the publish) so my code was failing silently and prevented the publish/remove at functionality from working correctly.
Not sure if this is of any use to you, but hopefully it'll point you in the right direction!
Braydie
hi guys,
Sorry for not replying sooner with my progress but it sorted itself out the following day from the looks of it it was just a massive server delay so umbraco wasn't getting the correct time took a couple of refreshes of the browser to get back into sync.
@Andreas i meant that when I manually put values of Publish At and Release At Dates into umbraco (the scheduling dates) - the button functions were working fine
Hi Paul, glad to here that your problems are gone and thanks for your reply.
is working on a reply...