EPrints Technical Mailing List Archive

Message: #03905

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[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