Blesta Addons Posted January 25, 2015 Report Posted January 25, 2015 this is not a big probleme , but is easy to fix . when a package is assigned to a group , and in editing mode, we want to leave the group Membership empty , , after the save we package reassign the last group assigned to it . so we are forced to create a unused group to assign it to it . simply , try to save a package with a empty group Membership field . PauloV 1
serge Posted January 25, 2015 Report Posted January 25, 2015 you mean the bug you report: is to be allowed to save a package without having a group assigned to this package?
Blesta Addons Posted January 25, 2015 Author Report Posted January 25, 2015 this bug is just in updating package , and saving the first time .
serge Posted January 25, 2015 Report Posted January 25, 2015 what I found is when editing package, and removing all Assigned Groups and save package. if we re edit after the package, previous assignated group(s) are still there and are also as still there as well in db table package_group for the given package. Blesta Addons 1
Blesta Addons Posted January 25, 2015 Author Report Posted January 25, 2015 what I found is when editing package, and removing all Assigned Groups and save package. if we re edit after the package, previous assignated group(s) are still there and are also as still there as well in db table package_group for the given package. so is a confirmed bug
Paul Posted January 26, 2015 Report Posted January 26, 2015 Just to be clear, you are saying: 1. When creating a package, you must assign or create a new package group for it. and 2. When editing a package, you can save it with no package group assigned? Packages cannot be ordered if they are not part of a group, but you may wish to have packages that don't belong to groups or to temporarily unassign them.
Blesta Addons Posted January 26, 2015 Author Report Posted January 26, 2015 Hello paul , we can't make package to don't belong to groups or to temporarily unassign them in editing mode .
Tyson Posted January 26, 2015 Report Posted January 26, 2015 Thanks, this has been fixed for v3.4.1 in CORE-1565.
Recommended Posts