And running without a try clause, the following showed in the bundle log
File "/share/MD0_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Plug-ins/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/parsekit.py", line 345, in ElementFromURL
).content, encoding=encoding, max_size=max_size)
File "/share/MD0_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Plug-ins/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/parsekit.py", line 300, in ElementFromString
check_size(string, max_size)
File "/share/MD0_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Plug-ins/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/parsekit.py", line 23, in check_size
raise Framework.exceptions.APIException("Data of size %d is greater than the maximum size %d" % (len(data), max_size))
APIException: (2103, 'Data of size 8133895 is greater than the maximum size 5242880')
So in my book, the framework does create an exception in check_size function, if the database is corrupted....
Now above is fine for me, but....
Since it simply throw an exception, I have sadly no way of tracking down the defective element :(
Would be nice, if the exception @ least told us where it choked, or ?
Hehehe.....And yes.....When posting, I was typing from memory :rolleyes:
Code is how ever correct, and framework still has a limit defined as max_size for an element size, which make sense, but leaves 3.Party in the dark here.....
In order for the user to fix it, so neither PMS, clients nor 3.Party plugin's breaks down, and we end up with a sad user, leaving the Plex sphere, since "It simply doesn't work"
I apologize for the silly questions. I like learning new things. Just tell me to stop if I'm getting out of hand with these questions. :D
Looking in the install package for the Synology versions I see sqlite files. Maybe because the extension is different it looks like the so file is not there? Or the installer is not installing them properly? Can you just extract the file and place it in the Plex folder to give you the feature you need?
Synology Intel - libsqlite3.so.0
Synology ARM - libsqlite3.so, libsqlite3.so.0, and libsqlite3.so.0.8.6
And an update here, if anybody besides MovieFan is following this thread:
As said, I did have an entry that was buggy in the database, but after removing that, my Plex2CSV still refused to work, due to a framework created exception.
So I made a change in the framework, and made the max_size bigger for a small test, and bingo......Plex2CSV could now complete an export :)
My request does however still stand here.....
Please show in the log the data that the framework chokes on, when generating an exception
Also maybe reevaluate the value of max_size default value