Hey everyone,
after an upgrade to Confluence 4.2.1 we encountered the following error showing on top of every page (even on the login page). Seems to be related to the quick comments plugin. Quick comments are not working and if I disable the plugin the message disappears. Any ideas on how I could fix this? We are using refined Wiki if that makes any difference which I doubt...
Thanks in advance,
Christian
Hi Christian,
Please try the following workaround
<entry>
<string>confluence.web.panel.renderers</string>
<boolean>false</boolean>
</entry>
Delete the above lines from your notepad and saved it
Execute the following SQL query
UPDATE BANDANA set BANDANAVALUE = '<Put the entire strings from your notepad here>' WHERE BANDANAKEY = 'plugin.manager.state.Map';
Restart Confluence
Hope it helps.
Cheers,
Septa Cahyadiputra
Hey Septa,
thank you very much. Eyerything works fine...
Cheers Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My pleasure :).
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately the aforementioned query does not work with 5.1.7. :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This fixed the problem for me too. Thanks!
Not sure what caused the issue, would be good if this could be fed back to the development team for them to resolve as I suspect it was caused during recent updates to both Confluence (5.1.2) and JIRA (6.0)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
We have a kind of this error in the WebPanel in Jira (above the banner).
Any help/advice?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This fixed the problem for me too. Thanks!
Not sure what caused the issue, would be good if this could be fed back to the development team for them to resolve as I suspect it was caused during recent updates to both Confluence (5.1.2) and JIRA (6.0)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.