Undo some easy to resolve (no longer netstd2.0 TFM) breaking changes (#12316)
* Undo some easy to resolve (no longer netstd2.0 TFM) breaking changes * Restore missing ctor to PublishedSnapshotServiceEventHandler
This commit is contained in:
@@ -4,6 +4,7 @@ using Umbraco.Cms.Core.Events;
|
||||
using Umbraco.Cms.Core.Models;
|
||||
using Umbraco.Cms.Core.Notifications;
|
||||
using Umbraco.Cms.Core.PublishedCache;
|
||||
using Umbraco.Cms.Core.Services;
|
||||
using Umbraco.Cms.Core.Services.Changes;
|
||||
using Umbraco.Cms.Infrastructure.PublishedCache.Persistence;
|
||||
using Umbraco.Extensions;
|
||||
@@ -38,6 +39,17 @@ namespace Umbraco.Cms.Infrastructure.PublishedCache
|
||||
_publishedContentService = publishedContentService;
|
||||
}
|
||||
|
||||
[Obsolete("Please use alternative constructor.")]
|
||||
public PublishedSnapshotServiceEventHandler(
|
||||
IRuntimeState runtime,
|
||||
IPublishedSnapshotService publishedSnapshotService,
|
||||
INuCacheContentService publishedContentService,
|
||||
IContentService contentService,
|
||||
IMediaService mediaService)
|
||||
: this(publishedSnapshotService, publishedContentService)
|
||||
{
|
||||
}
|
||||
|
||||
// note: if the service is not ready, ie _isReady is false, then we still handle repository events,
|
||||
// because we can, we do not need a working published snapshot to do it - the only reason why it could cause an
|
||||
// issue is if the database table is not ready, but that should be prevented by migrations.
|
||||
|
||||
Reference in New Issue
Block a user