[Deploying Sakai] Ask the community: Your institution and Sakai bug reports

[Neal Caidin]

Are the stack traces missing from the log or just from the user experience?

Could it be related to this new property?

# Certain institutions consider Sakai error messages as overly verbose,
revealing technical information that is not relevant to the user (e.g.,
stack traces, SQL error messages, etc.).

# You can limit such disclosures by setting portal.error.showdetail to
false.

# DEFAULT: true

# portal.error.showdetail=false

(I thought the default was false, btw, because that is how it behaves on
nightly?)


-- Neal



On Fri, Jan 30, 2015 at 1:52 PM, Shawn Foster <sfoster9 at uwo.ca> wrote:

> Thanks for your response, Adam. Sounds like good customer support by
> following up.
>
> Has anyone else noticed the stack traces missing from bug reports in
> Sakai 10? Was this an intentional change for 10?
>
> Thanks,
> -Shawn
>
> --
> Shawn Foster
> eLearning Technology Support and Application Development
> Information Technology Services
> Western University
> London, Ontario, Canada
>
> On 15-01-30 1:34 PM, Adam Marshall wrote:
> > We look at bug reports where a user was logged in when it was generated.
> You can browse quite a lot of our Sakai without being logged in.
> >
> > I generally only follow it up if the user has left a comment. I rarely
> get a response from the user and have never been able to isolate a problem
> this way.
> >
> > Having said that I think it gives users confidence if someone reads
> their comments and gets in touch so I don't view it as a waste of time.
> >
> > When we moved to sakai 10 we lost the stack traces from the bug report.
> This made them less useful. I don't know whether its something we did or a
> new feature.
> >
> > Adam
> >
> > sent from my phone
> >
> > On 30 Jan 2015 17:45, Shawn Foster <sfoster9 at uwo.ca> wrote:
> > Some questions about Sakai bug reports:
> >
> > 1. Does your instance of Sakai generate bug reports?
> >
> > 2. How does your institution deal with bug reports generated from Sakai?
> >
> > 3. Does someone at your institution read/monitor the bug report email?
> >
> > 4. Do you follow up with your users who leave comments?
> >
> > 5. Do you follow up with your users who don't leave comments but who
> > cause a bug report?
> >
> > Thanks for your opinions and anecdotes,
> > -Shawn
> >
> > --
> > Shawn Foster
> > eLearning Technology Support and Application Development
> > Information Technology Services
> > Western University
> > London, Ontario, Canada
> > _______________________________________________
> > production mailing list
> > production at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/production
> >
> > TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20150130/e2e2703d/attachment.html