[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Re: Errors on generate_views after 3.3.12 to 3.3.13 upgrade



Run that ./epadmin upgrade repository_id


Mohd Izwan Bin Salim
Pustakawan | Unit Pembangunan Web | Bahagian Pengurusan Perpustakaan 
Digital (BPPD),
Perpustakaan Tun Abdul Razak, 
Universiti Teknologi MARA, 40450 Shah Alam, Selangor Darul Ehsan

Email: mohdizwan8733 at salam.uitm.edu.my / kizbye at gmail.com
Phone: 03 5544 3770 / 012 912 9094




From:   Lizz Jennings <E.Jennings at bath.ac.uk>
To:     "eprints-tech at ecs.soton.ac.uk" <eprints-tech at ecs.soton.ac.uk>, 
Date:   10/02/2015 08:23 PM
Subject:        [EP-tech] Re: Errors on generate_views after 3.3.12 to 
3.3.13 upgrade
Sent by:        eprints-tech-bounces at ecs.soton.ac.uk



You should just be able to click the Update Database button in the Admin 
screen for config tools.
 
Lizz
 
--
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 at bath.ac.uk
Research Data Management: http://www.bath.ac.uk/research/data
 
 
From: eprints-tech-bounces at ecs.soton.ac.uk [
mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Jacob Wenzel
Sent: 10 February 2015 12:06
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Errors on generate_views after 3.3.12 to 3.3.13 upgrade
 
Hi guys!

After upgrading my repository from 3.3.12 to 3.3.13, the generate_views 
gives me these errors in the console:
DBD::mysql::st execute failed: Unknown column 
'subject__ordervalues_en.sortvalue_sortvalue' in 'order clause' at 
/usr/share/eprints3/bin/../perl_lib/EPrints/Database.pm line 3211.
SQL ERROR (execute): SELECT `subject`.`subjectid` FROM `subject` LEFT JOIN 
`subject__ordervalues_en` ON 
`subject`.`subjectid`=`subject__ordervalues_en`.`subjectid` WHERE 1=1 
GROUP BY `subject`.`subjectid`, 
`subject__ordervalues_en`.`sortvalue_sortvalue`, 
`subject__ordervalues_en`.`name_name` ORDER BY 
`subject__ordervalues_en`.`sortvalue_sortvalue` ASC, 
`subject__ordervalues_en`.`name_name` ASC
SQL ERROR (execute): Unknown column 
'subject__ordervalues_en.sortvalue_sortvalue' in 'order clause'
DBD::mysql::st fetch failed: fetch() without execute() at 
/usr/share/eprints3/bin/../perl_lib/EPrints/Search/Condition.pm line 588.
Warning! No values were found for eprint.view.subjects [subjects] - 
configuration may be wrong
Warning! No values were found for eprint.view.divisions [divisions] - 
configuration may be wrong

I don't use subjects or divisions in my repository (I have one division 
and one subject), so the warnings in the end are expected and were there 
before the upgrade. But the errors above it are new. A have made no 
changes to Database.pm or Condition.pm.

All view pages generate correctly, so I am wondering if I should just 
ignore it. Any thought or help on this topic would be greatly appreciated.

Have a nice day everyone!

/Jacob*** 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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20150211/7d04239f/attachment.html