Bug 5073 - Entering an order with the 'koha item type' field blank causes a 500 error
Summary: Entering an order with the 'koha item type' field blank causes a 500 error
Status: CLOSED DUPLICATE of bug 4955
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Robin Sheat
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-29 05:07 UTC by Robin Sheat
Modified: 2012-10-26 00:41 UTC (History)
2 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 Robin Sheat 2010-07-29 05:07:53 UTC
The 'koha item type' is compulsory, but doesn't look it. It should be in red, and default to the top one on the list so that it's impossible to make an error that results in a mysterious message.
Comment 1 Robin Sheat 2010-07-29 05:27:39 UTC
This occurs when you don't have an acquisitions framework set up that makes koha item type mandatory.
Comment 2 Katrin Fischer 2010-07-29 05:36:17 UTC
I am not sure changing the order is a good idea. The order is defined by the framework the same way at different places in Koha (cataloging, subscriptions with items in serials).

There is also a bug report requesting a default ACQ framework. (bug 3841)

This bug is duplicate or at least related closely to bug 4955.

Marking some fields as mandatory in frameworks was a bit problematic in my last tests. Bug 3727 describes what I saw, but this was some time ago and needs to be retested perhaps.
Comment 3 Nicole C. Engard 2010-07-29 13:45:50 UTC
If the there is no default ACQ framework then most users will not know that this is why they're seeing this problem.  It's a bug in my book because there are no clues to the user as to why they have this error poppping up.

And it is a duplicate, marking it as such.

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