cancel
Showing results for 
Search instead for 
Did you mean: 

Using MSWord SPP,and using AWE create different file URLS

brucemoser
Champ in-the-making
Champ in-the-making
I have a fairly vanilla install of Web Quick Start. I created a folder called main-content. Then I created a file in said folder called file1.html. Back at the root index.html, I added file1.html as a static asset for the index.html page. If I open the file1.html in MSWord and add an image everything looks and goes well, until I open root index.html in a browser. The image is broken. Upon inspection the path is incorrect and is only relative to the folder it was created in, which it obviously not running in due to the static asset utilization. If I then open the same file in AWE and edit it, then do nothing but save, the image paths get updated to a relative path from the root which now when viewing index.html the images are no longer broken.

I have two issues with this.

One is that I assumed that there would be a setting somewhere to define the default path in a spp setting, but for the love and three days of internet searching, I cannot find one.

Two is that regardless of whether or not there is a setting (please let there be a setting) the spp interface and the awe should produce the same url path technique regardless if it is the right one or the wrong one (we all would prefer the correct one).

Has anyone else seen this behavior? Has anyone else found a solution other than opening every edit in awe and saving it?
1 REPLY 1

afaust
Legendary Innovator
Legendary Innovator
Hello,

I am unaware of any integration of AQS/AWE with the SPP support in Alfresco or any special treatment of content maintained via SPP that relates to these modules. How are you opening HTML files in MS Word via the SPP module? Are you using EditOnline in the Share UI or opening them from within MS Word? How are you "add an image" in Word to your HTML - via source code edit or some nifty Word tool?

My first educated guess is that, when you edit your HTML in Word, Word is unaware of any special URL treatment necessary for linked images and does its own thing, which Alfresco SPP does not correct as it assumes Word to behave correctly (crazy idea, I know, but it can't do anything else as it is unaware of the use case context). Using AWE on the other hand may include some cleanup logic in your content editors that auto-corrects subtle errors and is aware of the context - you are using a WCMS related component after all, which SPP is not.

Regards
Axel