DTD1941

We are testing blesta. We created some clients and a package . We added the package as a service for one of the clients. We then wanted to delete a client and all the services and the package associated with the deleted client. We then the following for the client to be deleted: (1) voided hist invoices; (2) canceled all services for that client; (3) delete the client. At this point we want to remove the package that is no longer connected to a client. This gives the error "The package could not be deleted because a service is currently using it." This error happens because the `services` table links to the `client` table and the `packages` table. You can delete the package if the client's records are removed from the `package` table. I also removed that client from `service_invoices`. This is okay in the test because all invoices were voided. So the question is can a package that has been assigned to a user ever be delete? It appears that the answer to this question is no. My "solution: allows orphan packages to be removed. In what we were doing, i.e. testing, the need to be able to do this clear. We are learing blesta and di not want all the 'crud' we entered as test data to remain. Also the interface and documentation suggest a package can be deleted. If the case of real removing orphan packages has value in avoiding confusion and data entry mistakes.As long as the package table are no used in view or printing an invoice it would seem that moving the records is okay. In our test it did not break anything. We do need to test this with an orphan package associated with a client with some non-voided invoices. A lots to words to support there seems to be a bug in the deletion of a package.