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.

Issue with Edit in Microsoft Office

andrew_sumner

Hi,

We are running Alfresco Community Edition v5.2f on CentOS 7, but have encountered an issue that I could use some help with:

In the Alfresco Share website, I have created a test folder and uploaded a Word document (docx), I then select the document so it appears in the on-screen editor, and then select "Edit in Microsoft Office" under the Document Actions. This generates a security prompt which I then click Yes to, and the Word 2016 application then opens, however the document never actually loads within Word (its just an empty window).

The laptop (client) I am working from is running Windows 10, Office 2016, Chrome web browser.

Alfresco is running out-of-the-box configuration.

Is there any specific configuration needed to get this feature to work? If not, what is the best way to investigate this issue?

Thanks in advance,

Andrew

Find more posts tagged with

Alfresco Content Services

Comments

cesarista

Hi:

You must activate SSL when using Alfresco Office Services. Do you ?

Prerequisites for using Alfresco Office Services | Alfresco Documentation

Regards.

--C.

andrew_sumner

Hi Cesar,

No I was previously using http://192.168.1.81:8080

Instead I am now using the SSL url https://192.168.1.81:8443. This gets me further.

I now get a Microsoft Word Security Warning dialog because Alfresco is using a self signed certificate that my machine doesn't trust. I can view the certificate and see it's issued to Alfresco Repository. If I then click Yes to accept the certificate and proceed, I get another Microsoft Word dialog saying:

Sorry, we couldn't open 'https://192.168.1.81:8443/alfresco/aos/test-folder/new file.docx'.

Any ideas?

Thanks,

Andrew

cesarista

Hi:

You need a valid SSL certificate (a self-signed is not the case), and the usual way involves a secured frontend (ex. Apache) configured as a reverse proxy. Besides, if your frontend is on the internet, you may use free Let's encript SSL certificates.

The self-signed certificate that you mention is for Alfresco and SOLR communication, it is not valid for this task.

Regards.

--C.

andrew_sumner

Hi Cesar,

Thanks for these pointers.

I don't suppose there is a guide/instructions for getting this feature to work?

It is for a lab environment at first (not internet facing), but ultimately it will be a live internet facing site once I can prove the features work.

I am not that familiar with these technologies, and so it could take me a while to figure it out if there is no step-by-step guide...

Thanks,

Andrew