We have just upgraded our repository module from 4.0 to 4.1 (and upgraded DNN too) and most of our PDF documents no longer open.
we get an Adobe error saying: "There was an error opening this document. The file is damaged and could not be repaired"
Some PDFs do open but most do not.
We are on DNN 9.6.1 ( we have recently done several upgrades from 7.4.2 but have been checking all modules along the way and the Repository did appear to work in other DNN versions. We don't really want to go backwards in DNN platform incase it's a security risk).
Is there a fix for this? or is the only way to re-upload the files? (could be over 200).
thanks.
Posted By sypa on 30 Jul 2020 05:27 AM We have just upgraded our repository module from 4.0 to 4.1 (and upgraded DNN too) and most of our PDF documents no longer open. we get an Adobe error saying: "There was an error opening this document. The file is damaged and could not be repaired" Some PDFs do open but most do not. We are on DNN 9.6.1 ( we have recently done several upgrades from 7.4.2 but have been checking all modules along the way and the Repository did appear to work in other DNN versions. We don't really want to go backwards in DNN platform incase it's a security risk). Is there a fix for this? or is the only way to re-upload the files? (could be over 200). thanks.
I don't expect that the upgrade really corrupted the files TBH. Can you acees them directly? (or are they in a secured folder..?) Anyway, I guess it's better to (also) post this issue @ https://github.com/DNNCommunity/DNN.Repository
we have just re-mapped them by deleting repository 4.1 re-installing repository 4.0 (which is more stable) and recreated a new module on each page (24 in total) and then re-assigned the appropriate module ID from the new module to the existing records.
another repository issue - it forces a description to be inserted for every repository. we've never had one before so this is a suprise and annoying because we really don't want one and now all users see an ADMIN notice!
ADMIN: Select Repository Settings from the Module Settings drop down menu to set the Repository Description text as well as set the number of objects to be displayed on each page.
- update - i've managed to remove the above message now in repository/app_localresources/repository.ascx.resx
Posted By sypa on 30 Jul 2020 11:30 AM another repository issue - it forces a description to be inserted for every repository. we've never had one before so this is a suprise and annoying because we really don't want one and now all users see an ADMIN notice! ADMIN: Select Repository Settings from the Module Settings drop down menu to set the Repository Description text as well as set the number of objects to be displayed on each page. - update - i've managed to remove the above message now in repository/app_localresources/repository.ascx.resx
Please log these issues on the github repo I mentioned before.
Posted By Timo Breumelhof on 30 Jul 2020 12:07 PM Posted By sypa on 30 Jul 2020 11:30 AM another repository issue - it forces a description to be inserted for every repository. we've never had one before so this is a suprise and annoying because we really don't want one and now all users see an ADMIN notice! ADMIN: Select Repository Settings from the Module Settings drop down menu to set the Repository Description text as well as set the number of objects to be displayed on each page. - update - i've managed to remove the above message now in repository/app_localresources/repository.ascx.resx Please log these issues on the github repo I mentioned before.
ok - i've reported the issue.
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.