The following issues are known to exist in this release.
- JSP exception viewing reports
- When creating a report with a filter on the "fixed in release" field, you get a
JSP exception. (fixed in upcoming hotfix - artf25849)
- emailing multiple forums on same email leads to "ghost" postings
- Messages sent to multiple forums were incrementing the count of messages for
all forums, but the message itself would only appear in one of them. (fixed in
upcoming hotfix - artf25857)
- Encoded filename when exporting tracker with Japanese name in Japanese project
name
- The naming of tracker export files was changed in 4.4 to use the project name
and tracker name as part of the filename, causing issues if these names use
multibyte characters. (fixed in upcoming hotfix - artf25839)
- Page not found error in FRS
- In the File Release System, on the page listing the releases for a specific
package, checking the checkbox for a release and clicking the "Download
Selected" button would result in an error page. (fixed in upcoming hotfix -
artf25864).
- Special characters can't be displayed properly in saved tracker searches.
- If the name of a saved tracker search included certain characters such as square
brackets, less-than or greater-than signs, those characters would not appear
correctly in the pull-down list of saved searches. (fixed in upcoming hotfix -
artf25863)
- SourceForge Explorer does not show offline in Microsoft Windows 2000
- When running Microsoft Windows 2000, if you log into SourceForge Explorer, and
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.
- 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, and then open it directly in PowerPoint without error.
- 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, and
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 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, and then upload
it to SourceForge again.
- Potential exception when deleting subscriptions for an object
- The application could potentially error when a site admin deletes a user and
then within a very short interval of that, deletes a project that the deleted
user is a member of. If this happens, just wait for a few minutes and then
repeat the project delete operation.
- Search Indexes can be corrupted.
- If the SourceForge process which indexes objects for searching is killed or
encounters an error while an index file is in the process of being written out,
the search index can become corrupted. If this occurs, the search indexes will
need to be deleted and the search index will need to be regenerated; there is a
script supplied with SFEE for initiating a search reindex.
- Config files are overwritten
- The process of upgrading from older versions of SFEE may overwrite local
customizations to certain config files, such configurations for Jboss and James.
For instance, changes to the config.xml file for the James mail handler will be
lost if upgrading from a version older than SFEE 4.3 Hotfix 6. Before upgrading,
administrators should note any local customizations, back them up, and re-make
the changes after upgrading.
- UI gives impression that disabled users can be added to monitoring.
- For objects that can be monitored, SFEE now allows users to see who is
monitoring the object, and add other users to the set of users monitoring. The
user picker which is used to add users will appear to allow one to select
disabled users to add to monitoring, but they are not actually added to
monitoring.
- Fields are draggable beyond screen limits, creating infinite scrollbar.
- In the new drag-and-drop interface for tracker field administration introduced
in 4.4, if fields are grabbed and dragged beyond the window limits to the right
or far down, this will cause the window to become infinitely bigger, on both
FireFox 2 and Internet Explorer 7. (artf25272)