Template error clicking button to upload during online update
A template error in version 4.10.b1 can cause a "Template Error" to be displayed in some cases. This can be worked around by fixing the template. (A corrected template file is supplied with the next beta release.)
Right click and "Save Target As..." the file swupdate.tmpl. Save this file to a place where you can easily find it later, such as your desktop.
Open your FTP program. Navigate the "local" side to the directory where you saved the file, and the "remote" side to the Discus administration directory (typically discus_admin_xxxxxxxxx). Within the administration directory, change into "template" and then "admin".
Using ASCII mode, transfer the swupdate.tmpl file you downloaded from step 1, into the "admin" directory on your server as you navigated to in step 2.
Return to your Version Manager via the web interface and re-attempt the upgrade.
Internal Server Error accessing Version Manager
An "Internal Server Error" accessing Version Manager is a known issue with Discus 4.10.b1 and some Windows platforms that do not support the "alarm" function within perl. The following workaround should be used:
Log in to the discussion board as the board administrator (typically "admin") and go to Options Manager.
If you are in "Basic Mode" you will need to click the button to switch to "Advanced Mode" to continue.
Click the "Other" tab.
The bottommost option on this screen is entitled "Version Manager: Do not contact DiscusWare's server to determine current Discus version". Check this box and save your options.
Access Version Manager, and if the Internal Server Error is gone, click the "Update" tab to access the update process.
After updating to version 4.10.b2 or later, you should be able to undo steps 3-4 of this procedure, as the problem is believed to be fixed. Further internal server errors or other problems occurring after version 4.10.b2 should be reported to DiscusWare.
"update to the latest version" link produces error message
The link in the Version Manager under the text "update to the latest version" is mispointed in Discus 4.10.b1 and 4.10.b2. The intended destination is the same as for the "Update" tab at the top of the screen. Therefore, this simple workaround should be used:
If you experienced an error message clicking the link, use the browser's "Back" button to exit the error screen and return to the Version Manager screen.
Click the "Update" tab at the top of the screen.
update_receiver error (with complaint about differing file size, or directory parse error)
The automatic update process has certain safeguards to ensure that files are installed correctly, and corrupt files are rejected. We have discovered that on a small number of systems, the file size written to the disk may be different from the expected size, due to line endings. This problem is present in versions 4.10.b1 and 4.10.b2, and is resolved in version 4.10.b3. For customers with an affected version, the following workaround can be used to update:
Right click and "Save Target As..." the file swupdate.pl. Save this file to a place where you can easily find it later, such as your desktop.
Open your FTP program. Navigate the "local" side to the directory where you saved the file, and the "remote" side to the Discus administration directory (typically discus_admin_xxxxxxxxx). Within the administration directory is a subdirectory called "source" and you should navigate into this directory.
Using ASCII mode, transfer the swupdate.pl file you downloaded from step 1, into the "source" directory on your server as you navigated to in step 2.
Return to your Version Manager via the web interface and re-attempt the upgrade.
Other problems
Other problems, when confirmed and validated, will be added to this page. If you have encountered difficulty, please contact DiscusWare via one of the following methods:
Discus Professional customers with licenses under support: Please open a support case.
Discus Freeware customers, and Discus Professional customers whose licenses are no longer under support: Please post a message in the Support Forum.
|