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
Event export with ZM_USE_DEEP_STORAGE option set #506
Comments
This issue was reported in Debian as well: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723706 I confirm it is still exist in v1.28.1. Apparently this is because export is not using |
When this was reported initially, I thought this described an issue with the location on the filesystem where the export data was written. Rather, the issue is with one of the generated html files inside the exported archive file. And it is just zmEventImagesMaster. The other files in the exported archives all point to the correct location. I see now. Merging |
skins/classic: fix HTML export with USE_DEEP_STORAGE (Closes: #506).
When the ZM_USE_DEEP_STORAGE option is set, the event export function generates faulty javascript in the zmEventImagesMaster HTML file. It does not use the deep path format, so the links to the actual event data are broken.
The issue appears to be with the file .../skins/classic/includes/export_functions.php. Someone offered a solution on the ZM forums, but it effectively hard-codes deep paths. See http://www.zoneminder.com/forums/viewtopic.php?f=29&t=18573.
This issue has also been reported on Ubuntu on Launchpad. https://bugs.launchpad.net/ubuntu/+source/zoneminder/+bug/1176128.
I am running Ubuntu 14.04.1 LTS and ZoneMinder 1.27, which I compiled from source.
The text was updated successfully, but these errors were encountered: