cancel
Showing results for 
Search instead for 
Did you mean: 

Word Plugin action:'Save to Alfresco' -> wrong

jwtenpas
Champ in-the-making
Champ in-the-making
I use CFIS which works fine when I us the, save to menu-option in Word.

When I use the Alfresco Word plugin (CFIS drive filled in the configuration option: CFIS server), the "save to alfresco" action generates an error stating that the filename is not valid (I use the name: test).

I 've tried several  CFIS configuration alternatives (see below), but they all do not work.

When I leave the CFIS server configuration option blank, the "save to my alfresco" action works, but it creates a new space of which the name consists of the last 8 characters of the name of the Company Home SPACE.  In this space there is a sub-space( same name as my home space) in which the dokument is saved.

Obviously this is not what I want. I want a document saved in the active space, and not in a self generated space. I changed the name of the Company Home space, could this be the reason for above behavour?

I tried the following CFIS configurations:

\\10.54.7.9\alfresco
\\10.54.7.0\\Alfresco
\\10.54.7.9\alfresco\
\\10.54.7.0\\Alfresco\
\\Kantoorjw_A\alfresco\
\Kantoorjw_A\alfresco
\\Kantoorjw_A\alfresco\
\\Kantoorjw_A\alfresco
O:\ (name of mapped drive which works fine

Hopfully someone can help

My compliments to the developers of the plugin. When the above problem is solved the plugin forms a ver nice interface to the alfresco document managementsystem!

Kind regards

Jan-Willem
2 REPLIES 2

mikeh
Star Contributor
Star Contributor
Hi,

Word's "Save As…" API can be troublesome if Windows hasn't cached an authentication session for that *exact* network path. Word's error message is less than useful ("invalid filename") but that sounds like what you're experiencing.

The key to getting a seamless CIFS connection working with the add-in is to make sure that when you do Start->Run… and type the CIFS path into the box, Explorer shows the files and folders without prompting for username and password. It's that authentication prompt that Word refuses to show when using the API - hence the error. Unfortunately there's very little the add-in can do to mitigate this situation.

I 've tried several  CFIS configuration alternatives (see below), but they all do not work.

[…]

I tried the following CFIS configurations:

\\10.54.7.9\alfresco
\\10.54.7.0\\Alfresco
\\10.54.7.9\alfresco\
\\10.54.7.0\\Alfresco\
\\Kantoorjw_A\alfresco\
\Kantoorjw_A\alfresco
\\Kantoorjw_A\alfresco\
\\Kantoorjw_A\alfresco
O:\ (name of mapped drive which works fine
The add-in supports using mapped drives as the CIFS path, so you can go ahead and use that if you like. Presumably you asked Windows to save the username and password when you mapped the drive?

When I leave the CFIS server configuration option blank, the "save to my alfresco" action works, but it creates a new space of which the name consists of the last 8 characters of the name of the Company Home SPACE.  In this space there is a sub-space( same name as my home space) in which the dokument is saved.

Obviously this is not what I want. I want a document saved in the active space, and not in a self generated space. I changed the name of the Company Home space, could this be the reason for above behavour?
That would be possible if you're not using code (both Alfresco server and add-in client) from after 19th July - see http://issues.alfresco.com/browse/AWC-1346 for details of that fix, which is in 2.1 Community Final.

My compliments to the developers of the plugin. When the above problem is solved the plugin forms a ver nice interface to the alfresco document managementsystem!

Kind regards

Jan-Willem

Thanks for the kind words!

Mike

jwtenpas
Champ in-the-making
Champ in-the-making
Hi Mike,

Thank you very much for your quick answer. I found out that:

That would be possible if you're not using code (both Alfresco server and add-in client) from after 19th July - see http://issues.alfresco.com/browse/AWC-1346 for details of that fix, which is in 2.1 Community Final.

was the course of the problem. So after installing versions form after 19th July, my problems are solved.

With kind regards,

Jan-Willem