nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

edit .doc word files online?

targa2000

Is it possible to edit .doc files in Share document library without having to download and then upload the changed file again?

Find more posts tagged with

Comments

mikeh

Yes, if you've got the Sharepoint ("vti") module installed and you're using Internet Explorer. Otherwise no, sorry.

Thanks,
Mike

fselendic

Online Edit works for me. With some problems with versioning.

1. I click on Online Edit in Explorer, Windows XP ask for credentials, Word 2007 SP2 opens file, I can see document/space info on the right. Document is locked in Share Document Library. So far, so good.
2. Change something, press Save, Word saves changed document, still locked, expected behavior.
3. Version stays 1.0. I've seen webcasts with Word 2003, and on just opening document (without Check out), seems to me that it should up minor version (1.1). MS Sharepoint actually asks Minor/Major/Comments. Alfresco leaves it at 1.0, but changes Date/Time of last change
4. Check out document, change something, Check In. Now it ask for Comments, however, on a first Check-in, version stays 1.0. Subsequent Check-ins do however change versions (2.0, 3.0, etc…)
5. None of the above works with Wndows 7, documents are always opened in Read-only mode

Am I doing something wrong? Any tweaks that I should do in Word 2007/Alfresco?

gronfelt

Online Edit works for me. With some problems with versioning.

1. I click on Online Edit in Explorer, Windows XP ask for credentials, Word 2007 SP2 opens file, I can see document/space info on the right. Document is locked in Share Document Library. So far, so good.
2. Change something, press Save, Word saves changed document, still locked, expected behavior.
3. Version stays 1.0. I've seen webcasts with Word 2003, and on just opening document (without Check out), seems to me that it should up minor version (1.1). MS Sharepoint actually asks Minor/Major/Comments. Alfresco leaves it at 1.0, but changes Date/Time of last change
4. Check out document, change something, Check In. Now it ask for Comments, however, on a first Check-in, version stays 1.0. Subsequent Check-ins do however change versions (2.0, 3.0, etc…)
5. None of the above works with Wndows 7, documents are always opened in Read-only mode

Am I doing something wrong? Any tweaks that I should do in Word 2007/Alfresco?

I've seen the same behaviour, where files are not versioned upon saving via the Sharepoint interface. However, it seems that if I manually set the versionable aspect on a document (by removing the versionable aspect and then adding it again) it's versioned correctly (but without the ability to add a comment) when saved from Word. Not sure why this happens and how to fix it though.

As for Windows 7, that seems to be a problem that's related to the fact that Alfresco does not fully implement the WebDAV standard (Sharepoint/VIT is just WebDAV, with some extras added). Windows 7 makes use of a method called PROPPATCH, but Alfresco just responds to that method with "not implemented". This issue is marked as fixed in the Enterprise tree, so I guess there's a good chance that the fix will be included in the next community release.

fselendic

Thanks a lot, I will try versioning aspect trick. Although, I did take a look at that before, and all documents in Share doclib should be versionable by default.

mikeh

This versioning issue sounds reproducible. Could one of you raise it in JIRA please?

Thanks,
Mike

gronfelt

This versioning issue sounds reproducible. Could one of you raise it in JIRA please?

Thanks,
Mike

I've tried to reproduce it, but I'm not really sure where the actual problem is. It seems to be related to the fact that documents that are uploaded in Share are marked as versionable, but they're really not versionable until they're actually versioned (by uploading a new version) or have the versionable aspect added manually.