How many times have we seen people confused by weird behaviour in Koha, which was caused by them not having entered a "catch all" basic circulation rule? If we had a very simple sample rule that would catch the combination of all patron categories and all item types, it might save some confusion. This should be a part of the optional sample data that users can choose to install as part of the web installer.
*** Bug 9527 has been marked as a duplicate of this bug. ***
Why sample data? Why not a default behavior if no rules are present? Either reject transactions until all the pieces are in place, or have a hard set rule in place in case basic rules or a "catch all" is defined by admin.
(In reply to Christopher Brannon from comment #2) > Why sample data? Why not a default behavior if no rules are present? > Either reject transactions until all the pieces are in place, or have a hard > set rule in place in case basic rules or a "catch all" is defined by admin. Doing it via sample data (or mandatory data for that sake) was seen as a quick fix. No objections to making a proper fix for it!
*** This bug has been marked as a duplicate of bug 15757 ***
Magnus, it's not a duplicate, bug 15757 won't create a default rule.
I think this has been solved by the onboarding tool that forces you to add a circulation rule at time of installation.