...
| Code Block |
|---|
<SCRIPT LANGUAGE="JavaScript" src="<%= request.getContextPath() %>/utils.js"></script>
|
That needs to be in the <HEAD> element. It's in jsp/layout/header-default.jsp but if you have a locally modified version, your modified copy might not have this line.
- The e-person tool is a pop-up window. Check that your browser isn't blocking pop-ups for your DSpace installation.
This pop-up window was, in retrospect, a controversial point. Post explaining the decision - If your site 'skin' has a form in it (e.g. , a search box) this breaks the JavaScript, specifically the references in `jsp
jsp/utils.js`jsto `windowwindow.document.forms0`forms0.- See http://sourceforge.net/tracker/index.php?func=detail&aid=1155173&group_id=19984&atid=119984 this bug report Another way to fix this problem may be to remove the form from the skin in
dspace-admin/eperson-main.jsp. If, for example, you placed a search box in your location bar, changinglocbar="/dmirror/http/wiki.dspace.org/link"tolocbar="off"in the dspace:layout tag in eperson-main should resolve the issue.
- See http://sourceforge.net/tracker/index.php?func=detail&aid=1155173&group_id=19984&atid=119984 this bug report Another way to fix this problem may be to remove the form from the skin in
How do you append data from a test server to a production environment?
...
Many people have run into trouble getting DSpace running on Redhat/Fedora Core Linux, specifically, encountering CLASSPATH errors and relating to 'libgcj'.
The easiest way to resolve this is to remove all the PM-based Java components, and install the original binary packages: Java SDK from Sun, and Ant and Tomcat from Apache.org.
To remove the PM Java stuff, do:
| Code Block |
|---|
rpm \-e libgcj
|
This will probably throw up a load of dependency errors. You'll need to remove the packages that depend on libgcj too.
Another useful list from RichardJones of packages he had to remove from Fedora Core 2:
...
If filter-media appears to hang after it creates the thumbnails and indexes text content, you may consider running filter-media as root. For some reason, certain users report that =filter-media= will hang after printing the following message:
Creating search index:
...
If something doesn't seem to be working, you can often find out more by upping the logging level of DSpace. To do this:
1. Edit dspace/config/log4j.properties.
2. Change the level by changing this line:
| Code Block |
|---|
log4j.rootCategory=INFO, A1
|
to this:
| Code Block |
|---|
log4j.rootCategory=DEBUG, A1
|
3. Restart Tomcat (or Resin, etc.).
Now you'll find there's a lot more information in dspace/log/dspace.log. You can switch on and off logging for particular DSpace classes. For example, if you just want to know about SQL queries going to the database, you could leave the main level above as INFO, and instead add the following line (then restart Tomcat):
| Code Block |
|---|
log4j.logger.org.dspace.storage.rdbms.DatabaseManager=DEBUG, A1
|
More information about DSpace log files is available in the DSpace System Documentation.
...