Hello 
I have an installation of dspace 1.5.1 running on freeBSD.
 
I ran 1.4.1 for a while with few issues ......but when we upgraded the
server and installed 1.5.1 we started having issues.  
 
I am able to create communities and upload articles, but when I try to
search by community, author, title, subject or issue date I get Internal
System errors.
 
In Manakin, I can do a straight search and it seems to work, by if I try
to search by author, or title, etc I get a
"java.lang.NullPointerException" error
 
Please help!
 
best
David
 
David Marcinkowski
Associate Director
Academic Computing
Manhattan Campus
Pratt Institute
 

-----Original Message-----
From: Mark Diggory [mailto:[email protected]] 
Sent: Wednesday, July 08, 2009 5:44 PM
To: Patrick K. Etienne
Cc: [email protected]
Subject: Re: [Dspace-tech] DSpace (Manakin) - entities & link/meta tags


I would highly recommend that the content of these meta tags needs to
remain escaped as so to be embedded into an html attribute value
properly, otherwise you are violating the html spec. 

Mark


On Wed, Jul 8, 2009 at 1:09 PM, Patrick K. Etienne
<[email protected]> wrote:


DSpace Community, 

I've been working on a fairly in-depth (Manakin) redesign for a DSpace
instance and am having trouble when displaying simple or full item
records. On those two page types, additional information is embedded
within the "head" section of the html code in the form of "link" and
"meta" tags. The "<" and ">" symbols that open and close the link/meta
tags are showing up within the source as "&gt;", "&lt;". The source
seems to be from the "buildHead" template within the "structural.xsl"
stylesheet. Near the bottom of that template is the following code:


            <!-- Head metadata in item pages -->
            <xsl:if
test="/dri:document/dri:meta/dri:pageMeta/dri:metada...@element='xhtml_h
ead_item']">
                <xsl:value-of
select="/dri:document/dri:meta/dri:pageMeta/dri:metada...@element='xhtml
_head_item']"
                              disable-output-escaping="yes"/>
            </xsl:if>


My understanding is that the disable-output-escaping attribute should be
preventing this behavior, resolving those entities as the actual symbols
rather than representative counterparts. For some reason they are being
translated as entities rather than being taken as literals. If anyone
has any suggestions, I'd be very much obliged.

Many Thanks!

 - Patrick E.




---
Patrick K. Étienne
Systems Analyst
Digital Library Development
Library and Information Center
Georgia Institute of Technology
email: [email protected]
phone: 404.385.8121

"Mediocre Writers Borrow; Great Writers Steal" - T.S. Eliot


------------------------------------------------------------------------
------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will
have
the opportunity to enter the BlackBerry Developer Challenge. See full
prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech




------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to