The footer says:
Supplied free of charge with no support, no certification, no maintenance, no warranty and no indemnity by Alfresco or its Certified Partners. Click here for support. Alfresco Software Inc. © 2005-2009 All rights reserved.The footer includes Alfresco's logo by reading an image from the Alfresco website. This image is called a web bug, or beacon, and Alfresco can use the image request to their server to help track who is using Alfresco. The footer's underlined text links to pages on the alfresco.com website to provide warnings that the Labs version of Alfresco is not supported by Alfresco Software Inc. The right-side graphic links you to Alfresco's SourceForge download site.
Except for the web beacon image, I don't fault Alfresco Software for adding the footer to its web client. Alfresco Labs is a powerful -- free -- and flexible product. If used within an organization, it is not a bad thing that users are made aware that the product is not the supported Enterprise version. However, since I am using Alfresco on an internal website, and plan to customize the various JSP pages, displaying the warning on every one of my pages seems overkill and unnecessary. And I could do without sending tracking statistics to Alfresco Software.
Removing the global footer isn't a simple process, but it is pretty straightforward. The removal should be as simple as editing a globally included text file. Instead, those clever developers at Alfresco embedded the footer text into a fairly useful JSP tag. This
<r:page>JSP tag outputs the skeletal HTML page tags, and includes HTML to pull in global scripts and cascading stylesheets. It also includes code that can log how long it took Alfresco to build the JSP page. To remove the footer from your web pages, you need either to stop using the
r:pagetag or recompile the page tag to set the text to what you would like, which is what the instructions below cover.
r:pagetag that lives in the Alfresco web client JAR file isn't complicated. Assuming you already are using the Alfresco Labs 3 web application, the process should take you a half hour or less, with most of that time spent downloading and compiling code.
The steps below show you how to obtain the complete source code to Alfresco, make the necessary change to the Java page tag code, rebuild the web client JAR file, then replace the existing JAR file in your Alfresco server with the newly built one.
Prerequisites: You must have a Java compiler, a Subversion client, Apache Ant, and be able to use the command line. For Windows users without Subversion, you can install the SlikSVN client. Others can find a link to download a Subversion client from CollabNet's Tigris.org.
Here are the steps to rebuild the Alfresco web client with the altered JSP page tag. (You should be able to cut and paste these lines onto your command line if you remove the prompt character.)
- Create an empty directory for the source code
% mkdir alfresco-labs % cd alfresco-labs
- Use Subversion to download the Alfresco Labs source code
% svn co svn://svn.alfresco.com/alfresco/HEADor use the http protocol if you have internal firewall issues:
% svn co http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEADThe
svncommand will connect to the Alfresco Subversion repository and copy each of the files in the HEAD branch into your local directory. Total download size will be about 734MB. Depending on the speed of your connection, this might be a good time to get coffee, have lunch, check your email. If the Subversion URL doesn't work, check this page to see if Alfresco has changed the repository location.
PageTag.javato change/remove the page footer text
PageTag.javafile you want to edit is in the directory
HEAD/root/projects/web-client/source/java/org/alfresco/web/ui/repo/tag. The commands below will edit the file in Notepad for Windows or vi for Unix/Mac users. But you also can just navigate to the folder and edit the file with any editor.
% notepad HEAD\root\projects\web-client\source\java\org\alfresco\web\ui\repo\tag\PageTag.javaFor Unix variants:
$ vi HEAD/root/projects/web-client/source/java/org/alfresco/web/ui/repo/tag/PageTag.javaAt this point, you can decide what you want your new page footer text to say. The quickest edit is to completely remove all footer contents by changing line 115:
private static String alfresco = null;to:
private static String alfresco = "";Why this works is that static
alfrescovariable holds the contents of the page footer HTML (images and text), which is output by the overridden JSP tag library method
doEndTag. If the
alfrescovariable is null, which it is the first time the code is run, the
doEndTagmethod calls a private helper method,
getAlfrescoButton, to populate it.
If you want to change the footer text to something of your own choosing, or perhaps you want to retain the Alfresco copyright notice because you won't be changing the web client's look and feel, you will want either to set the
alfrescovariable to the text of your choosing, or edit the
getAlfrescoButtonmethod and/or some of the variables it uses to build up the footer text.
For example, if you want to retain the copyright statement but remove the warning text, edit the
ALF_COPYconstant on lines 103-112 to remove the text you don't want:
private final static String ALF_COPY = "Supplied free of charge with " + "<a class='footer' href='http://www.alfresco.com/services/support/communityterms/#support'>no support</a>, " + "<a class='footer' href='http://www.alfresco.com/services/support/communityterms/#certification'>no certification</a>, " + "<a class='footer' href='http://www.alfresco.com/services/support/communityterms/#maintenance'>no maintenance</a>, " + "<a class='footer' href='http://www.alfresco.com/services/support/communityterms/#warranty'>no warranty</a> and " + "<a class='footer' href='http://www.alfresco.com/services/support/communityterms/#indemnity'>no indemnity</a> by " + "<a class='footer' href='http://www.alfresco.com'>Alfresco</a> or its " + "<a class='footer' href='http://www.alfresco.com/partners/'>Certified Partners</a>. " + "<a class='footer' href='http://www.alfresco.com/services/support/'>Click here for support</a>. " + "Alfresco Software Inc. © 2005-2009 All rights reserved.";If you want to keep some of the text but remove the web beacon image or SourceForge graphic, you will need to edit the
getAlfrescoButtonmethod or set the
alfrescovariable as discussed previously.
getAlfrescoButtonmethod does not add structural HTML text to the footer, so setting the
alfrescovariable directly with your chosen text is a viable option. If you use HTTPS on your website and you want to use an image in your footer, have a look at the technique used in the
getAlfrescoButtonmethod to change the image URL based on the request scheme. It's a handy way to avoid having web browsers complain about an encrypted page using non-encrypted components.
With the code edited, you are ready to rebuild Alfresco.
- Rebuild the web client application
Here is where you need Ant. Use the build target to rebuild the project modules. The default target will attempt to deploy the rebuilt WAR file, so make sure to use the "build" target.
% ant -f HEAD\root\build.xml buildFor Unix:
$ ant -f HEAD/root/build.xml buildYou will see several warnings about the use of deprecated methods and the like. But the code should build correctly.
The Ant task should rebuild the Alfresco JAR files and the WAR file. The rebuilt
alfresco-web-client.jarfile is the one that contains the repository JSP tag you want to replace. The Ant task creates this JAR file in the directory
- Copy the alfresco-web-client.jar to your Alfresco webapp
Copy the JAR file to your exploded WAR file directory location under the
WEB-INF/libdirectory. If you deploy Alfresco as WAR file rather than exploded WAR, you can use the full
alfresco.warfile that you also will find in the
Gone is the footer from this and all Alfresco web client pages.