Important notice- Update Re:Private Documents on this site

UPDATE 6/24/2014 – Not as bad as we thought.

The good news is that this should mean that under normal conditions the private content on the site should stay private.

This issue has only been replicated on  on machines where the user has previously logged into the site using their username and password. It seems that even after you log out the site your machine may “remember” you.

We have had help from the FireFox folks to help evaluate and understand the problem outlined below. It seems that the issue is being caused by persistent cookies.


 

The Problem –This post is to make you aware of a newly discovered “bug” in the intended functionality for this site. The intent and functionality when this site was launched was to allow some documents and postings to be limited to some groups.

It has been discovered that this functionality no longer works as expected with some newer versions of the FireFox browser. (It works as expected in IE, Chrome, and Safari)

Other than the noted problem regarding limiting document access, the site is working as it should.

How does this impact what is done on this site? – It means that all documents are potentially available to any user who chooses to view that posting or document.  Given the way this site has been used up to now that should not be a major issue.

Existing Documents – If you have any documents which you wish to remove as a result of this change in functionality please let us know by putting in a help request with details of what you would like removed.

What we have done – We have done a number of troubleshooting tests to test the issue and rule out issues specific to this site which might be causing it.  The change in the look is one of these tests. We have returned the site to standard look (theme) that is provided by WordPress to rule out a theme specific problem and disabled all unneeded features to test if one of those was the problem.

Where we stand – We have put in bug reports and await any resolution from WordPress or FireFox to resolve this problem.  Sorry for the inconvenience,