Known Issues

The following issues are known to exist in this release.

Some versions of Perl corrupt binary file downloads with SOAP::Lite

Some older versions of Perl contain a bug that causes some binary files downloaded through SOAP::Lite to become corrupted. The version of Perl that ships with RedHat Enterprise Server 3 is known to contain this bug. The version that ships with RedHat Enterprise Server 4 does not, nor does the latest version compiled from source.

SourceForge Explorer does not show offline in Microsoft Windows 2000

When running Microsoft Windows 2000, if you log into SourceForge Explorer, then disconnect your network connection, SourceForge Explorer does not indicate that you are working offline. The Create New Object and Open In SourceForge buttons remain enabled in the toolbar; however, you will receive an error message if you attempt to use them.

Error viewing deleted Subversion files

If you delete a file in a Subversion repository, you will still be able to view previous versions of the file on the SourceForge View Commits page. However, if you click the file name, you will receive an error.

If you create a new file with the same name as the deleted file, all references in the revision history of the deleted file will point incorrectly to the new file. You will also see this behavior if you move a file, then create a new file with the same name in the original file's location.

ASCII control characters stripped when accessed via the SOAP API

Data containing ASCII control characters will have these characters stripped and replaced with spaces when accessed via SOAP. Any modifications made via SOAP to objects containing this data will save this character-to-space replacement back to SourceForge.

Only frame-enabled applications can be linked

You can create linked applications only with web-based applications or websites that can run in a frame. An application that is not frame-enabled can still be linked; however, when launched, it will take over your entire web browser window and remove the SourceForge navigation.

Must re-launch SourceForge Explorer to see new tracker fields

If you are running SourceForge Explorer, and use the SourceForge web interface to add or configure Tracker fields, you must close and re-launch SourceForge Explorer to see the new or updated fields.

Browser error when uploading >2GB files

SourceForge has a 2GB file size limit on uploads or attachments. If you attempt to upload a >2GB file using a Windows-based browser, you will not be able to upload the file, but you may not receive an error message.

Microsoft Office XP users must update to SP3 to view PowerPoint files

If you are running Microsoft Office XP, you may encounter an error when trying to open a PowerPoint file directly from SourceForge. To resolve this error, install the Microsoft Office XP Service Pack 3 update. You can also save the PowerPoint file locally, then open it directly in PowerPoint without error.

Cannot view CVS browser when connecting directly to JBoss

If your SourceForge installation connects directly to JBoss (e.g. if you are not using Apache,) and you are running both CVS and SourceForge on the same server, you will not be able to view the SourceForge CVS browser in some versions of Internet Explorer. This is a known Microsoft issue with Internet Explorer 6.0. For additional information on this issue, see the following Microsoft Knowledge Base article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;843518

To resolve this issue, you must use Apache as a frontend to JBoss. Do not use http://<servername>:8080/sf to access SourceForge. Use http://<servername>/sf without the port.

PowerPoint files do not save automatically in SourceForge

If you are using the SourceForge Document Manager Add-in for Microsoft Office, and use the Open in SourceForge function from within Microsoft PowerPoint, then click Save, the document will be saved to your temp directory, not back to SourceForge. You must use the Save to SourceForge function to update the document in SourceForge.

Must edit document after canceling Save to SourceForge

If you are using the SourceForge Document Manager Add-in for Microsoft Office, and use the Save to SourceForge function, but cancel the operation before saving, you must make at least one edit to the document before you can use the Save to SourceForge function again.

Must select document to update in SourceForge

If you are using the SourceForge Document Manager Add-in for Microsoft Office, and use the Save to SourceForge function to update a document that already exists in SourceForge, you are prompted to browse to the document folder containing the document that you want to update. You must then select the document that you want to update. If you do select the folder only, without selecting the document, SourceForge will create a duplicate copy of the document.

Internet Explorer does not recognize file type when document is open

If you are using Internet Explorer, and attempt to upload a Microsoft Office document while the document is still open, SourceForge will not recognize the document file type. To resolve this issue, close the document, then upload it to SourceForge again.

White screen displays when opening PDF files in IE 6.0

When using Internet Explorer 6.0, you may encounter a blank screen when attempting to open a PDF file stored in the Document Manager. If this happens, right-click the document name, then choose Save Link Target As. You will be able to open the file from your file browser.

Erroneous notification message when a SourceForge Administrator changes a user's email address

When a SourceForge administrator changes a user's email address, a confirmation message is generated stating that an email notification will be sent to confirm the address change. Email is currently sent to the original email address.