[gollem] Dynamic SMB location in gollem backend

[Soporte SCHOLEM]

Thank you, Matthew for your answer and suggestions. I would want to resume
our situation (maybe other guys have the same):
One year ago we installed Horde with basic modules (mail, schedule,
contacts, notes and tasks) in replacement of our Exchange Server 2003. The
result was great. Horde is a very nice and useful packet and was very well
accepted for users.
Now, after one year of usage and improvements, we would want to migrate our
MS file sharing and move all the user's data to Horde, by adding Gollem
module.
With this schema, users would have only one login for all (Horde login),
and would be able to access to all their content from anywhere by web
interface, becoming Horde to be the main Intranet page.
But we are seeing that our Gollem (that is a powerful tool) has some
problems:
1. Folders creation: if you create a new folder, Gollem keeps it in tmp
space until you put into (upload) the first file. If you just create the
folder and leave to other menu, Gollem deletes the tmp folder. i.e.: You
have to move some files from one folder to a new one. Then, you mark the
files and copy them the clipboard. Next, you pick on *create folder*, wrote
a name, pick OK and new folder *seems* to be created. If you go to that
"virtual" folder and paste from the clipboard, you get this error
message: 
*****************************************************************************
[folder] NT_STATUS_OBJECT_NAME_NOT_FOUND
  1. Gollem::copyFile() /var/www/horde/gollem/manager.php:171
  2. Gollem::_copyFile() /var/www/horde/gollem/lib/Gollem.php:497..........
*****************************************************************************

In order that no errors appear, you have to upload some file immediately
after of create the folder. So, the folder go from tmp space to disk space
and no error shows when you paste files from clipboard.
Is this a bug or a misconfiguration?. Anywone has the same problem?
2. Cut & paste: if you *cut* instead *copy* a file, you will always get
this error when you paste the file anywhere:
*********************************************************************
NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file [path\file]
  1. Gollem::moveFile() /var/www/horde/gollem/manager.php:169
  2. Gollem::_copyFile()/var/www/horde/gollem/lib/Gollem.php:480.............
*********************************************************************
Is this a bug or a misconfiguration? Does it have relation with ticket
#12106?

3. Gollem and WebDAV integration. When users have to edit files other than
txt or html, they have to download and upload them. This drawback is not
only in the additional job of upload, but also for leaving a copy of the
modified file at the desktop or download place. Finnaly, users won't use
Gollem's folders, but will use their desktop copies and this is not what we
want. I guess integration of WebDAV with Gollem would solve this issue, but
that integration is not developed yet. Will next versions of Gollem include
some of those changes?

Thank you in advance.
Have a nice day!
Carlos


> Matthew <mw at robotmouse.com> escribió:
>
>> On 07/01/14 11:54, Carlos Martinez wrote:
>>> I would tell you that I am also installing Gollem with smb backend and
>>> have some basic problems with the implementation. I would want to know
>>> if you had the same ones.
>>> The main problem is about the usage:
>>> *When my users have to edit a file other than txt or html (.doc, .xls,
>>> etc), they have to download it, edit it and upload it again. That is a
>>> undesired additional job for them*.
>>>
>>> I tried giving an alternative way to access their files: folders
>>> network sharing throug smb. But this schema is not compatible with file
>>> sharing of Gollem.
>>>
>>> I tested two backends: file and smb.
>>> Each have advantages and problems:
>>> *File* backend: due to www-data is the owner of folders, users can
>>> share them because security is taken from Gollem tables. This is great.
>>> But if folders are accessed from other environment out of Horde, all
>>> users can see all folders, because there is no security.
>>>
>>> *smb* backend: due to each user is owner of his folder, security is ok
>>> when they access from other environment out of Horde.
>>> But users cannot share folders because security of Gollem tables cannot
>>> override smb security.
>>>
>>> How did you solve the problem of downloading and uploading files when
>>> users need to edit a file?
>>
>> Hi Carlos - thanks for your reply and comments. I wish I had some good
>> answers for you, but I think I can only agree with you!
>>
>> As to editing files, I don't think theres anyway round downloading and
>> uploading, when accessing through a web interface. The mechanism just
>> isn't there to be able to do it - it's a browser limitation rather than
>> a Horde one. I guess in theory if you go the all MS route, there may be
>> some kind of ActiveX thing that could do it - but I'm really not up on
>> it. For me it's not really a big issue as I'm using Horde for
>> occasional/remote access to shares - when people are at the office, they
>> mainly have shares mounted directly via SMB.
>>
>> Which sort of leads to your next query about file vs smb - as far as I
>> can tell, you are right, but I don't really have a workaround to hand -
>> maybe somebody else does? I haven't really tried the folder sharing
>> feature of gollem, so I've not figured how it works with various types
>> of backend.
>>
>> You may want to take a look at pydio (formerly Ajaxplorer) which is
>> another online file manager which has some clever sharing stuff going on
>> - I had been using it until now and it is good - but I'm switching to
>> gollem since it allows my users access to everything via a single web
>> interface. If that's not so important, then pydio is worth looking at.
>> Matthew
> Carlos Martínez
> Responsable IT
> O.E.I. Scholem Aleijem
> Tel: (011) 4855-4200
> http://www.scholem.edu.ar
> ------------------------------------------------------------------------------------
> Antes de imprimir este correo, piense bien si es necesario hacerlo.
> El medio ambiente es un problema de todos.


------------------------------------------------------------------------------------
Antes de imprimir este correo, piense bien si es necesario hacerlo.
El medio ambiente es un problema de todos.