Hi Patrick,
You mean you are disabling access to single files through the reverse
proxy or are you forbidding sync client usage at all in your setup ?
To get the file list you currently need to iterate over the "tr" elements:
$('#fileList tr').each(function() {
var $tr = $(this);
// do something with the $tr
});
Currently there is no better way but I hope we can add utility functions
in the future.
If you want access to a single file, you can use:
$tr = FileList.findFileEl('filename.txt');
It will give you the tr matching the file.
Hope this helps.
Cheers,
Vincent
On 02/24/2014 10:35 AM, Hoffmann, Patrick wrote:
> Hi Vincent,
>
> thanks I will look in the FileActionsReady trigger, sounds like what i was
> looking for, but that makes new questions, because I'm
> not familiar with the apis.
>
> Assumed, I add:
>
> $('#fileList').on('fileActionsReady',function(){
>
> });
>
> in the JS file, how am I supposed to get each filename in the filelist?
> Should I filter the fileList for the <tr> tags, or is there a better way,
> maybe with the OC object?
> In the fileActionsReady should be a foreach, calling the workin function with
> the
> correct filename parameter.
>
> About the block, I disabled any access from the reverse proxy, so only port
> 449 is allowed, i only need to disable the row at the OC webpage.
>
>
> Regards,
>
> Patrick
>
>
>
> BITO-Lagertechnik Bittmann GmbH
>
> Obertor 29
> 55590 Meisenheim
> Germany
>
> Tel: +49 (0) 6753 122 0
> Fax: +49 (0) 6753 122 399
>
> E-Mail: i...@bito.de
> http://www.bito.de
>
> Geschäftsführer: Werner Magin, Winfried Schmuck | HRB 2704 Bad Kreuznach |
> Gesellschafter: Fritz Bittmann Holding GmbH | USt-ID: DE 811 202 181
>
>
> *************************************************************************************
> Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und
> kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material
> enthalten. Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die
> des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von
> BITO-Lagertechnik Bittmann GmbH dar. Sind Sie nicht der Empfänger und haben
> diese E-Mail irrtümlich erhalten, sind jegliche Verwendung, Veröffentlichung,
> Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail strengstens
> untersagt. Jede ausgehende E-Mail wird von uns mit höchster Sorgfalt auf
> Viren geprüft. Jedoch übernehmen weder BITO-Lagertechnik Bittmann GmbH noch
> der Absender (Patrick Hoffmann) die Haftung für Viren; es obliegt Ihrer
> Verantwortung, die E-Mail und deren Anhänge auf Viren zu prüfen.
>
> This email is exclusively meant for the addressee and may contain
> confidential information or information which can be classified as
> professional secret. Any view or opinion stated in this email is that of the
> author and does not necessarily represent the view or the opinion of
> BITO-Lagertechnik Bittmann GmbH. If you are not the addressee and if this
> email has been transmitted to you by mistake, you may not make use of,
> publish, transmit, reproduce or print the information contained therein for
> whatever purpose. We take every reasonable care to check all out-bound emails
> for viruses. However, neither BITO-Lagertechnik Bittmann GmbH nor the sender
> (Patrick Hoffmann) can be held liable for the occurrence of viruses and any
> consequential damages. It is therefore the addressee's sole responsibility to
> check incoming emails and attachments for viruses.
> *************************************************************************************
> Anhänge:
> Versand am 24.02.2014 10:35 von Patrick Hoffmann
>
> -----Ursprüngliche Nachricht-----
> Von: devel-boun...@owncloud.org [mailto:devel-boun...@owncloud.org] Im
> Auftrag von Vincent Petry
> Gesendet: Montag, 24. Februar 2014 10:05
> An: List for Developers of ownCloud
> Betreff: Re: [owncloud-devel] [app] Workin2gether - support request
>
> Hi Patrick,
>
> The file actions can currently only be added from the JS side, not PHP.
>
> A similar case like yours is for shared files, which work like this.
> 1. File list is loaded
> 2. Event "fileActionsReady" is triggered (see
> "apps/files_sharing/js/share.js")
> 3. Call to OC.Share.loadIcons (in "core/js/share.js") which load the sharing
> information 4. Update to file share icons
>
> You might want to do something similar in your case.
>
> I'm not sure whether locking the files the way you do is a good idea.
>
> Will you try and block the sync client from uploading by returning 403 for
> locked files ? I'm not sure what the sync client will do in such cases, it
> will probably skip that file and retry later.
>
> Cheers,
>
> Vincent
>
> _______________________________________________
> Devel mailing list
> Devel@owncloud.org
> http://mailman.owncloud.org/mailman/listinfo/devel
>
> _______________________________________________
> Devel mailing list
> Devel@owncloud.org
> http://mailman.owncloud.org/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
Devel@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/devel
