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
After completing the parsing of the OPML-file, sometimes the warning
Operation result: some feeds were not loaded properly. Check the log for more information.
appears in the Import feeds dialog. However, there is no button or link to view the log in this window, and the main application window is blocked. If the user closes the Import feeds window and opens the Application log, he will see an empty window. That is, the notification is meaningless, and in the current situation it should be replaced with something like
Operation result: some feeds were not loaded properly. Close the Import Feeds window, open the Application Log window, and run the parsing again to see what exactly went wrong.
Or, better yet, allow the user to get a list of feeds that were not successfully parsed directly in the Import feeds window. With the ability to copy their addresses for manual checking or searching for the corresponding lines in the imported file.
Or, another option, do not block the main application window, and write to the log everything that happens with overwriting the oldest records when the user-specified log file size is reached. Or creating a new file when the limit is reached. But then in the application settings you will need to add both the limit for the log file and the number of files to be stored. And the ability to disable logging.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
After completing the parsing of the OPML-file, sometimes the warning
appears in the
Import feeds
dialog. However, there is no button or link to view the log in this window, and the main application window is blocked. If the user closes theImport feeds
window and opens theApplication log
, he will see an empty window. That is, the notification is meaningless, and in the current situation it should be replaced with something likeOr, better yet, allow the user to get a list of feeds that were not successfully parsed directly in the
Import feeds
window. With the ability to copy their addresses for manual checking or searching for the corresponding lines in the imported file.Or, another option, do not block the main application window, and write to the log everything that happens with overwriting the oldest records when the user-specified log file size is reached. Or creating a new file when the limit is reached. But then in the application settings you will need to add both the limit for the log file and the number of files to be stored. And the ability to disable logging.
Beta Was this translation helpful? Give feedback.
All reactions