----------------------------------------------------------------------- ----------------------------------------------------------------------- Release notes: ----------------------------------------------------------------------- ----------------------------------------------------------------------- ----------------------------------------------------------------------- Version 2.7.9 3/1/2008 ----------------------------------------------------------------------- Bug fixes. A few of these fixes are the result of me running a public instance of BugTracker.NET hosted at GoDaddy, at http://ifdefined.com/btnet. * Fixed bug 1891559, "Email message no longer has a border around each item." Same bug described here: http://sourceforge.net/forum/forum.php?thread_id=1890301&forum_id=226938 Some people reported that the css doesn't work in the email notifications. As a workaround, I added a "ForceBordersInEmails" which uses border=1 instead of css to create a border in the emails. See also "btnet_css_for_email.css.renamed". If you rename that file to "btnet_css_for_email.css", notifications will use that css file. * Fixed bug with generate_btnetsc_reg.aspx. It's the page that generates a .reg file for the screen capture utility's settings. There was some debugging code accidently left in it. * Fixed bug 1904370 "index out of range error on edit_bugs.aspx" when user is guest and there are no projects in the project dropdown. * Modified email.cs after experimenting with hosting an instance of BugTracker.NET at GoDaddy. Now, even if you storing attachments in the db, the app will still use the "UploadFolder" in order to temporarily store attachments in the files system before being loaded into the db. Before, the logic always tried to create a temporary folder, which it doesn't have the rights to do at GoDaddy. * Fixed a bug where sometimes the bugs.aspx would crash trying to use a filter that no longer applied to the query.You had to switch back and forth between the search and bugs page to make the crash happen. * Fixed "Object reference not set to an instance of an object" bug that was happening at BugTracker.NET running at GoDaddy. Where the logic was looking for a custom field in the Request's variable collection, the logic now handles the case of the variable being missing. * Merged in code from Gerard Chanekon that adds ids to project specific custom fields in edit_bug.aspx, to help with css. * Corrected insert_bug.aspx to truncate short description at 200 chars, not 100. Enhancements: * Added "days ago" to the dates displayed in edit_bug.aspx * Some cosmetic changes to edit_bug.aspx and search.aspx. * The app intercepts errors and writes them to the log and can also send an email with the info. Now writing the server variables into the log and error notification emails. Server variables means things like the IP of the browser, User Agent, Referer, Cookie Values... ----------------------------------------------------------------------- Version 2.7.8 2/23/2008 ----------------------------------------------------------------------- To upgrade to this release, run the SQL from upgrade.sql that creates the emailed_links table. You only need this table if you turn on the new features related to the new Web.config settings "AllowSelfRegistration" and "ShowForgotPasswordLink". * Fixed bug 1884391 - prevent entry of more text into a custom TEXTAREA field that would cause a databse truncation error. * Fixed bug on relationship page - sibling/parent/child radio button wasn't being initialized * Corrected the sample code in workflow.cs. * Fixed bug where emails with subjects longer than 200 chars were failing to be inserted into the db. Now insert_bugs.aspx truncates the subject at 200. * Added option to enforce strong passwords. See"RequireStrongPasswords" in Web.config. Turning on the flag has no effect on users until they try to change their passwords. This satisfies RFE 1726311. * Users can now reset their own passwords if they forget them. See "ShowForgotPasswordLink" in Web.config. This satisifies RFE 904044. * Users can now register themselves (add themselves to the user table). See the following settings in Web.config: "AllowSelfRegistration" "SelfRegisteredUserTemplate" "RegistrationExpiration" * Format of user's email address is now validated. ----------------------------------------------------------------------- Version 2.7.7 2/16/2008 ----------------------------------------------------------------------- * Added new Web.config setting "AllowGuestWithoutLogin". This is the explanation from Web.config: There's a special user in the database, "guest". Think of it as a user account that can be shared by several people. The guest user can't save settings and can't save searches. If "AllowGuestWithoutLogin" is set to "0", then the guest user still has to login with a password. If set to "1", then the guest user doesn't need to even enter a password. Instead, a link will appear on the login page, default.aspx, saying: Continue as "guest" without logging in You can control the per-project permissions of the guest user in the same way as other users EXCEPT that even if you give the guest user permissions beyond View Only and Reporter, the system will automatically reduce his permissions downward. * Modified search of comments to also search email bodies. * Bug's last update datetime/user is now updated when an email is sent. * Some people have reported that there are no borders around the comments in the email notifications. I made changes to print_bug.cs that may have fixed the problem. Not sure, sinece I could never reproduce the problem. If you had this problem before and this release fixes it, please let me know at ctrager@yahoo.com. * Added another query sample to setup.sql. This one shows the bugs that have been stuck the longest time without a status change. Here's the SQL if you want to try it out: select case when datediff(d, isnull(bp_date,bg_reported_date), getdate()) > 90 then '#ff9999' when datediff(d, isnull(bp_date,bg_reported_date), getdate()) > 30 then '#ffcccc' when datediff(d, isnull(bp_date,bg_reported_date), getdate()) > 7 then '#ffdddd' else '#ffffff' end, bg_id [id], bg_short_desc [desc], datediff(d, isnull(bp_date,bg_reported_date), getdate()) [days in status], st_name [status], isnull(bp_comment,'') [last status change], isnull(bp_date,bg_reported_date) [status date] from bugs inner join statuses on bg_status = st_id left outer join bug_posts on bg_id = bp_bug and bp_type = 'update' and bp_comment like 'changed status from%' and bp_date in (select max(bp_date) from bug_posts where bp_bug = bg_id) WhErE 1 = 1 order by 4 desc * In queries.aspx, now preserving the line breaks in the SQL, for easier reading. * Cosmetic changes to edit_bug.aspx, which I hope folks will like. * Printing of "detail" reports should have better performance. Before, the css styles were wrongly being included once per bug, not once for the whole page. ----------------------------------------------------------------------- Version 2.7.6 2/8/2008 ----------------------------------------------------------------------- * Fixed bug: when user has only view or reporter permission, the bug's short description was hidden on the edit_bug.aspx page. * Changed the implementation of filters dropdowns in the bug lists so that usually, they only show choices that are actually present in the bug list. Before this change, if you had external users looking at bugs assigned to internal users, the filter dropdowns would have been missing the internal users. Thanks to Suchacek Zdenek for reporting this. * I added a way to make it a bit easier for somebody with C# coding skills to build strict workflow rules in BugTracker.NET. See the new file, App_Code\workflow.cs. It's the designated spot for your custom C# code to control the transition of statuses. For example, if you want to say that the only valid status after "tested" is "deployed", or if you only want users in the "testers" group to mark a bug as "tested", then you could add your logic to this file. See the comments in the file for more detail. ----------------------------------------------------------------------- Version 2.7.5 2/2/2008 ----------------------------------------------------------------------- This release adds some LDAP/Active Directory support. Before deploying this release, you must change your Web.config file. Your Web.config might be different from mine, but for me, the change I had to make was from this: to this: To enable LDAP support, configure these settings in your Web.config: When you enable LDAP support, the application checks user passwords against the ones stored in your LDAP directory rather than the ones stored in the database. The zip also contains sample code for importing users from LDAP into BugTracker.NET's database. See "import_users_from_ldap_sample.cs". Also: * Fixed bug with duplicate users in user dropdowns that affected "external" users. Thanks to Suchacek Zdenek for help with this. * Fixed how app was handling bugs associated with inactive projects or inactive users, or users who are no longer marked assignable. Before, if a bug was assigned to an inactive user, and then you updated the bug in some other way, you would inadvertently also change the user too, because the inactive user was missing from the dropdown. Now, the current project/user is always FORCED into the dropdown, even if it is inactive. ----------------------------------------------------------------------- Version 2.7.4 1/27/2008 ----------------------------------------------------------------------- * With this version, BugTracker.NET no longer supports storing user passwords unencrypted. The setting "EncryptStoredPasswords" is now ignored because passwords are now ALWAYS stored encrypted. To upgrade to this version, run the following SQL to modify your database before deploying the new web pages: alter table users add us_salt int null As users log in, if their passwords had been stored unencrypted, the app will automatically update the database with the encrypted passwords. Or, you can encrypt all the passwords by invoking this page: upgrade_723_to_724.aspx Even passwords that had been encrypted before will be re-encrypted with a stronger encryption scheme. * Now using the the ASP.NET "App_Code" folder. Util.cs has been split up into several smaller files. * Adding attachments now updates the bug's last update date and user id. ----------------------------------------------------------------------- Version 2.7.3 1/19/2008 ----------------------------------------------------------------------- See "upgrade.sql" for database changes for this release. Run the relevant part of the script against your database to upgrade. * Added field level permissions for the non-custom fields. As admin, go to "organization" and see the field level permissions related to project, org, category, priority, assigned_to, status, and the user-defined-field. No field level permissions on custom fields or project-specific custom fields. * Added the concept of parent/child to relationships between bugs. ----------------------------------------------------------------------- Version 2.7.2 1/12/2008 ----------------------------------------------------------------------- THIS RELEASE FIXES SECURITY VULNERABILITIES. Please email me at ctrager@yahoo.com if you think there are still vulnerabilities. * Fixed the worst Cross Site Request Forgery (CSRF) vulnerabilities. This is work is related to bug 1867089 "Multiple XSS and CSRF vulnerabilities". Many thanks to Si Wong for discovering and reporting these important vulnerabilities. For more about CSRF, also known as "session riding", read here: http://www.cgisecurity.com/articles/csrf-faq.shtml Until you install this release, a worst-case scenario is, if you are an admin and logged into BugTracker.NET, and while you are logged in - while your browser cookie is still in effect - if a bad guy could get you to view his malicious web page, then just by viewing that page you could delete bugs from your BugTracker.NET database. With the fixes in this version, I've closed all the vulnerabilities that I know about. Specifically, I revised all the delete_xxx.aspx pages. I've also revised massedit.aspx, subscribe.aspx, flag.aspx, and relationships.aspx. * Fixed the specific XSS vulnerability described in bug 1867089, where a user could enter javascript into a text custom field that would then be executed if a user without edit permissions views the page. I'm not aware of any other XSS vulnerability. * Fixed edit_self.aspx's project subscription dropdown. It shouldn't have been showing the "no project" option. * Fixed bug 978216 "Globalization problem on custom fields when type is float". Or rather decimal. Edit_bug.aspx was changed to handle the European decimal fields, which can use a comma as the separator instead of a period. Thanks to Christian Jundt for the code. * Added logic to insert_bug.aspx to allow for an attachment to be posted without wrapping it inside an email message. ----------------------------------------------------------------------- Version 2.7.1 1/6/2008 ----------------------------------------------------------------------- * The flag column in queries now has a filter, just like category, status, priority, etc. * Friendlier handling of sql errors in bugs.aspx, so that if you edit a query introducing a syntax error in the SQL, it's easier to get back to the query page. * Fixed bug 1661602 "Bug count is incorrect when filtering bugs". Now when a filter changes the number of bugs shown in a query, the text becomes: Showing N out of N bugs returned by query. * Resolved bug 1863186 "HideSql flag ineffective in 2.7.0". Actually, support for the Web.config "HideSql" setting was dropped in version 2.5.8, but I forgot to remove it from Web.config itself. ----------------------------------------------------------------------- Version 2.7.0 12/21/2007 ----------------------------------------------------------------------- * Fixed bug - "or" logic in search page allowed people to see items in the list that they don't have permission to see. The sql had been wrong, something like this: where has permission OR matches criteria 1 OR matches criteria 2 The corrected SQL is something like this: where (has permission) AND (matches criteria 1 OR matches criteria 2) * Fixed bug in search screen - the "organization" dropdown was showing organizations even if the user didn't have permission to see them. Now, if the user doesn't have permissions to see other organizations, the dropdown isn't even shown. * Fixed bug with the flag feature - flag.aspx was caching. Add logic to tell the browser not to cache flag.aspx. * Added new feature, "create copy". It will create a copy of a bug, not including related posts. ----------------------------------------------------------------------- Version 2.6.9 12/14/2007 ----------------------------------------------------------------------- Bugs: * Fixed bug in search "left outer join orgs on ct_id = bg_org" should read "left outer join orgs on og_id = bg_org". * Fixed javascript error with svn_log.aspx. Thanks to Walt Crosby for being persistent about reporting the bug and supplying the correct code. * Added missing permission check to subscribe.aspx. * Added isnull() to check for project custom fields in search.aspx, in case you have nulls in those fields. * Fixed some typos related to project custom dropdowns in search, for dropdowns 2 and 3. Also, improved performance of search with regards to project custom dropdowns. The page no longer makes a trip to the server if you are NOT using project custom dropdowns. * Fixed "Object not set to reference bug on this line in edit_bug.aspx when a user with Reporter permission tries to update a bug with a custom field: Line 1851: string val = Request[drcc["name"].ToString()].Replace("'","''"); New Feature: Add ability for each user to mark bugs with a personal flag, like, "Flag for follow-up". Use the new magic "$FLAG" macro in your queries as shown below. You also need the left outer join with the bug_user_flags table. Select ...., isnull(fl_flag,0) [$FLAG],... from bugs left outer join bug_user_flags on fl_bug = bg_id and fl_user = $ME ----------------------------------------------------------------------- Version 2.6.8 12/07/2007 ----------------------------------------------------------------------- Upgrade your database for this version using the SQL here: alter table bugs add bg_org int not null default(0) alter table orgs add og_other_orgs_permission_level int not null default(2) * Fixed bug 843284 "svn diff, blame can't handle unix style line endings" * Fixed recently introduced bug where view-only users were seeing the wrong values in the dropdowns. * Fixed bug with edit_user.aspx. It was losing the user's default query selection. * Fixed bug with adding subscribers in view_subscribers.aspx. Only the newly added subscriber should get a notification. * Fixed bug for when there are two "WHERE" clauses in the SQL and it's the second one that needs to be altered for the permissions. It's a workaround. First the logic looks for "WhErE", with the upper/lower case letters exactly like that. Note the weird capitalization. For an example, see setup.sql, "demo last comment as column". * Fixed bug with add_svn_file_revisions.aspx. It was submitting the data twice. Thanks to Walt Crosby for the fix. * Fixed bug 1707551 "[No project] = no edit" - when somebody adds a bug and doesn't set the project, then nobody can get to it in order to add the project if the DefaultPermissionLevel is not 2. New features: * You can now associate a bug to an "Organization". Typically, an "Organization" would be your company's customer, but it could also be a department within your company, or whatever group of users you want. * Added "Permission level for bugs associated with other (or no) organizations". This allows you to restrict a gorup of users to just being able to see bugs associated with that group. Typically, you would use this to restrict a customer, or an individual, to only seeing bugs associated with that customer or individual. ----------------------------------------------------------------------- Version 2.6.7 12/01/2007 ----------------------------------------------------------------------- * Added "organizations". See admin page. Some of the permissions that used to be on the third tab of the add/edit user page page are now on the add/edit organization page. If you are looking for something like a user "role", use "organization". Actually, this new "organization" entity doesn't really do much yet, but its the basis for the next round of changes, to make BugTracker.NET a better tool for an internal team to collaborate with external customers. * A query can now be visible either to 1) everybody, or 2) just one user or 3) just one organization. If anybody wants to modify the code, and upgrade.sql too, so that the query-role relationship is many-to-many, so that one query can be associated with multiple organizations, I'd welcome that. Send it to ctrager@yahoo.com * Repaired the very poorly documented "guest" user feature that's been in the app for a couple years. It still needs documentation. Set up a user with the username of "guest" and limited either view only, or reporter only permissions. He will be different than other users because he will not be able to save searches as queries or change his own settings. In this way, several people can share the same "guest" account. ----------------------------------------------------------------------- Version 2.6.6 11/25/2007 ----------------------------------------------------------------------- New Features: * Search now handles project custom dropdowns. Thanks to Jason Kresowaty, who took my primitive implementation and fixed and finished it. * The edit_bug.aspx page now has more "AJAX" behavior. Specifically, you can now do the following without having to first save your bug changes: add attachments dd relationships toggle show/hide images toggle show/hide change history get/stop notifications You still have to save your changes before clicking a link that would bring you to the send_email.aspx page. * You can now delete received emails if you are admin or have been given the permission by an admin. * Some changes to btnet_base.css to make it easier for folks to customize the layout of edit_bug.aspx. Bug fixes: * Adding an attachment caused the user doing the adding to receive notification even when "Send notifications even for items you add or change" was not checked. * Emails with attachements and bugs posted by screen capture caused an additional notification per attachment. * Along with this release I'm posting a new version of the screen capture utility, btnetsc.exe version 2.1.1. There was a bug fix: Posting a screenshot to an EXISTING bug wrongly created a NEW bug instead of adding an attachment to the specified existing bug. ----------------------------------------------------------------------- Version 2.6.5 11/18/2007 ----------------------------------------------------------------------- * !!!!!IMPORTANT!!!!! Print bug AND email notifications were both broken by 2.6.4 because the logic was looking for btnet_custom.css in the wrong folder. If you don't want to move to this release, then you can put an additional copy of btnet_custom.css into the parent btnet folder to fix the problem. * Cosmetic changes in the add/edit bug form. The goal is to make it easier to read for all three categories of users: - full add/edit permission - reporter only permission - view only permission In general, in the coming releases, I want to make BugTracker.NET better as a tracker that faces outside, customers, clients, users, rather than just a tracker that is used internally. * "Comment visible to internal users only" shouldn't have been visible to view-only users * In relationships page, "detach" link shouldn't have been visible to view-only users. * Hid links that view-only users shouldn't see: add attachment send email ----------------------------------------------------------------------- Version 2.6.4 11/17/2007 ----------------------------------------------------------------------- See "upgrade.sql" for database changes for this release. Run the relevant part of the script against your database to upgrade. * Created new "custom" folder and moved several files into it. All the files intended for customization are in this folder now, except for Web.config. When you upgrade to a new version of BugTracker.NET, just make sure you don't overlay your Web.config and all the files in the "custom" folder. * Added ability to specify subversion repository, user, password and WebSvn URL for specific projects different from the overall global settings in Web.config. * Fixed svn_blame.aspx. It wasn't HTML encoding the text of the document, so if the code had HTML tags, the page displayed nonsense. * RFE 1750613 "Project Description and name, not just name" * BugTracker.NET now gives you the choice of storing attachments in the database instead of in a file folder. You can switch the setting back and forth, because the app will always look in both locations if it can't find the attachment in the first location. Thanks to Jason Kresowaty who did all the work on this change. This satisifies the following RFE's: 1825966 "Attachment as BLOB field in DB" 1468063 "Image Upload in SQL Database" * "UploadFolder" setting was missing from recent versions of the Web.config file. * Fixed bug with send_email.aspx when forwarding comments entered with font/color formatting. Thanks to Jochen Jonckheere for the fix. * Changed "about.aspx" to "about.html". * RFE 1832515 "Show Field Name When Editing Custom Field" * Fixed default.aspx to use custom_logo.html. ----------------------------------------------------------------------- Version 2.6.3 11/10/2007 ----------------------------------------------------------------------- * The Web.config setting "LogoHtml" is now obsolete. Instead, there are now three new files that give you even more control over the look: custom_logo.html - The "BugTracker.NET" logo is in this file. If you are using "LogoHtml", copy your HTML to this file instead. You don't have to escape the HTML characters. custom_header.html - HTML that is written before the logo and links at the top. custom_footer.html - HTML this is written just before the closing tag. Changes you make in these files don't take effect until you restart the Web application - For example, by "touching" Global.asax by entering a space character in it. * More subversion integration: Added "TortoiseSVN_integration.bat" to the Subversion folder. It's another, nicer, way to integrate Subversion with BugTracker.NET. For general information about how this script works, see: http://tortoisesvn.net/issuetracker_integration Also modified btnet_post_commit.vbs to have the option to work with the nicer TortoiseSVN integration. It can optionally look for the bugid at the end of the checkin comment instead of the beginning. ----------------------------------------------------------------------- Version 2.6.2 11/8/2007 ----------------------------------------------------------------------- Along with this release of the web pages, there's a new release of the screen capture utility, btnetsc_2.0.exe. The new screen capture supports SSL. If you aren't using SSL, you don't need to upgrade. Thanks to Jason Kresowaty, who did all the work. Bug fixes in this release: * svn_diff.aspx ("diff") wasn't escaping HTML tags. * svn_diff.aspx didn't color some diffs right (when unified diff output omitted the number of lines in the block) * If "PromptBeforeLeavingEditBugPage" setting was turned on, toggle images/history links resulted in page-not-found. Also: * Added an additional way to integrate with Subversion, by adding a link to a WebSvn (or similar) web page. See the new Web.config setting "WebSvnUrl". * Swapped svn_log.aspx back to listing most recent on top. * Removed the "edit" column at the far right of the bug lists * Revised the page that generates registry settings for the screen capture utility, generate_btnetsc_reg.aspx. It no longer creates a setting for "Port" since you would now specify that in the URL itself, if it's not a standard port. ----------------------------------------------------------------------- Version 2.6.1 11/5/2007 ----------------------------------------------------------------------- Important bug fixes: * Adding a user didn't set the user's password correctly. You had to re-edit the users password before it really got into the db. This bug was introduced in version 2.5.8. * "EncryptStoredPasswords" setting in Web.config was being ignored. I think also introduced in 2.5.8. * Version 2.6.0 Subversion post-commit script wasn't handling multiline checkin comments. * Subversion post-commit script wasn't handling single quotes in checkin comments. * With the addition of the additional user fields in 2.5.8, the users.aspx page, the list of users, was hard to user because the "edit" link was so far from the name of the user. Moved it to the far left. Also, added the revised pre-commit script by Jason Kresowaty. Thanks Jason, for your patience. Also from Jason: * now displaying Subversion dates in a nice format. * svn_log.aspx handles deleted files better. ----------------------------------------------------------------------- Version 2.6.0 11/3/2007 ----------------------------------------------------------------------- Big changes to the Subversion integration. If you are using the new Subversion pages in 2.5.9, you should upgrade to 2.6.0. First of all, if you aren't using version control at all, start using Subversion and TortoiseSVN. If you are using SourceSafe, you might still want to experiment with Subversion/TortoiseSVN and BugTracker.NET together just to see what you are missing. IMPORTANT: To migrate to this release, run the SQL in upgrade.sql. The sql creates two new tables, svn_revisions and svn_affected_paths and loads them with whatever data you have in the bug_file_revisions table. These two new tables REPLACE your old bug_file_revisions table. I am not deleting that table, but I'm no longer supporting it. IMPORTANT: You **MUST** replace your BugTracker.NET subversion post-commit hook script to work with the new database tables and new web pages. Just modify the new one the same as the old, changing the path to the "svnlook.exe" command and your database connection string. I've also revised the script to make it easier to read and debug. Also, several new pages REPLACE the view_file_revisions.aspx page. You will be able to do the svn commands cat, log, diff, and blame from within BugTracker.NET. I'm interested in feedback on the Subversion integration, so please let me know what you think at ctrager@yahoo.com. For admins, there is a link at the bottom of the "revisions" page to manually connect a revision to a bug, in case there's a glitch with the post-commit script (like, the db was down at the time of the commit?), or if you forgot to put the bugid in the comment. Bug fixes in the subversion pages include: * Better handling of file renames, although it's not perfect. See the note on renames in Subversion's documentation: http://svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html * Handling of spaces in file paths. * Fixed ocassionaly hangs capturing the stdout output of the svn command. Also, bug fixes unrelated to Subversion: * Added title to reports produced by "view data" link. * Fixed bug with single quotes in the both the labels and values of project-level custom dropdowns. ----------------------------------------------------------------------- Version 2.5.9 10/30/2007 ----------------------------------------------------------------------- Inportant bug fixes. New features too. Also, better Subversion integration. First, thanks to everybody who quickly reported the bugs in 2.5.8 and especially to Jochen Jonckheere who provided several of the fixes. And sorry to everybody for the inconvenience. So, first these are bugs that I introduced in 2.5.8 and am fixing in this release: * Edit_user.aspx as broken. If you tried to add a new user. * Notifications didn't get sent if the ONLY change was a change to comments. * Delete_comment.aspx was broken. * Translate.aspx was broken. * In the admin pages that list categories, statuses, priorities, the "id" column was missing and a new "hidden" column was showing. Other changes: * In the lists of bugs on the bugs and search pages, the filters, sorts, and page (when the list is long and has to be broken into pages) is remembered until you run a new query. This fulfills RFE 1720096 "Retain applied filters on bugs screen" and RFE 1632312 persistent sort/filter. * Now checking for dupe query names before saving * Changed the behavior of the "history", "relationships", "subscribers" links in edit_bug.aspx. Instead of them opening a fake modal-ike window, they open a real browser window. * Added "PromptBeforeLeavingEditBugPage" setting to Web.config. If you set it to "1", then clicking on the "add attachment", "send email", and the hide/show toggle links causes their to be a prompt warning the user that unsaved changes will be lost. It should be a per-user setting, but right now it's not. Sorry. Subversion Integration Because of the bugs I introduced in 2.5.8, I am doing this release ASAP I happen to be in the middle of improving the Subversion integration. If you give the web server machine client access to subversion, and set the following settings in Web.config appropriately, you'll see some of the new pages working. Maybe you want to experiment with them and give me feedback? In the next week or two I hope to complete this work and provide documentation. But for now, maybe experiment. I've also put a new Subversion "pre-commit" script into the Subversion folder. The author is Jason Kresowaty. Thanks to Jason for the script and for good info/advice about Subversion. "EnableSubversionIntegration" "SubversionRepositoryUrl" "SubversionPathToSvn" "SubversionUsername" "SubversionPassword" ----------------------------------------------------------------------- Version 2.5.8 10/26/2007 ----------------------------------------------------------------------- To migrate from 2.5.7 to 2.5.8 run the sql in upgrade.sql. IMPORTANT: This release affects user permissions and the behavior of the search page. It's possible that some non-admins will temporarily have FEWER permissions because I'm changing some settings to be from global, for the entire installation, to per-user. All users will be able to save searches as queries, but only users you choose will be allowed to edit the raw sql. Please keep reading for the details: * The following settings in Web.config are now obsolete. Instead of the global switches here in Web.config, you can now control these settings for individual users, which is explained in the next bullet point: HideSql AllowQueryPageForNonAdmins AllowBugDeletionForNonAdmins AllowCommentDeletionForNonAdmins AllowBugMergingForNonAdmins AllowAttachmentDeletionForNonAdmins AllowQueryEditingForNonAdmins * The following fields have been added to the users page, permission tab. Here's how they are explained on the page edit_user.aspx, in the permissions pane: Use the following settings to control permissions for non-admins. Admins have all permissions regardless of these settings. [] External user (External users cannot view posts marked "Visible for internal usrs only") [] Can edit sql and create/edit queries for everybody [] Can delete bugs [] Can edit and delete comments and attachments [] Can merge two bugs into one [] Can mass edit bugs on search page [] Can use reports [] Can create/edit reports [X] Appears in "assigned to" dropdown in edit bug page (defaults to true) Except for "Appears in 'assigned to' dropdown in edit bug page", all the other fields default to false. That is, if you had any of the "Allow" settings in Web.config set to "1", you will have to edit the user permissions to restore the feature to that user. For example, if you had "AllowBugDeletionForNonAdmins" set to "1", you will have to edit each user and check "Can delete bugs". You could also run some SQL to update settings for all users. The format would be: update users set XXX = 1 Replace X with one of the new fields: us_can_edit_sql us_can_delete_bug us_can_edit_and_delete_posts us_can_merge_bugs us_can_mass_edit_bugs us_can_use_reports us_can_edit_reports The end result of removing the fields from Web.config and putting them on the user page is that you now have finer-grained control over who can do what. * All users by default now have the ability to save search criteria as a private query that only that user can see. Users with minimum permissions cannot see or edit the sql itself. Admin can grant permission to individual users to see and edit sql, create public queries. * Added new feature/concept: a distinction between internal and external users. The feature is turned off by default. Enable by setting "EnableInternalOnlyPosts" in Web.config to "1". When enabled, acheckbox appears where you can add/edit comments or attachments. The checkbox lets you mark the comment or attachment as "Visible to internal users only". Users marked "external" on the edit_user.aspx permission pane won't be able to see them. Please read the entire comment in Web.config. * Added the ability to create a new user by copying an existing user. Everything on the edit_user.aspx page gets copied except for the source user's username, first and last name, password, email address, and email signiture. All the permissions get copied. * Cosmetic change. The links to "edit" or "delete" things like users, projects, categories have been moved from the far right to the far left. ----------------------------------------------------------------------- Version 2.5.7 10/14/2007 ----------------------------------------------------------------------- The changes in this release only affect appearance - the css files and how they interact with the web pages. Btnet_base.css has been changed so that more control of the tables is in .css. But good luck actually changing anything - I found that Firefox and Internet Explorer's reaction to table-related css changes to be very different. If you have made changes css changes to customize the look of tables, it's possible that you will have to adjust them with this release. But you'll end up with more css control. Also, if you have wanted to use css positioning, you might have found that changes to the edit page break the search page. Now the edit bug page, edit_bug.aspx, now additionally includes the btnet_edit_bug.css and the search page, search.aspx now additionally includes btnet_search.css. These new css pages allow you to change css positioning of elements on those pages indepenently, so that changes to positioning on one page don't affect the other. * Fixed bug 1806180 - "Sortable.js doesn't maintain class attribute on table." * Fixed bug 1778632 - "Using custom CSS formats Search page too" * Did RFE 1033103 - "Move All Formatting to CSS" ----------------------------------------------------------------------- Version 2.5.6 9/23/2007 ----------------------------------------------------------------------- No features or bug fixes in this release. The code is now more compatible with Visual Studio. The ideas for these changes come from Andrew McKay. You can now compile and publish the web pages using Visual Studio. More detail about the changes: * The files related to SharpMimeTool.dll have been moved to a separate "SharpMime" folder and now there is a csproj file too. * Likewise, code for btnet_service.exe and btnet_console.exe also have been moved to a seperate "btnet_service" folder and there are csproj files for each. * Renamed some "inc..." files so that they have an .inc file extension instead of an .aspx extension. The .aspx was confusing to Visual Studio. * Made minor changes to the code to make a lot of the compile warnings go away. You can ignore the warnings about about the obsolete System.Web.Mail and System.Configuration.ConfigurationSettings. They still work fine. ----------------------------------------------------------------------- Version 2.5.5 9/21/2007 ----------------------------------------------------------------------- Important bug fix: * Fixed bug 1800000 "Search.aspx throwing error in SQL" - because there's a space missing after the "and" or after the "or". * Fixed bug in insert_bug.aspx if screen capture or btnet_service.exe tries to use it after website has been idle for a while, related to forum thread "project email insertion causes strange error". ----------------------------------------------------------------------- Version 2.5.4 9/16/2007 ----------------------------------------------------------------------- * Enhanced search: Added radio button that allows users to use "or" logic between SQL where clauses instead of always "and". So, instead of where A = 1 and B = 2 and C = 3 You can do where A = 1 or B = 2 or C = 3 It's either all "and" or all "or". Also, for custom text fields that are not dropdowns, SQL uses "like" operator instead of equals. That is, search looks for rows where the field has a value that contains the text the user typed in rather than rows where the field has a value that exactly matches what the user typed in. * Fixed bug 1647742 "Popups don't close always and should have a delay". I you have disabled the popups because you thought they were annoying, I encourage you to try them again. Email me at ctrager@yahoo.com and tell me what you think. * Fixed bug in send_mail.aspx. The bug description and the fix are from Jochen Jonckheere: "The forwarded email didn’t contain the original e-mail, or just a part of it. The cause is that FCKeditor sees a < or > as the beginning of a tag and if it isn’t a valid one the rest of the text is ignored. This only occurs when using Firefox." * Fixed bug 1789400 "Error when searching with no criteria selected". The problem was a custom column with the characters "order" as part of its name. Confused my logic that looks for the "ORDER BY" clause in SQL. ----------------------------------------------------------------------- Version 2.5.3 9/3/2007 ----------------------------------------------------------------------- * Added support for GMail SMTP and POP3. See new settings in Web.config and btnet_service.exe.config. Thanks to Eric (TehOne) Lebetsamer for the code. * Fixed bug 1771868 "Tabs don't change on settings pages for IE" * Fixed bug 1766649 "Decimal custom fields cause search.aspx to crash" Thanks to "David" for the code. * Added "LogSqlEnabled" setting in Web.config, which you can use to log less by setting to "0". ----------------------------------------------------------------------- Version 2.5.2 7/15/2007 ----------------------------------------------------------------------- * I posted version 1.9 of btnetsc.exe, the screen capture utility. It now works with non ascii (Chinese, Arabic, etc), both the short description and the longer comment area. Also, you no longer have to tell it the "codepage". (This was my own personal #1 bug. I probably spent 100 hours trying to get btnetsc.exe to fully support Unicode. Whew!) * RFE 1749357 "Allow filtering on empty field" - Added [none] and [any] options to the dropdown filters. In order for these to work right, you have to make sure that all your bug queries return blanks, not nulls for columns with no value. See setup.sql for how I've used "isnull" in the queries, for example: select .... isnull(ct_name,'') .... left outer join categories.... * RFE 1744256 "please remove 7000 character limitation" - removed the restriction. * RFE 1746947 "Filter User List (Admin page) - show/hide inactive users" * Fixed date format in btnet log (for debugging). It should always show time down to seconds regardless of app's display format. * Added some logging messages that might help folks who have the problem where they log in and get redirected back to the login page over and over. It doesn't fix the problem, but it makes it clearer if the problem is being caused by the failure of the browser to send the cookie back that was issued to it when the browser logged in. ----------------------------------------------------------------------- Version 2.5.1 6/26/2007 ----------------------------------------------------------------------- * Fixed upgrade.sql. It was missing the "pu_admin" column on project_user_xref, required for upgrading to 2.5.0. * Fixed generate_btnetsc_reg.aspx. It had the wrong registry key. Thanks to "romwil" for the code for this fix. * Enhanced insert_bug.aspx so that categories, etc can be controlled from the query string. See README.HTML. Look for "$CATEGORY$". * Added a "more CSS info..." link to edit_priority.aspx, edit_status.aspx. If you are using CSS styles to indicate different priorities and statuses, or if you are interested in doing so, then click on that link. The new page (edit_styles.aspx) gives you an overview of the combined effect of the priority and status styles. ----------------------------------------------------------------------- Version 2.5.0 6/15/2007 ----------------------------------------------------------------------- Run this SQL for this upgrade (also found in upgrade.sql) alter table users add us_enable_bug_list_popups int not null default(1) alter table users add us_created_user int not null default(1) * Added new feature "project admin". An admin is able to give permission to a regular user to add and delete users for specified projects. This features satisfies RFE: 1451208 "New role of project admin - can add users for his project" Does not satisfy the following which deals with changing project settings. 1719295 "Admin for his own project" * Added ability in user settings to turn OFF the green popups in the bug lists. * This won't matter to you unless you have modified your copy of BugTracker.NET's source code: Re-arranged some code. I moved things out of a couple of the "inc" files and into util.cs. I also organized the code a bit within util.cs into more classes. The following files are now gone: inc_insert_bug.aspx inc_print_bug.aspx edit_user_permissions.aspx * Added a link "screen capture" to bugs.aspx to make it easier to get started with the screen capture utility. From it you can download the screen capture utility from sourceforge and you can generate a .reg file to initialize btnetsc.exe's settings. *Along with this release, I'm posting btnetsc_1.8.exe. (The screen capture utility). It now looks for its settings in a new place in the registry that isn't version dependent, so that as you upgrade without loosing your previous settings. * Also new in screen capture utility, You can now also post screen capture images to EXISTING bugs rather than being forced to create new ones. * Rearranged the code in upgrade.sql, so that the most recent entries are at the bottom instead of the top. * Emails are now sent UTF8 encoded. If somehow that breaks things for you, set the new "BodyEncodingUTF8" Web.config setting to "0". * Made cosmetic changes to the "settings" page the pages for editing users, edit_self.aspx and edit_user.aspx. They have something like tabs now, except that the tabs don't look like tabs. ----------------------------------------------------------------------- Version 2.4.9 5/12/2007 ----------------------------------------------------------------------- To migrate from 2.4.8 to 2.4.9, run the sql in upgrade.sql: alter table bug_posts add bp_comment_search ntext null alter table users add us_use_fckeditor int not null default(0) alter table bug_relationships alter column re_type nvarchar(500) * This release integrates "FCKEditor" (www.fckeditor.net). To try it out, go to your user settings and check "edit using colors and fonts". Thanks to Jochen Jonckheere for this nice new feature. * Changed the documentation in README.html. Most important to some of you, I added instructions on how to use the Visual Studio debugger with BugTracker.NET. (Thanks to the anonymous person who posted the instructions on the sourceforge forum.) * Fixed bug 1708170 "Using presets does not refresh Re-assign drop down". I fixed it by removing "project" as one of the fields that the preset link changes. * Fixed bug - Dropdown filter was showing users who didn't have permissions in projects for which the logged in user has permissions. * Fixed bug 1689731 "bug relationship with long comment causes SQL error". I increased the size of the column 500. * Fixed bug where users without project permissions related to the logged on user were being displayed in the user filter dropdowns of the bug lists. * Changed the send_email.aspx "To:" field allow for more characters. * The "edit comment" page is now only available for comments. Not for sent emails, history of updates. It doesn't make sense to be able to edit the text of an email after it has been sent. * Cosmetic improvements: Changed edit_bug.aspx so that its appearance can be a bit more controlled using style sheets. I also added some more sample code to btnet_custom.css. The intent of the changes and the sample code was to show that you could align the column of the labels and dropdowns the way you liked, using css. * Recompiled btnet_service.exe, just in case I had forgotten to last time... Sorry... * Corrected the spelling of "EXCEPTION" in Global.asax. * Added a note about the "sessionState" setting and the "mode" attribute in Web.config. * Fixed another null object error in "print details" related to ASP.NET session timeout. * Fixed bug where emails weren't being processed right because header fields said "from:" instead of "From:". Discussed in Help Forum topic "from: missing from emailed bugs". For more info, see: http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework/topic62515.aspx * Now preventing passwords from being filled in automatically on the "edit user" pages. Added "autocomplete=off" to password and confirm password fields. * Not sure if this made it into the compiled version of btnet_service.exe or not in 2.4.8, but this time for sure the service now is marked as having a dependency on TCPIP. That allows Windows to know that it needs to start the network stuff before it starts this service, like when the server is rebooted. Thanks to Jochen Jonckheere. ----------------------------------------------------------------------- Version 2.4.8 3/11/2007 ----------------------------------------------------------------------- * Fixed bug 1663239 "Swedish characters stripped in email bug reports" The problem is related to how the POP3 service client reads the input. I'm a little bit worried that my fix is risky, so only turn on the fix if you think you need it. To turn it on, set "ReadInputStreamCharByChar" in btnet_service.exe.config to "1". * Fixed bug 1672988 "Custom user dropdown shows integer rather than name in email" * Fixed bug 1643938 "Item has already been added. Key in dictionary: SERVER_NAME". Or, at least I hope I fixed it. I can't reproduce it, but I got rid of the line of code that was causing it, I think. Let me know if you still have this problem. The folks who have had it say it is very infrequent. * Fixed bugs 1649980, 1638919 "ERROR AFTER SESSION TIMEOUT". I'm still using ASP.NET session variables in a few places, but not the one here that was causing problems. * Added logic for RFE 836604 "allow customization of subject field of e-mail notifications". Related to this RFE, the app is no longer using Web.config setting "PutTrackingIdStringInNotifications". Instead, it is using new Web.config setting "NotificationSubjectFormat", which can do what the "PutTrackingIdStringInNotifications" setting did, and much more too. See comments in Web.config for "NotificationSubjectFormat" on how to use the new setting. * When you add somebody ELSE as a subscriber to a bug, that person will now get a notification at that moment, instead of having to do a subsequent change to trigger the sending of the email. * Changed btnet_base.css to make the filter dropdowns less wide. Not much difference on IE, but it helps with screen real estate on Firefox. * Added X axis labels to the line charts you can view from the "reports" page. * Made some minor performance improvements by batching up SQL on the search.aspx page. ----------------------------------------------------------------------- Version 2.4.7 3/02/2007 ----------------------------------------------------------------------- * "Fixed" bug 1654938 "Edit a comment destroys Umlaut's". Actually, I can't reproduce the problem, but I added a line in Web.config so that if you do have the problem you can turn on a fix for yourself. See the new Web.config setting "HtmlDecodeComment". * Add others as subscribers. From the subscribers link on the edit_bug.aspx page, you can now add others besides yourself as subscribers. * Changed btnet_service.exe "Installer" to record dependency on TCP/IP. Used code from Jochen Jonckheere verbatim. * Added "TotalErrorsAllowed" to btnet_service.exe.config. The comment there says: "How many errors should we allow before the fetch loop automatically stops? This is a safeguard in case there is some sort of problem with the web server where insert_bug.aspx does succeed in inserting the bug, but somehow fails to give a good response to this service. If the service doesn't get a good response, it will not delete the email from the pop3 server and will try to insert the email again when the fetch interval triggers another loop. The result can be a lot of duplicate bugs generated from the one problem email. This has happened to a couple people...." ----------------------------------------------------------------------- Version 2.4.6 2/24/2007 ----------------------------------------------------------------------- I added some integration with Subversion. If you aren't using Subversion, don't bother with this release. If you want to do the integration, run the sql in upgrade.sql and then read the instructions in the file. "btnet_post_commit.rename_to_vbs" Before using it, rename it to btnet_post_commit.vbs. With this script, when you commit to cvs, if you put the bugid at the start of you commit comment, the script will insert recs into a new bug_file_revisions table connecting the bug with the revision and the files. ----------------------------------------------------------------------- Version 2.4.5 2/22/2007 ----------------------------------------------------------------------- The handling of incoming emails is better with this release. I'm using the latest SharpMimeTools, downloaded from here: http://anmar.eu.org/projects/sharpmimetools Here's the line I use to compile the source into the dll: C:\cit\btnet>csc /debug /R:log4net.dll /target:library SharpMimeTools.cs ABNF.cs SharpMessage.cs SharpMimeAddress.cs SharpMimeHeader.cs SharpMimeMessage.cs SharpMimeMessageCollection.cs SharpMimeMessageStream.cs SharpDecodeOptions.cs SharpTnefMessage.cs Besides using a newer SharpMimeTools, I also made fixes to my code: * Fixed bug 1665336 "Thunderbird e-mails end up as HTML code". I'm now making an attachment of everything that does NOT look like the plain text message body. * Fixed bug 1663242 "Email attachments not working for Thunderbird". A variation on the same problem. * Fixed bug parsing incoming emails with multiparts nested within multiparts. A symptom of the bug was that I was failing to find a message body. * New Web.config "ProcessVariablesInEmails" setting for turning variable parsing on and off. Set to 0 by default, so if you were using these variables, make sure your Web.config now has this set to 1. * Added another variable parsed in the email, $PROJECT$. See sourcecode of insert_bug.aspx for how these work. * Changed all uses of @@IDENTITY in SQL to scope_identity(). * Added "PutTrackingIdStringInNotifications" to Web.config. This is related to the forum thread "TrackingIdString". http://sourceforge.net/forum/forum.php?thread_id=1676067&forum_id=226938 * Added support for RFE 1641374 "Automatically re-open an issue". See Web.config setting "StatusResultingFromIncomingEmail". ----------------------------------------------------------------------- Version 2.4.4 1/14/2007 ----------------------------------------------------------------------- Minor bug fixes only in this release. Fixed bug 1635411 "error when user is view only, and default perm lvl is 0". Fixed bug with bugs.aspx and $fullnames in SQL, in bugs.aspx Fixed bug with "[first]" link as discussed in Help forum topic "[last] / [first] link issue". Fixed problem with old sql in upgrade.sql as discussed in Help forum topic "Updgrade issues from v1.9.6 to v2.4.3" Fixed problem with custom user dropdowns as discussed in Help forum topic "User type custom col history shows user id" Fixed bug 1605280 "SSPI login fails if the user's full name contains ' [single quote]". I added "HtmlEncodeSql" setting in web.config. If you are having the problems described in these bugs, try setting it to 1 and let me know at ctrager@yahoo.com if it helps. 1590120 html encoding wrong for editing queries 1585740 "Saving Query does not allow < or > symbols?" You can now pass the user and password to default.aspx in the URL, like http://YOURHOST/default.aspx?user=admin&password=admin ----------------------------------------------------------------------- Version 2.4.3 11/19/2006 ----------------------------------------------------------------------- Minor fixes: * Fixed bug 1595637 "btnet 2.4.2, ToTable() doesn't compile in .NET 1.1" * Fixed bug 1597628 "Default search.aspx SQL doesn't work with UseFullNames" * Fixed crash on null when bug's fk to user defined attribute table, or something similar was pointing to a non-existent row. This happens if you delete a row in the status, permission, category, or user defined attribute table directly in SQL instead of going through the webpages. The webpages stop you from deleting rows if they are referenced by bugs. * I added a page "default_simple.aspx". Some folks have experienced the following symptom: They setup up BugTracker.NET and try to log in for the first time and after typing in the valid user/password the next page they see is still default.aspx, with no error message. If you are having this problem, try default_simple.aspx, and maybe that will work? ----------------------------------------------------------------------- Version 2.4.2 11/12/2006 ----------------------------------------------------------------------- For this upgrade, run these sql statements: alter table custom_col_metadata add ccm_sort_seq int default(0) alter table custom_col_metadata add ccm_dropdown_type varchar(20) null I changed Bug_list.js. Sometimes when I change javascript files folks report problems. The solution is to clear the browser cache so that the browser gets the latest file. * When adding a new bug, now displaying a project's default user before the bug has been added to the db. * Fixed bug where searching on text fields wasn't working with unicode. * There's now a new type of custom field, a "user" dropdown. It is populated with the same list of users as "assigned to". In other words, it follows the same permission rules. For those of you who wanted an "owner", in addition to the "assigned to", or something like that, I think this will work for you. * You can now specify what order custom fields appear on the screen. It used to be they displayed in the order that you created them. Now they display in the order that you arrange them. If you want more control over layout, use the custom css file. * The filters feature, the ones that you see in the column headings, has been enhanced. There are now filters for custom fields which are dropdowns, including the new "users" dropdown, the "User Defined Attribute", and the "reported by" and "assigned to" fields. * Custom columns are now automatically added as "SELECT" columns in the SQL being generated by the search page. In the past, they had been added to the search results, but not to the SQL you could see at the bottom of the page, that you could save as a query. * On the search page, custom columns which are dropdowns are presented as dropdowns that allow multiple selection, just like the built in fields like "category", etc. * On the search page, custom columns which are NOT dropdowns, which are presented as simple input fields now support multiple entries, seperated by commas. ----------------------------------------------------------------------- Version 2.4.1 10/28/2006 ----------------------------------------------------------------------- * Fixed bug 1583153 "Add New Bug" gives security warning using IE, this page contains both secure and nonsecure items. * Fixed bug 1583310 "Print Detail crashed tracker when bg_id isn't called 'id'" * Fixed bug 1584916 "Custom dropdown, first option not visible in IE" * Corrected HTML encoding in popups in bug list. * Added Web.config setting "SmtpUseSSL". If your SMTP provider requires SSL. Gmail, apparently, does. * Added Web.config setting "BugListFormSubmitMethod". Here's what I wrote in Web.config: "When navigating back to the bug list using the browser's "Back" button, do you get a warning "Warning: Page has Expired"? If so, try changing this from "POST" to "GET". But, if you get a javascript error when submitting the form around the line "theForm.submit()", then use "POST". GET can break if you are sending too much data back to the server - and ASP.NET's viewstate mechanism is kind of long." This change covers RFE 1583779 "back to the view page" ----------------------------------------------------------------------- Version 2.4.0 10/21/2006 ----------------------------------------------------------------------- You will need to run this SQL to upgrade to this release. create table custom_col_metadata ( ccm_colorder int not null, ccm_dropdown_vals nvarchar(1000) not null default('') ) create unique index cdv_index on custom_col_metadata (ccm_colorder) * Finally added ability to create as many dropdown custom fields as you want. Try the "admin" "custom fields" page. This change is related to these RFEs: 1578265 "custom listbox" 1063616 "CODE TO CREATE PICKLIST CUSTOM FIELD POSTED HERE" 1556453 "allow unlimited custom dropdowns - global or proj specific" * Made default values for custom fields actually work right. This was RFE 1017561 "Ability to create default value for custom fields". * Added "Presets" feature to edit_bug.asp. Set all 6 dropdowns with one click. * Adjusted copyright notice so as not to interfere with exporting to excel. * Fixed bug 1578303 "edit_self.aspx can't handle NULL in users.us_default_query" * When there were to many pages, the links to move from pages stretched across the page. Now showing thirty at a time. * Fixed bug 1014749 "CHNGING PRJCT: shouldn\'t be able to change to view only prj" * Fixed bug 1346170 "Bugs stranded if no Project assigned" * Fixed bug 1463935 "View only user should not be able to edit comments" * Fixed bug 1040849 "CHNGING PRJCT: bug_subscriptions not updated". ----------------------------------------------------------------------- Version 2.3.9 10/13/2006 ----------------------------------------------------------------------- * Fixed bug 1575345 "Datetime conversion error on bug updt (localization problem)". If your times use "." as a seperator instead of a ":", this will help you. * Related to above, corrected default "SQLServerDateFormat" in Web.config to "yyyyMMdd HH\:mm\:ss". * I revised Web.config comments based on info in 1239348 "CultureName comments in Web.config misleading regarding date". * Fixed bugs 1521559 "Search Page Too Wide With Long Custom Fields" and 1575969 "large custom field shows as "text", not "textarea" in search" * Fixed bug where a ">" in the sql saved as a query were saved as ">". * Fixed handling of single quotes in search.aspx in custom fields. * RFE 1575859 "custom link at post level, same as link at bug level" Jochen Jonckheere did the work and contributed a fun example that can translate a bug comment from one language to another. See the new "CustomPostLinkLabel" and "CustomPostLinkUrl" settings in Web.config. ----------------------------------------------------------------------- Version 2.3.8 10/11/2006 ----------------------------------------------------------------------- Just one big fix - for bug 1575066 "bugs.aspx not dispayed in IE". Sorry everybody. You can just edit your copies of bugs.aspx and search.aspx instead of downloading this version. Change this: