Step to reproduce : - export default framework as SQL - create new framework - Import the exported SQL file into this new framework. Go to default framework : It disappeared. If some libraries want to share default frameworks, then it is a major bug.
Created attachment 6790 [details] [review] patch proposed
Created attachment 6792 [details] [review] [SIGNED-OFF] Bug 7360 Import Default framework into other deletes default Framework Step to reproduce : - export default framework as SQL - create new framework - Import the exported SQL file into this new framework. Go to default framework : It disappeared. If some libraries want to share default frameworks, then it is a major bug. This patch fixes the test in order to cope with 0 character framework name. Signed-off-by: François Charbonnier <francois.charbonnier@biblibre.com>
tests I did : 1/ I created as many test frameworks as we have framework export choices 2/ I imported each export file within a specific test framework 3/ Each time, I checked that the default framework was still here It works!
updating severity & assigning. I won't QA it, because it's author=BibLibre & signoff=BibLibre, but pls QA quickly, it's a critical problem for anyone who export/import the default framework !
Just adds support for 0 character frameworks (down from minimum 1). Marking Passed QA
Patch pushed, please test