I don’t think this problem/solution is much different in older versions.
Problem: when you send a link from Communicator client to another, the link isn’t clickable, has a _ (underbar) in front of it, or both. Results may be different on different computers. It’ll look like this
_http://www.google.com
Solution: Two things are happening here that are not related. The first is the OCS Server (and Edge Server) have the URL Filter enabled, which are adding the _ underbar to all links. Also called “Intelligent IM Filter”. You need to tone that filter down or disable all together to your liking. If users are coming in through an Edge Server, they will follow the Filter settings of the Edge Server they are using, which seams to supersede the Front End Server (my guess is the most restrictive wins). So be sure to set it on both servers separately. Results were instant in new IM’s.
The other issue is the lack of a clickable hyperlink. If you disable the URL Filters above, the underbar goes away but links are still not blue and underlined. To fix this you need to apply a GPO or set a local registry setting to allow Communicator to make hyperlinks clickable:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator\
new DWORD EnableURL=1
After that exit and restart Communicator.
In both of these cases they are secure by default, which is great; but even years after this features release over several versions their use and configuration are still a mystery to most starting out.
I see a lot of people saying they are getting auth prompts for public anonymous content on SharePoint sites. Once you have anonymous enabled in Central Admin and in the site collection, you’d expect it to be all good right?
I discovered one more resaon beyond the obvious permissions problems. If you put a graphic or something embded in a page, then publish that page but NOT the embeded object (i.e. it’s still draft or unapproved) you’ll get an auth prompt when the page loads.
On a busy (lots of stuff) page it can be tough to find what’s the issue. The quickest way I’ve found to discover the problem (99% of time an image) is to cancel out of auth prompts, then look for broken stuff on the page. An image you can right click the broken icon and find the location of it… then jump to that library and check the file. My bet is it’s never been published.
Just upgraded from Wordpress 2.2.x to 2.3.1 and found a few plugin issues.
- Needed to upgrade Google XML Sitemaps. I just deactivated the old and uploaded/activated the new.
- The new plugin upgrade feature in WordPress told me to upgrade my WordPress Database Backup, which wasn’t activated, so I just overwrote the file.
- My K2 theme is so advanced it had it’s own Widget manager before WordPress did. Once WP added the feature, you needed a K2 plugin to disable the WP widget manager (because K2’s is still better). Now, the K2 theme disables the WP one on it’s own without the Plugin. So, I’m removing this plugin and updating my K2 next.