MS Office integration - blinking...

[wit]

Hi everybody!

I've tried to use Alfresco integration with MS Office, but…

I have installed Integration sowtware ( http://sourceforge.net/project/showfiles.php?group_id=143373&package_id=237030&release_id=524564 ), configured Web Client URL - but then I press Alfresco Icon in MS Word (2003) - window with Alfresco login blinks (refreshing?) - and there no possibility to enter password or press Enter.

Someone have experience with such kind of problem?

[mikeh]

New problem - i can't open Word document

That file is not corrupted - i can open it in Alfresco in browser.

Possibly an Office bug involving CIFS authentication - are you using WebDAV or CIFS (i.e. did you populate the CIFS text box?)

Thanks,
Mike

[mikeh]

Hello again Mike,

Yes - they're all compatible.

The latest modules management also tool seems to be backward compatible
with everything.

Would you happen to know if this also applies to the other stuff (some of
which tends to appear without a version number) like the PHP integration /
PHP client library / Web service client / blog integration?

The Records Management hasn't actually changed since the middle of last
year, but I haven't seen in import properly into anything since the official 2.1
Community release: (the bug is listed on the JIRA).

In general it's best to assume they're not.

Mike

P.S. Also, please try not to hijack threads 😉

[sacco]

In general it's best to assume they're not.

Thanks, that was more or less my guess, although with the client libraries there's less at stake in the sense that they're likely either to work or else to break obviously without any collateral damage.

[wit]

New problem - i can't open Word document

That file is not corrupted - i can open it in Alfresco in browser.

Possibly an Office bug involving CIFS authentication - are you using WebDAV or CIFS (i.e. did you populate the CIFS text box?)

Thanks,
Mike

No, I haven't entered there some values.
Should I install some client/server parts of CIFS? Is there some description of that installation/configuration?

[mikeh]

No - you should be fine using WebDAV.

Have you tried loading an Office document using WebDAV via Windows Explorer? Do you happen to have a proxy server between you and the Alfresco server?

Mike

[wit]

No - you should be fine using WebDAV.

Have you tried loading an Office document using WebDAV via Windows Explorer? Do you happen to have a proxy server between you and the Alfresco server?

Mike

ops: I think "loading an Office document using WebDAV via Windows Explorer" is not the same with read/write files from/to some network place, isn't it? Is that Web Folder some special organized folder? How can check that possibility?

There is no proxy between me and Alfresco.

[sacco]

Yes - they're all compatible.

As far as I can tell, the tasks pane in the latest nightly build of the Office
2003 plugin can see nothing at all when run against either the 2.1 Community
release, or the last public nightly build of 2.2.0dev .

I start an advanced workflow in one instance, but the assignee never sees
anything in his instance, although the task does show up in the Web client.

[mikeh]

ops: I think "loading an Office document using WebDAV via Windows Explorer" is not the same with read/write files from/to some network place, isn't it? Is that Web Folder some special organized folder? How can check that possibility?

There is no proxy between me and Alfresco.

In Windows Explorer, create a new Network Place and browse to

http://<server>:8080/alfresco/webdav‍

Explorer knows how to speak WebDAV, so it should appear like a normal network drive.

Thanks,
Mike

[mikeh]

As far as I can tell, the tasks pane in the latest nightly build of the Office
2003 plugin can see nothing at all when run against either the 2.1 Community
release, or the last public nightly build of 2.2.0dev .

I start an advanced workflow in one instance, but the assignee never sees
anything in his instance, although the task does show up in the Web client.

Well the web scripts won't have changed and are completely independent of the actual add-in client, so I suspect there's something else going on there. Updating the client software has no effect on workflow, tasks, etc.

You can prove this for yourself by browsing to

http://<server>:8080/alfresco/wcservice/office/myAlfresco?p=‍

…although loading and saving of documents will throw Javascript errors due to the client code not being hooked into the browser, the basic information will be there as this is effectively the UI for the Office add-ins.

I've noticed you mention this before: you say you're running 2.2.0dev - presumably that was grabbed from our nightly build server before Christmas? If so, you're actually running a (very!) early version of 2.9 Labs before we updated version numbers. You might want to consider updating to 2.9B if you're in a position to do so. It's certainly not an early version of 2.2 Enterprise that's about to be released, so I wouldn't want you to confuse it like that.

Thanks,
Mike

[sacco]

I've noticed you mention this before: you say you're running 2.2.0dev -
presumably that was grabbed from our nightly build server before
Christmas? If so, you're actually running a (very!) early version of 2.9
Labs before we updated version numbers. You might want to consider
updating to 2.9B if you're in a position to do so. It's certainly not an early
version of 2.2 Enterprise that's about to be released, so I wouldn't want
you to confuse it like that.

It was the last nightly labelled 2.2.0dev (end of October), although there
was also a 2.9 nightly build available concurrently, but that was probably
just some confusion during the switch over.

The only reason I changed to that was that there were some bugs
blocking me in the 2.1 release that it fixed, but I was aiming to fix a build
and work from that rather than having a constantly moving target. 
However, given your comment, I'd probably better migrate that system to
2.9B or a recent nightly within the next week or two.  A pity I'm so busy
today…

Thanks, that information about the relationship between this build and the
recent developments is the most useful tip yet!