sbcrumb/nfoguard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: nfo logic long vs shortname

Browse Source
This commit is contained in:
SBCrumb
2025-09-22 11:02:12 -04:00
parent de3896b8c3
commit 3e5c80279f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
core/nfo_manager.py
+2 -2
View File
@@ -425,8 +425,8 @@ class NFOManager:
print(f" 🔍 Debug: existing_long_nfo = {existing_long_nfo}") print(f" 🔍 Debug: existing_long_nfo = {existing_long_nfo}")
print(f" 🔍 Debug: nfo_path.exists() = {nfo_path.exists()}") print(f" 🔍 Debug: nfo_path.exists() = {nfo_path.exists()}")
# Try to load existing NFO file (either standard or long-named) # Prioritize long-named file for migration, otherwise use standard file
source_nfo_path = nfo_path if nfo_path.exists() else existing_long_nfo source_nfo_path = existing_long_nfo if existing_long_nfo else nfo_path if nfo_path.exists() else None
print(f" 🔍 Debug: source_nfo_path = {source_nfo_path}") print(f" 🔍 Debug: source_nfo_path = {source_nfo_path}")
if source_nfo_path: if source_nfo_path: