FAQ

Why is Alfresco's MySpaces Web script not working with AWPr?

Alfresco's MySpaces Web script was written in a way that is tailored to work with their Web script portlet. It also assumes an embedded deployment where Alfresco and the portal are running in the same JVM. We have made some changes to this Web script and created a new one called AWPrMySpaces which should work with AWPr. You can downalod the AMP containing AWPrMySpaces here and you can read about how to use it here.

When I installed AWPrMySpaces I see the Web script in AWPr but there is an AJAX loader (hourglass) that spins forever and I don't see the documents.

This is probably due to cross-domain security. Since Alfresco and the portal are on two different app servers the AWPrMySpaces Web script is trying to connect directly to Alfresco (or the value of the alfUrl Web script parameter) and since that URL is on a different domain than the one running the portal your browser will not allow it. The solution to this issue is to front both Alfresco and the portal with a proxy (e.g. Apache Web server + mod_jk) and make sure you can access both portal and Alfresco using the same domain. You can read more about this here.

AWPrMySpaces exposes the Alfresco ticket in the browser and it can be sniffed. Is that secure?

Of course not . The AWPrMySpaces Web script was provided by us to the community merely as an example. It is not intended to be used in production since it's simply a rewrite of Alfresco's out-of-the-box myspaces Web script. Use it at your own risk.

There doesn't seem to be a way for me to download content directly from AWPr. Am I missing something?

Up till and not including AWPr version 1.4.0 direct downloads were not supported. But starting with AWPr 1.4.0 we are leveraging Portlet 2.0's resource phase to allow AWPr instances to stream content from Alfresco direcly to the end-user's browser. This is the desired approach so that we can maintain the claim that different AWPr instances on the same portal page can access different Alfresco instances.

I deployed AWPr and it's not authenticating with Alfresco.

AWPr relies on a custom Alfresco authentication component that we wrote called STAr (Secure Token Authentication rivet). You must install and configure the STAr AMP for AWPr to authenticate against Alfresco successfully. To read more about how to configure STAr click here.

Why are my HTML GET forms not working?

Most portals don't support HTML forms that use the GET method. It is better for you to use POST for all your forms. Using HTML forms that use the POST method is fully supported by AWPr starting with version 1.5.0.