Has anyone experience macro behavior where some macros stop working while other continue to function as they are suppose to? And not on all pages. For example, in recent days, the TOC macro has stopped working on a number of pages, but not all. Then is will start working again, only to stop the next day. See the screen shot below. I'm using Confluence version 5.8.13
Any help would be appreciated.
Thanks, Sandy
image2016-11-15 18:52:5.png
Julia - thanks I'll have my support team give this a try
Rob - We are an IE only shop. However, I did discover that I I edit and save the page the problem would go away, but only for that page of course.
Hi Sandy,
If it helps, this is the supported browsers page. There are a number of IE and Edge notes that might be useful for you. More than a few answers on this forum include "try a browser that's not IE" and end up solving the problem. I've got absolutely no axe to grind with IE or Microsoft, but if there is any way you can move/allow your users to access Atlassian on Firefox, Safari or Chrome then in general you and they will have a better experience.
But if you can't, this forum is always available
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, so the odd thing is that we've been on this version of Confluence for almost a year and on IE 11 longer than that and this problem only started occurring within the last 2-3 weeks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Sandy,
we have often the issue connected to Java. So we have to restart and delete the plugin-cache to fix it.
https://confluence.atlassian.com/confkb/how-to-clear-confluence-plugins-cache-297664846.html
I hope that will solve your problem.
Regards,
Julia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've experienced something similar and equally intermittent and random. All I can tell you is that we discovered that it only happened on Firefox and not on Chrome, so our workaround was for Firefox users to switch to Chrome if they were having problems on a particular page.
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.