 |
|
|
Search this site!
|
 |
 |
|
Bug fixes addressed with CSB 4.0
|
Globalscape has provided the following partial list
of internal changes and bug fixes addressed in version 4.0:
|
1. When publishing a site using the new FTP Publishing Wizard, if the user has trailing spaces in the FTP path, the system fails to publish because the path with the space does not exist. Copying often picks up a trailing space (using the "smart select" of windows) and pasting would result in this error. RESOLUTION: Trim trailing spaces on this screen.
2. Incorrect product name shown in Web page source.
3. When site is published, pages with empty description property (of page) get default content that will show up in some search engines.
4. Image tags are not being dropped into document upon publish.
5. Anchors work properly when viewed from CSB, however anchors does not work properly when published
6. CSB will not publish a new index.html if there is an index.html present on the FTP you are publishing to
7. Transparency options are not handled properly - Fix - modified ImagePropSheet to not display transparency property page when image is of type Animated GIF.
8. Max image size is now 3600 x 3600
9. Cannot display status information or thumbnail in Insert Image dialog when viewing some very large EXIF JPG images. Fix - Updated Pegasus dispatcher with latest version from Pegasus. Increased size of buffer initially read from image when getting status information.
10. When you right-click in the page area and choose Properties > Page Area, one of the tabs there is 'Edge'. This will create a border in "edit" mode, but it will not appear when published. Added note to Edge screen that the border will not appear when published.
11. When inserting a video file, a Windows 'Open' dialog appears before the user can choose to browse for a file or link to a URL.
---
Additional findings:
1. At least on Windows XP, if you used <PrintScreen> to copy an active Window into the clipboard memory, and then tried to paste it into CSB3, you would get an error message. That appears to work better.
2. Again with Windows XP, after exiting CSB3, if you were to open up your Task Manager, often you would find one or more copies of csb.exe still running on your system, using up processor and memory. This appears to have been fixed with CSB4.
|