Hi Elmarie Just tried this, and in my case they are ending up in $DHIS2_HOME/documents, what is your home set to? are you sure the application can access that folder?
-- Morten Olav Hansen Senior Engineer, DHIS 2 University of Oslo http://www.dhis2.org On Wed, Jul 6, 2016 at 11:23 PM, Elmarie Claasen <[email protected]> wrote: > Hi all, > > > > From what I am told whatever resources you load into DHIS under Reports > > Resources and whether you add them to a dashboard those are stored in a > subfolder in the war file folder on the server. When the war is updated all > those files are destroyed and thus you don’t have those copies anymore. Any > reason why those resources are stored in the war file folder and not in the > same location as uploaded files on the dhis2_home or even better in the > database itself? > > > > The problem is that you add those documents to a dashboard and if you > update the war file they no longer available… best not to have an option to > share resources then if you need to reload them every time… > > > > I do understand that DHIS2 has the ability to store files but the use in > this case is for example to add manuals or SOPS or guidelines to the system > so the file storage is not ideal rather chose to use resources since it is > available in DHIS2. We also using it to load user access forms which may > not be intended usage but is useful and the reality is that every time the > war is updated everything that is uploaded is destroyed – quite a shock… > > > > I must also say that the documentation does not provide clear guideline on > how this feature should be used and a warning that anything you load there > is stored in the war file? > > > > Regards, > > > > *Elmarie Claasen* > > [image: Hisp logo] > > Project Manager > > Health Information Systems Program > > Tel: 041-367 1027 > > Cell: 082 374 2209 > > E-mail: [email protected] > > Skype: elmarie.claasen52 > > > > > > This message and any attachments are subject to a disclaimer published at > http://www.hisp.org/policies.html#comms_disclaimer > . Please read the disclaimer before opening any attachment or taking any > other action in terms of this electronic transmission. > If you cannot access the disclaimer, kindly send an email to > [email protected] > and a copy will be provided to you. By replying to this e-mail or opening > any attachment you agree to be bound by the provisions of the disclaimer. > > > > *This message and any attachments are subject to a disclaimer published at > http://www.hisp.org/policies.html#comms_disclaimer > <http://www.hisp.org/policies.html#comms_disclaimer>. Please read the > disclaimer before opening any attachment or taking any other action in > terms of this electronic transmission. If you cannot access the > disclaimer, kindly send an email to [email protected] > <[email protected]> and a copy will be provided to you. By replying to > this e-mail or opening any attachment you agree to be bound by the > provisions of the disclaimer.* > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
