Orphan/dangling references to page layouts that can't be seen in the UI

mark · October 12, 2023, 4:19am

I’m unsure if this is a known issue, but when I delete unneeded pages or modules, it leaves behind orphan/dangling references to page layouts that can’t be seen in the UI. This becomes an issue when we update/ provision a new environment via Terraform, as we need to manually delete errors one by one during deployments. We have a workaround but it is a bit messy.

I’m looking for suggestions on how we identify or prevent orphan/dangling references in the first place?

ege345dc4g5c45gc · October 16, 2023, 1:40pm

I believe I have a related issue, I can’t export namespaces because of some orphaned modules/fields/pages that were deleted in the meantime.
It’s mentioned here:

I also created Github issue:

github.com/cortezaproject/corteza

Error trying to export namespace: module does not exist

opened 04:49PM - 06 Sep 23 UTC

martkaczmarek

bug backend

### Is there an existing issue for this? - [X] I have searched the existing iss…ues ### Version of Corteza 2023.3.5 ### Current Behavior When trying to export a namespace (Manage namespaces -> Pick from list -> Export namespace), I'm encountering the following response: ``` { "error":{ "message":"invalid module reference {corteza::compose:module {[347533651178741763] map[347533651178741763:true]} {corteza::compose:namespace {[344241087105269762] map[344241087105269762:true]}} false}: module does not exist" } } ``` 344241087105269762 is a valid namespace ID - it's the built-in CRM namespace that I modified over time. No module exists with the id of 347533651178741763, at least not now. I guess it was created and then deleted. However, when I go into modules list in this namespace and hit "Export", the modules list exports without problem. Module with ID 347533651178741763 was not in that list. ### Expected Behavior Export tool should ignore non-existing modules during export or have some sort of clean-up after deleting module. ### Steps To Reproduce _No response_ ### Environment and versions _No response_ ### Anything else? When I created a blank test namespace with two modules and deleted one of them, the export succeeded, so that wasn't the case here. There's something wrong with this one particular namespace.

It seems it’s set to be fixed in release 2023.9.1, whenever it might be: