Skip to content

File based caching causes attempt to sync which throws an error #1

@lucasjans

Description

@lucasjans

The file based caching causes the watcher to trigger, which throws this error.

DotNetNuke.Services.FileSystem.InvalidFileExtensionException: The extension '.resources' is not allowed. The file has not been added.
   at DotNetNuke.Services.FileSystem.FileManager.AddFile(IFolderInfo folder, String fileName, Stream fileContent, Boolean overwrite, Boolean checkPermissions, String contentType, Int32 createdByUserID)
   at DotNetNuke.Services.FileSystem.FileManager.AddFile(IFolderInfo folder, String fileName, Stream fileContent, Boolean overwrite, Boolean checkPermissions, String contentType)
   at DotNetNuke.Services.FileSystem.FileManager.AddFile(IFolderInfo folder, String fileName, Stream fileContent, Boolean overwrite)
   at InspectorIT.FileWatcher.Components.FileMonitor.onFileChanged(Object sender, FileSystemEventArgs e, PortalInfo portalInfo)

I will put in a pull request to fix it. Should we not throw an error for file types that are excluded? Maybe a warning? Or perhaps certain types of files should be ignored?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions