| 2022-04-21 00:29:18 |
Dianne Tennent |
description |
This happens in both MySQL and Postgres
To replicate:
1. Create an institution template collection (set to 'Current auto-copied template') with portfolio completion.
2. Create a new account and run the cron so that the portfolio is created in the new member's account.
3. As admin, try to delete the institution template collection.
Result
- SQL error messages on screen
Expected:
- Perhaps there should be a warning to institution admins that the collection has been auto-copied before deleting it. |
This happens in both MySQL and Postgres
To replicate:
1. Create an institution template collection (set to 'Current auto-copied template') with portfolio completion.
2. Create a new account and run the cron so that the portfolio is created in the new member's account.
3. As admin, try to delete the institution template collection.
Result
- SQL error messages on screen. There is a foreign key constraint with collection_template.originaltemplate = collection.id, so it won't allow you to delete from collection table until collection_template table entries are cleared.
Expected:
- Perhaps there should be a warning to institution admins that the collection has been auto-copied before deleting it.
- I think we need to delete from the collection_template table where originaltemplate = $this->id, rather than where collection = $this->id (htdocs/lib/collection.php:324). Then we'll be able to delete from collection table. |
|
| 2022-04-21 00:31:01 |
Dianne Tennent |
description |
This happens in both MySQL and Postgres
To replicate:
1. Create an institution template collection (set to 'Current auto-copied template') with portfolio completion.
2. Create a new account and run the cron so that the portfolio is created in the new member's account.
3. As admin, try to delete the institution template collection.
Result
- SQL error messages on screen. There is a foreign key constraint with collection_template.originaltemplate = collection.id, so it won't allow you to delete from collection table until collection_template table entries are cleared.
Expected:
- Perhaps there should be a warning to institution admins that the collection has been auto-copied before deleting it.
- I think we need to delete from the collection_template table where originaltemplate = $this->id, rather than where collection = $this->id (htdocs/lib/collection.php:324). Then we'll be able to delete from collection table. |
This happens in both MySQL and Postgres
To replicate:
1. Create an institution template collection (set to 'Current auto-copied template') with portfolio completion.
2. Create a new account and run the cron so that the portfolio is created in the new member's account.
3. As admin, try to delete the institution template collection.
Result
- SQL error messages on screen. There is a foreign key constraint with collection_template.originaltemplate = collection.id, so it won't allow you to delete from collection table until collection_template table entries are cleared.
Expected:
- Perhaps there should be a warning to institution admins that the collection has been auto-copied before deleting it.
- I think we need to delete from the collection_template table where originaltemplate = $this->id, rather than where collection = $this->id (htdocs/lib/collection.php:324). Then we'll be able to delete from collection table.
Kristina mentioned that a Behat test for this would be good, since we don't regularly come across this scenario. |
|
