You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
I have an Umbraco installation running 6.1.6 with UrlTracker 3.0.
Whenever a user sets a "Remove At" date for a given page, everything seems to work fine when looking in the backoffice. When the date is passed, the page correctly appears to have been unpublished according to the UI on the backoffice. However in the frontend, the page seems to still be existing in the content cache.
Steps to reproduce:
Create a page
Set "Remove At" date and publish the page
Wait...
Page is still accessible via the frontend after the date has passed
I tried upgrading to UrlTracker 3.2, but the page still isn't unpublished properly if I retry the above steps.
If I try to remove the UrlTracker DLL, the page is unpublished correctly.
The text was updated successfully, but these errors were encountered:
[BugFix] Error during installation: 'ASP.UmbracoHelper' does not contain a definition for 'IsVersion7OrNewer' ([#52](#52))
[BugFix] JavaScripts errors in backend in IE11 ([#31](#31), updated jQuery)
[Feature] Domain on child node with cross site/host redirects ([#40](#40))
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have an Umbraco installation running 6.1.6 with UrlTracker 3.0.
Whenever a user sets a "Remove At" date for a given page, everything seems to work fine when looking in the backoffice. When the date is passed, the page correctly appears to have been unpublished according to the UI on the backoffice. However in the frontend, the page seems to still be existing in the content cache.
Steps to reproduce:
I tried upgrading to UrlTracker 3.2, but the page still isn't unpublished properly if I retry the above steps.
If I try to remove the UrlTracker DLL, the page is unpublished correctly.
The text was updated successfully, but these errors were encountered: