EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #03436
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Issues following database change (possibly...)
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: Issues following database change (possibly...)
- From: Lizz Jennings <e.jennings@bath.ac.uk>
- Date: Wed, 03 Sep 2014 15:05:12 +0100
If you're iterating over something, is it picking up the iteration number as the field name?
Lizz On 03/09/2014 14:19, Andrew Beeken wrote:
This seems to be the most prevalent error, but it¹s not clear to me where the issue lies: [Wed Sep 03 14:06:12 2014] [error] :Apache2 IO write: (103) Software caused connection abort at /usr/share/eprints3/cgi/export line 199 [Wed Sep 03 14:06:14 2014] [error] [client 10.82.3.45] Can't use string ("") as an ARRAY ref while "strict refs" in use at /usr/share/eprints3/perl_lib/EPrints/MetaField/Authorid.pm line 37.\n Use of uninitialized value in string ne at (eval 105) line 31. dataset eprint has no field: 1 ------------------------------------------------------------------ ---------------- EPrints System Error ---------------------------- ------------------------------------------------------------------ Attempt to get value from not existent field: eprint/1 ------------------------------------------------------------------ at /usr/share/eprints3/perl_lib/EPrints/DataObj.pm line 702.EPrints::DataObj::get_value(EPrints::DataObj::EPrint=HASH(0x7f4f7c62d5b0),1) called at (eval 69) line 99EPrints::Config::lirolem::__ANON__(EPrints::DataObj::EPrint=HASH(0x7f4f7c62d5b0), EPrints::Repository=HASH(0x7f4f78323da0), undef) called at /usr/share/eprints3/perl_lib/EPrints/Repository.pm line 1656 eval {...} called at /usr/share/eprints3/perl_lib/EPrints/Repository.pm line 1656 EPrints::Repository::call(EPrints::Repository=HASH(0x7f4f78323da0), "eprint_render", EPrints::DataObj::EPrint=HASH(0x7f4f7c62d5b0), EPrints::Repository=HASH(0x7f4f78323da0), undef) called at /usr/share/eprints3/perl_lib/EPrints/DataObj/EPrint.pm line 1537EPrints::DataObj::EPrint::render(EPrints::DataObj::EPrint=HASH(0x7f4f7c62d5b0)) called at /usr/share/eprints3/perl_lib/EPrints/DataObj/EPrint.pm line 1406EPrints::DataObj::EPrint::generate_static(EPrints::DataObj::EPrint=HASH(0x7f4f7c62d5b0)) called at /usr/share/eprints3/perl_lib/EPrints/Update/Abstract.pm line 66EPrints::Update::Abstract::update(EPrints::Repository=HASH(0x7f4f78323da0),"en", 5494, "/archive/00/00/54/94") called at /usr/share/eprints3/perl_lib/EPrints/Apache/Rewrite.pm line 471EPrints::Apache::Rewrite::handler(Apache2::RequestRec=SCALAR(0x7f4f7c5fd2c8)) called at -e line 0 eval {...} called at -e line 0 On 03/09/2014 12:27, "John Salter" <J.Salter@leeds.ac.uk> wrote:First stop: Apache Error log. This should tell you what it's complaining about. If the error message contained within is incomprehensible, the gathered wisdom of the list should be able to help... Cheers, John -----Original Message----- From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andrew Beeken Sent: 03 September 2014 12:14 To: eprints-tech@ecs.soton.ac.uk Subject: [EP-tech] Issues following database change (possibly...) Okay, so I¹ve just gone through the process of adding a new field to our ePrints Details page. The process went fine, the field is up and all logic associated with it is working. However, the Browse Authors view is now returning an internal server error: http://eprints.lincoln.ac.uk/view/creators/. I¹m not sure if this is a result of the new field or if the issue was there before we went through this process and we¹ve simply not noticed yet. The page is working fine in our development environment. Any thoughts or assistance offered would be greatly appreciated! Andrew The University of Lincoln, located in the heart of the city of Lincoln, has established an international reputation based on high student satisfaction, excellent graduate employment and world-class research. The information in this e-mail and any attachments may be confidential. If you have received this email in error please notify the sender immediately and remove it from your system. Do not disclose the contents to another person or take copies. Email is not secure and may contain viruses. The University of Lincoln makes every effort to ensure email is sent without viruses, but cannot guarantee this and recommends recipients take appropriate precautions. The University may monitor email traffic data and content in accordance with its policies and English law. Further information can be found at: http://www.lincoln.ac.uk/legal. *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/ *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/
-- Lizz Jennings BA MSc ACLIP MCLIP (Revalidated 2014) Technical Data Officer The Library 4.10, University of Bath, Bath, BA2 7AY UK Ext. 3570 (External 01225 383570) E.Jennings@bath.ac.uk
- References:
- [EP-tech] Re: Issues following database change (possibly...)
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- [EP-tech] Re: Issues following database change (possibly...)
- Prev by Date: [EP-tech] Re: Issues following database change (possibly...)
- Next by Date: [EP-tech] Re: Issues following database change (possibly...)
- Previous by thread: [EP-tech] Re: Issues following database change (possibly...)
- Next by thread: [EP-tech] Re: Issues following database change (possibly...)
- Index(es):