| - |
A customer migrated from the default Derby DB to an SQL DB and they could no longer create components, as they received an error in the template box. They also could not access the security tab of some of their templates. The resource ID of the offending templates was not present in the new DB's sec_resources table. This was remedied by copying a good template row and replacing the ID with the missing one.
|
+ |
In some instances of DB migration, the resource ID of some component templates is not migrated to the new DB's sec_resources table. This can be remedied by copying a good component template's row and replacing the ID with the missing component template's resource ID.
|
| |
|
+ |
Symptoms include the inability to create components, as an "error!!!" message is displayed in the template box. Also the security tab of some of the component template with the missing ID cannot me accessed.
|
