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
I am also using some cronjobs to extract metadata from the nZEDb-Database. I recognized, that the xml in table releaseextrafull row mediainfo is containing invalid xml in the latest nZEDb Version. Some node names start with numbers which is not allowed. Here an example:
<writing_application>
<0>mkvmerge v7.1.0 ('Good Love') 64bit built on Jul 27 2014 13:06:55</0>
<1>mkvmerge v7.1.0 ('Good Love') 64bit built on Jul 27 2014 13:06:55</1>
</writing_application>
The xml looked fine in my old nZEDb build. I suspect this has something to do with the usage of the php-mediainfo wrapper. Below is a comparison of the old and new xml structure.
Hi,
I recently set up a new nZEDb instance on Ubuntu 20.04 using the following guide https://github.com/nZEDb/nZEDb/wiki/Install-Guide:-Ubuntu-18.04 (was using a pretty old version on Ubuntu 14.10 before). Everything is working fine.
I am also using some cronjobs to extract metadata from the nZEDb-Database. I recognized, that the xml in table
releaseextrafull
rowmediainfo
is containing invalid xml in the latest nZEDb Version. Some node names start with numbers which is not allowed. Here an example:The xml looked fine in my old nZEDb build. I suspect this has something to do with the usage of the php-mediainfo wrapper. Below is a comparison of the old and new xml structure.
new mediainfo.xml structure:
Old mediainfo.xml structure:
The text was updated successfully, but these errors were encountered: