-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
class com.baloise.confluence.digitalsignature.Signature cannot be cast to class #70
Comments
Please refer to this Issue: #68. Best regars |
worked like charm, thank you! |
Hi,
The version of digital-signature is 7.0.3 I would like to try invalidating the plugin cache. My question is, can I do it only for the digital-signature plugin? Or can I invalidate the cache only for all our Confluence plugins using this method? Thank you. Marek |
Plugin cache of digital-signature should be sufficient. Best regards |
Hi @Tiliavir , Marek |
sorry I was wrong with that - just had a look into the Readme and attached issue where it states
and more importantly this comment on the referenced issue #68 (comment):
Sorry for the confusion and inconvenience. Unfortunately we are not (yet) migrated to DC and therefore the urge to push compatibility for this plugin is not too big. Hope I can address this issue with #72 Best regards |
Hi @Tiliavir , We have the server license for Confluence, not the data center. Anyway, I stopped the Confluence service last night, cleared the cache for all plugins and then started the service. The digital-signature plugin then started working just fine. Thanks for the support. Have a nice day. |
I'm getting this error message when trying to render the signatures:
The plugin worked fine until today, we didn't do any updates (Confluence or plugin).
We are using the Version 7.0.3 of the plugin and version 7.10.2 for Atlassian Confluence.
The text was updated successfully, but these errors were encountered: