Bug 15493: Use the correct CSV profile when exporting records from the export tool
The CSV profile used is not the one the user has chosen, but the one
defined in the pref ExportWithCsvProfile.
It's caused by a wrong variable name csv_profile vs csv_profile_id
Test plan:
Define 1+ csv profiles
Set ExportWithCsvProfile with 1 of these profile
Use the export tool to export some records using a csv profile.
Without this patch, the csv profile used, will always be the one defined
in ExportWithCsvProfile.
Signed-off-by: Hector Castro <hector.hecaxmmx@gmail.com>
Works as descrived
Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Signed-off-by: Brendan A Gallagher <brendan@bywatersolutions.com>
(cherry picked from commit 47e6df5fe4)
Signed-off-by: Julian Maurice <julian.maurice@biblibre.com>
This commit is contained in:
parent
1b5f4b8b9b
commit
0bbefeba82
|
|
@ -139,7 +139,7 @@ $(document).ready(function() {
|
|||
</li>
|
||||
<li class="csv_profiles">
|
||||
<label for="bibs_csv_profile">CSV profile: </label>
|
||||
<select id="bibs_csv_profile" name="csv_profile">
|
||||
<select id="bibs_csv_profile" name="csv_profile_id">
|
||||
[% FOR csv_profile IN csv_profiles %]
|
||||
<option value="[% csv_profile.export_format_id %]">[% csv_profile.profile %]</option>
|
||||
[% END %]
|
||||
|
|
|
|||
Loading…
Reference in New Issue