Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
lucasjans opened this issue Dec 16, 2013 · 1 comment
Open

Comments

@lucasjans
Copy link

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?

@jsheely
Copy link
Contributor

jsheely commented Jan 3, 2014

Yes, That's a good idea. Only the files types in the include Host Settings include list should added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants