Bug 17410 - Export default Framework gives always empty file
Summary: Export default Framework gives always empty file
Status: RESOLVED DUPLICATE of bug 17389
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 16.05
Hardware: All All
: P5 - low normal (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-06 09:59 UTC by Hugo Agud
Modified: 2017-02-19 00:14 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hugo Agud 2016-10-06 09:59:39 UTC
In koha 16.05.04 when tries to export the default framework, generates an emtpy file even choosing any format.

In plack-error.log 

Use of uninitialized value $mode in string eq at /usr/share/koha/lib/C4/ImportExportFramework.pm line 212.
Use of uninitialized value $mode in string eq at /usr/share/koha/lib/C4/ImportExportFramework.pm line 212.
Use of uninitialized value $mode in string eq at /usr/share/koha/lib/C4/ImportExportFramework.pm line 232.
Use of uninitialized value $mode in string eq at /usr/share/koha/lib/C4/ImportExportFramework.pm line 232.
Use of uninitialized value $mode in string eq at /usr/share/koha/lib/C4/ImportExportFramework.pm line 249.
Use of uninitialized value $mode in string eq at /usr/share/koha/lib/C4/ImportExportFramework.pm line 251.
Use of uninitialized value $format in string eq at /usr/share/koha/intranet/cgi-bin/admin/import_export_framework.pl line 58.
Use of uninitialized value $format in string eq at /usr/share/koha/intranet/cgi-bin/admin/import_export_framework.pl line 65.

There is no problem when exporting any other framework

TEsted in Koha 16.05.04 on Debian 8 with plack enabled
Comment 1 Mark Tompsett 2017-02-19 00:14:38 UTC
I believe this was solved in 16.05.05 in bug 16035. If not, bug 17389.

*** This bug has been marked as a duplicate of bug 17389 ***