RE: [dspace-tech] "Front page content" not displaying

2016-09-22 Thread Shedd, Julie
It really is the darndest thing. Initially un-logged-in: incorrect view. 
Logged-in: correct view. Logged-out-again: correct view.

I tried Alan’s solution and it appears to have done the trick – I’m having 
others check and they are reporting that while the site is slow (which is not 
new) once it loads, it loads correctly. Thanks, Alan!

---
   Julie D. Shedd
   Digital Initiatives Librarian, Mississippi State University 
Libraries
   (662) 325-0300 | 
jsh...@library.msstate.edu | 
http://library.msstate.edu/juliedshedd

From: Alan Orth [mailto:alan.o...@gmail.com]
Sent: Wednesday, September 21, 2016 11:40 PM
To: George Kozak ; Shedd, Julie 
Cc: DSpace Technical Support ; Huddleston, Paul 
; MML-HelpDesk 
Subject: Re: [dspace-tech] "Front page content" not displaying


Julie,

What if you clear the XMLUI cache from the DSpace control panel (under Java 
settings)? Also, if you're feeling adventurous, in Chrome or Firefox, you could 
try opening the developer tools (F12 probably) and look for errors, like 
scripts or images that have failed to load for some reason.

Regards

On Thu, Sep 22, 2016, 02:45 George Kozak 
> wrote:
Julie:
H...so if you're not logged in, the view is correct?   This has me stumped. 
 Maybe someone else may have an idea.   I wonder if there is something with the 
CSS?
Sorry I can't be of more help.
George Kozak
Cornell University


On Wednesday, September 21, 2016, Shedd, Julie 
> wrote:
That could be, I suppose. We haven’t been updating the permissions, either, 
though, and the problem only started last week – what might have caused the 
change?

Also, I noticed after I log out, I still get the “correct” view. Odd.

---
   Julie D. Shedd
   Digital Initiatives Librarian, Mississippi State University 
Libraries
   (662) 325-0300 | 
jsh...@library.msstate.edu | 
http://library.msstate.edu/juliedshedd

From: George Kozak [mailto:gkoz...@gmail.com]
Sent: Monday, September 19, 2016 6:55 PM
To: Shedd, Julie >
Cc: DSpace Technical Support 
>; 
Huddleston, Paul 
>; 
MML-HelpDesk 
>
Subject: Re: [dspace-tech] "Front page content" not displaying

Julie:
This may not be your problem, but, in the past, we had this problem if there 
was some html coding problem with the content of our home page.  In our case, 
we have code that modifies the content of the home page on a daily basis, and 
sometimes our html comes out malformed, and XSLT chokes on malformed html.  
However, since you are not changing the home page, could it be some kind of 
permission problem?
George Kozak
Digital Library Specialist
Cornell University

On Monday, September 19, 2016, Julie Shedd 
> wrote:

[https://lh3.googleusercontent.com/-CHa0hg5OKMU/V-BR42Q0JJI/EFo/BULzDXK90Y4_uq8dSmUKHWDM3C5pVTtDwCLcB/s320/MSUIR_screencap_1.jpg][https://lh3.googleusercontent.com/-ItmBdUYCKAY/V-BTF5RROyI/EFw/6TX5r2D1cEYhWcsjmoWACoOnlxckPiucACLcB/s320/MSUIR_screencap_2.jpg]
Hi all -
I have an odd problem.

We are running DSpace 5.5 with the Mirage2 XMLUI. We have not made any changes 
to the interface in quite a while (months), although we have been uploading 
materials and processing submitted materials.

The problem is this: For anyone not logged in, as well as for me when I log in 
with email address and password, the "intro" content is not displaying on the 
front page; the first thing that displays in the main content area is the 
Recently Added submissions (see MSUIR_screencap_1).

But for users who are logged in via Shibboleth, the front page displays 
correctly (see MSUIR_screencap_2).

Any idea what is happening here? We've restarted Tomcat, reloaded XMLUI, 
rebooted the server. It appears to be happening in Firefox, Chrome, and IE at 
least.
(Please keep in mind we are minus any "actual" developers right now and feel 
free to dumb it down. :) )

Thanks for any 

Re: [dspace-tech] DSpace current master: ERROR: prepared statement "S_29" does not exist

2016-09-22 Thread Tim Donohue

Hi Ilja,

Thanks for noting this. I have not yet encountered this error, but it 
definitely would be worth trying to find a way to reliably reproduce it 
(if possible).


From the error stacktrace you linked to, it looks like the problem 
originates in the UploadWithEmbargoStep of the submission process (at 
least in this example).  If you are able to recreate this error again, 
it might be interesting to see what is similar between each of the 
stacktraces.  Is it a single submission step to blame? Does the error 
occur more randomly (in different submission steps)?


Essentially if we can find a similarity between these stacktraces or a 
way to reliably reproduce the error, it would help us in determining 
whether this is only encountered with particular configurations/setups, 
and/or what the root cause may be.


You are welcome to create a ticket for investigating this issue, as that 
may be a better place to add notes should anyone encounter this issue.  
If we find it to be a non-issue, we can always close the ticket.


Thanks, and please do let us know if you find ways to reproduce or 
similarities between the error stacktraces.


- Tim

On 9/22/2016 5:28 AM, Ilja Sidoroff wrote:

I've been testing the latest git master (upcoming DS 6), and since pulling the 
latest changes on Tuesday, I've encountered errors like:

ERROR: prepared statement "S_29" does not exist
(a paste for the full stack trace: http://pastebin.com/2mLKNNHD)

(where "S_29" varies). The errors seem to happen when I use workflow functionality 
and try to submit something, or directly try to submit something to a collection. When the 
error state is on, I cannot start new submissions, upload bitstreams from the workflow, or 
upload bitstreams from administration->edit item - and possibly more. I don't know 
exactly what are the conditions for reproducing this nor I know how to recover from the 
state. I managed recovery once by restarting postgres, but in general it doesn't seem to 
help.

I first encountered this on Tuesday and asked help on irc. Helix84 did some 
googling and one reason this might happen, is some sort of concurrency problem, 
where the original PSTMT gets deleted/flushed out and is not available when 
resumed (unfortunately I don't have the reference or the irc log).

My environment is: Ubuntu 16.04, Java 1.8, Jetty 9, PostgreSQL 9.5. I'll 
continue examining the issue to determine if it is just something in my own 
environment or a genuine bug.

br,

Ilja Sidoroff
University of Eastern Finland



--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


Re: [dspace-tech] Question about search results

2016-09-22 Thread Sean Carte
Sorry, George; you're quite right.

Sean

On 22 September 2016 at 14:24, George Kozak  wrote:

> Thanks, Sean:
>
> I'm not sure.  I think that section is only for the browse indexes, but I
> will take a closer look.
> George Kozak
> Cornell University
>
> On Thu, Sep 22, 2016 at 3:00 AM, Sean Carte  wrote:
>
>>
>> On 21 September 2016 at 21:07, George Kozak  wrote:
>>
>>> My second question of the day.  Our discovery search results default to
>>> a "relevance" search.  I was asked today, if I could change the default to
>>> "title descending".  I am not sure where I need to make that change.  Can
>>> anyone provide some guidance?
>>
>>
>> I think this should work:
>>
>> edit dspace.cfg
>>
>> # Use this to configure the browse indices. Each entry will receive a
>> link in the
>> # navigation. Each entry can be configured in one of two ways. The first
>> is:
>> #
>> # webui.browse.index. =  : metadata : \
>> #   > prefix>.[.|.*] : \
>> #   (date | title |
>> text) : (asc | desc)
>> ...
>> webui.browse.index.3 = title:item:title:desc
>>
>>
>> Sean
>> --
>>
>>
>
>
> --
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> g...@cornell.edu
>



--

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


Re: [dspace-tech] Question about search results

2016-09-22 Thread George Kozak
Thanks, Sean:

I'm not sure.  I think that section is only for the browse indexes, but I
will take a closer look.
George Kozak
Cornell University

On Thu, Sep 22, 2016 at 3:00 AM, Sean Carte  wrote:

>
> On 21 September 2016 at 21:07, George Kozak  wrote:
>
>> My second question of the day.  Our discovery search results default to a
>> "relevance" search.  I was asked today, if I could change the default to
>> "title descending".  I am not sure where I need to make that change.  Can
>> anyone provide some guidance?
>
>
> I think this should work:
>
> edit dspace.cfg
>
> # Use this to configure the browse indices. Each entry will receive a link
> in the
> # navigation. Each entry can be configured in one of two ways. The first
> is:
> #
> # webui.browse.index. =  : metadata : \
> #prefix>.[.|.*] : \
> #   (date | title |
> text) : (asc | desc)
> ...
> webui.browse.index.3 = title:item:title:desc
>
>
> Sean
> --
>
>


-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


[dspace-tech] DSpace current master: ERROR: prepared statement "S_29" does not exist

2016-09-22 Thread Ilja Sidoroff
I've been testing the latest git master (upcoming DS 6), and since pulling the 
latest changes on Tuesday, I've encountered errors like:

ERROR: prepared statement "S_29" does not exist
(a paste for the full stack trace: http://pastebin.com/2mLKNNHD)

(where "S_29" varies). The errors seem to happen when I use workflow 
functionality and try to submit something, or directly try to submit something 
to a collection. When the error state is on, I cannot start new submissions, 
upload bitstreams from the workflow, or upload bitstreams from 
administration->edit item - and possibly more. I don't know exactly what are 
the conditions for reproducing this nor I know how to recover from the state. I 
managed recovery once by restarting postgres, but in general it doesn't seem to 
help.

I first encountered this on Tuesday and asked help on irc. Helix84 did some 
googling and one reason this might happen, is some sort of concurrency problem, 
where the original PSTMT gets deleted/flushed out and is not available when 
resumed (unfortunately I don't have the reference or the irc log).

My environment is: Ubuntu 16.04, Java 1.8, Jetty 9, PostgreSQL 9.5. I'll 
continue examining the issue to determine if it is just something in my own 
environment or a genuine bug.

br,

Ilja Sidoroff
University of Eastern Finland

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


[dspace-tech] Incorrect class in DSpace 5.x Discovery documentation

2016-09-22 Thread Alan Orth
Hi,

The DSpace 5.x Discovery documentation[0] incorrectly instructs the
user to use the "SidebarFacetConfiguration" class to add sidebar
facets, but this results in errors at startup:

Failed to startup the DSpace Service Manager: failure starting up
spring service manager: Error creating bean with name
'org.dspace.discovery.configuration.DiscoveryConfigurationService'
defined in file [/Users/aorth/dspace/config/spring/api/discovery.xml]:
Cannot resolve reference to bean 'defaultConfiguration' while setting
bean property 'map' with key [TypedStringValue: value [default],
target type [null]]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'defaultConfiguration' defined in file
[/Users/aorth/dspace/config/spring/api/discovery.xml]: Cannot resolve
reference to bean 'searchFilterAuthor' while setting bean property
'sidebarFacets' with key [0]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'searchFilterAuthor' defined in file
[/Users/aorth/dspace/config/spring/api/discovery.xml]: Error setting
property values; nested exception is
org.springframework.beans.NotWritablePropertyException: Invalid
property 'sortOrderSidebar' of bean class
[org.dspace.discovery.configuration.SidebarFacetConfiguration]: Bean
property 'sortOrderSidebar' is not writable or has an invalid setter
method. Does the parameter type of the setter match the return type of
the getter?

Using the "DiscoverySearchFilterFacet" class works as expected. DSpace 5.1.

Regards,

[0] 
https://wiki.duraspace.org/display/DSDOC5x/Discovery#Discovery-Searchfilters

-- 
Alan Orth
alan.o...@gmail.com
https://englishbulgaria.net
https://alaninkenya.org
https://mjanja.ch
"In heaven all the interesting people are missing." ―Friedrich Nietzsche
GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


Re: [dspace-tech] Question about search results

2016-09-22 Thread Sean Carte
On 21 September 2016 at 21:07, George Kozak  wrote:

> My second question of the day.  Our discovery search results default to a
> "relevance" search.  I was asked today, if I could change the default to
> "title descending".  I am not sure where I need to make that change.  Can
> anyone provide some guidance?


I think this should work:

edit dspace.cfg

# Use this to configure the browse indices. Each entry will receive a link
in the
# navigation. Each entry can be configured in one of two ways. The first is:
#
# webui.browse.index. =  : metadata : \
#   .[.|.*] : \
#   (date | title |
text) : (asc | desc)
...
webui.browse.index.3 = title:item:title:desc


Sean
--

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.