I have…
- [ x ] Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
- [ x ] Used code blocks with ``` to format my code examples like JSON or logs properly.
I’m submitting a…
- Regression (a behavior that stopped working in a new release)
- [ x ] Bug report
- Performance issue
- Documentation issue or request
Current behavior
I don’t know if you can reproduce this.
Someone managed to create a component and a schema with the same name. Usually, Squidex prohibits this. The schema was created 3 years ago.
Now the component is not available in the UI. Therefore, I don’t know when the component was created. But it has been actively used for probably more than 1 year.
The UI displays the Label of both the component and the schema, but when switching to the component, the user is directed only to the schema.
I update the CMS on average once a year. Perhaps the component and the schema were created in different versions.
Can you tell me how to fix this without deleting the component?
I think for deleting the diagram, but if the component is deleted and not the schema, then we will lose its schemaId.
Even if you then create a new one with the same name, for the UI it will be a new component since its schemaId will already be different.
For now I’m wary of deleting the schema, since the schema name is sent to the request, not the schemaId.
Expected behavior
fixing. Schema must have another name and current component must be saved.
Minimal reproduction of the problem
“unknown magic”
Environment
App Name:
- [ x ] Self hosted with docker
- Self hosted with IIS
- Self hosted with other version
- Cloud version
Version: 7.8.1
Browser:
- [ x ] Chrome (desktop)
- Chrome (Android)
- Chrome (iOS)
- Firefox
- Safari (desktop)
- Safari (iOS)
- IE
- Edge
Others:
I have json schema of both.