Maura,
I discovered some similar circumstance s in which my css and js was not
loading properly.
I do not know if you circumstances are the same as mine, but the following
change to my sitemap.xmap helped
<map:match pattern="themes/**/static/**.js">
<map:read type="ConcatenationReader"
src="static/{2}.js">
<map:parameter
name="requestQueryString" value="{request:queryString}"/>
</map:read>
</map:match>
<map:match pattern="themes/**/static/**.css">
<map:read type="ConcatenationReader"
src="static/{2}.css">
<map:parameter
name="requestQueryString" value="{request:queryString}"/>
</map:read>
</map:match>
I noticed that your page also has the following error
The page at 'https://bir.brandeis.edu/handle/10192/22946/discover' was
loaded over HTTPS, but ran insecure content from
'http://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js':
this content should also be loaded over HTTPS.
Terry
On Mon, Jun 9, 2014 at 1:04 PM, Maura Carbone <[email protected]> wrote:
> Hello all,
> We recently upgraded our DSpace installation from 1.7 to 3.2 and switched
> to Discovery. On the majority of pages discovery works and displays
> correctly, but on pages where we have custom sub-themes, discovery does not
> display correctly.
>
> Correct display: https://bir.brandeis.edu/handle/10192/27330/discover
> Incorrect display: https://bir.brandeis.edu/handle/10192/22946/discover
>
> The error seems to be stemming from the sub-theme attempting to call the
> discovery-styles.css from the wrong path (/themes/static/css/discovery
> rather than /static/css/discovery), but we haven't been able to figure out
> why this is the case. This does not happen on the non-custom pages, so it
> must be something in the xsl or sitemap of the custom themes. We even tried
> creating a copy of static in the themes directory just to see if it would
> find the correct file but to no avail. Aside from this weird discovery
> display error all the other files seem to be pulling correctly. Discovery
> does appear to function correctly.
>
> Anyone have any ideas? I can send along the xsl and sitemap of one of the
> custom themes (they all use the same one with just some minor tweaks). We
> are using a Mirage-based xmlui theme.
>
> Thanks in advance.
>
> --
> Maura Carbone
> Digital Initiatives Librarian
> Brandeis University
> Library and Technology Services
> email: [email protected]
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://www.library.georgetown.edu/lit/code
425-298-5498
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
