-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: Space - Export / Import
-
None
-
3
While trying to import space/s through script, if accidentally existing space is re-imported without knowledge, if we do not have access to the UI there is nowhere to tell why the import failed.
Below is the last line/hint being printed in the atlassian-confluence.log
2021-11-23 11:07:57,503 INFO [http-nio-8090-exec-9] [atlassian.confluence.upgrade.AbstractUpgradeManager] getOldestSpaceImportAllowed Compatibility of Space Import: 4517 Upgrade task "Migrate all Page Templates using a storage format round-trip conversion" prevents importing
At the same time in the UI I see an error which reads "A space with the key 'xyz' already exists. Please delete it before restoring a space with the same key." But for scenarios, where UI access is not available for some reasons, it becomes difficult, tried adding com.atlassian.hibernate.extras.XMLDatabinder & com.atlassian.confluence.importexport in DEBUG/TRACE but no signs of the error we saw in the UI.
Even went onto to check at the code level for the class that is responsible for printing this error in the UI, placed the below class in DEBUG/TRACE but nothing additional was printed on the application logs linking to the failure:
import com.atlassian.confluence.content.render.xhtml.migration.SiteMigrator