urgent: data is gone after upgrade to 7.0.7 from 7.0.4

[junlilenovo]

we just migrated from confluence 7.19.2 to 8.5.2. we found the e-signature 7.0.4 does not work. we upgraded it to 7.0.7 and able to create new signatures on new page, but old page showed errors. then we followed the instruction to clear cache and reboot every node, and now all pages with signatures don't have errors any more, but we noticed some signatures on some pages are gone, but not all gone either. how do we pull old data back?

[junlilenovo]

actually I just found out in our dev env where e-signature is 7.0.4 and confluence is 8.5.1, the signatures and timestamps are all gone. that means confluence upgrade made signature data disappear. is there a way to get data back?

[CodeParanoia]

actually I just found out in our dev env where e-signature is 7.0.4 and confluence is 8.5.1, the signatures and timestamps are all gone. that means confluence upgrade made signature data disappear. is there a way to get data back?

Hi @junlilenovo could you solve this somehow? I have the same issue... very uncomfprtable to explain everyone their "signed documents" are gone.
thanks.

[jayrod0112]

May we have an update with this issue? Is there anyway to restore the missing signatures? Thanks.

[jayrod0112]

May we have an update with this issue? The plugin's 7.0.4 version should be compatible to "Confluence Server 6.13.7 - 8.6.1".
However, when we upgraded from Confluence 7.19.6 to v8.4.0, we lost the existing signatures and can no longer provide new signatures.

Plugin version 7.0.7 enabled us to provide new signatures, however, the existing signatures prior to the upgrade are still lost.

[jayrod0112]

@Tiliavir any updates would be much appreciated.
Thanks!

[jayrod0112]

Please refer to issue #106 for updates

[jayrod0112]

@Tiliavir .. Atlassian support has this to say after studying the contents of our BANDANA tables. Please advise if the data can still be retrieved.

... The suspicion here is that with the updated version of the app, it will migrate its BANDANA signature data from XML to JSON, and somewhere during the data migration process, the "signature" values aren't being correctly converted into expected JSON format, and are therefore dropped entirely.