-
Notifications
You must be signed in to change notification settings - Fork 3
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
Bizarre "FATAL" On My End. #225
Comments
Try complete uninstall and reinstall. |
Uninstalled...reinstalled...the error still pops up right after the GUI, before opening my feed. |
Does the path "C:\Users\Adam\Documents\Channel Feed Manager\Temp" exist on your install? You are the only one experiencing this error. I think this is isolated to your configuration on UTM. |
Yes, the path is there. Very odd. I don't think it's causing an issue other than the pop-up. Thank you. |
AHHH...The Temp folder is EMPTY. There is no "Do Not Show.json" in there. |
Do you have "write" access to the folder? |
It appears you have read-only access to the files in the temp folder. The software tries to write a file into that folder. You must have write access for that to work. |
It's letting me write and read. I tried removing the CFM folder and reinstalled again. I launched with a completely clean CFM. However, the error persists. I'll try adding to the feed and see if anything else arises later. I just want to be free of needing AWS. 😂 I'll report back just in case someone else runs into this odd situation. |
Describe the bug
As a Mac guy, I've been running CFM on a Windows server vis AWS. I've just switched over to UTM (so cool, BTW!). I re-ingested my current feed, but on launch I get a supposedly FATAL error claiming "Do Not Show json" is invalid. Unlike Mortal Kombat, this fatality doesn't appear to be fatal at all. The app goes on to function properly. I tried reinstalling, but I'm still getting the error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No FATAL error.
Screenshots
Version number:
Additional context
Thinking there's an easy fix here, but 🤔
The text was updated successfully, but these errors were encountered: