Bug 30371 - The vendor does not exist at serials/subscription-add.pl
Summary: The vendor does not exist at serials/subscription-add.pl
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Serials (show other bugs)
Version: 20.11
Hardware: All Linux
: P5 - low major
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-27 09:44 UTC by Developer Inside
Modified: 2022-12-12 21:23 UTC (History)
0 users

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


Attachments
subscription-add.pl (108.87 KB, image/png)
2022-03-27 09:44 UTC, Developer Inside
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Developer Inside 2022-03-27 09:44:39 UTC
Created attachment 132272 [details]
subscription-add.pl

Home › Serials › New subscription

I have upgraded koha version 19.11 to 20.11.06.
Server : Ubuntu 16.04.4 LTS

Unable to add new subscription in koha.

vendor is available in koha,
I am able to search for a vendor on the subscription edit form at
serials/subscription-add.pl, but when i select vendor and biblio and
click on next button it shows " The vendor does not exist " alert.


I have installed Koha versions 18.05.00, 19.11.00,  20.11.06
But for Koha version 20.11.06  this problem appears.

aslo I have installed all the dependencies listed by the following command

root@server:~/koha-20.11.06# ./koha_perl_deps.pl -m -u
Total modules reported: 0 

I have tried all sorts of ways to identify the problem.

1) Tried to clear browser cache,

2) Tail log file (all present in ../log/koha/*.log and apache2/error): There is nothing in the log file.

3) The browser console is clean, no errors appear.

***We have installed koha through the command line standard installation process by downloading the tar.gz file, so we cannot use the koha command. ie. Koha-common or koha-perldeps. 


Is there anything else I might want to examine that could be causing the
problem?
Comment 1 Katrin Fischer 2022-03-27 10:04:31 UTC
We have several 20.11 installations that don't show this issue, so I believe this is more a problem of setup/installation and possibly the API not working because of dependency issues. 

As we use bugzilla only for bugs/enhancement requests, it's better to leave your question on the mailing list where more people will read it and can help you.

Have you tried Mason's last suggestion? Please reply on list.