Menu
▾
▴
[xoops-cvs2] SF.net SVN: xoops: [800] XoopsCore/branches/2.0.x/2.0.16
|
From: <sk...@us...> - 2006-11-13 03:44:34
|
Revision: 800
http://svn.sourceforge.net/xoops/?rev=800&view=rev
Author: skalpa
Date: 2006-11-12 19:44:23 -0800 (Sun, 12 Nov 2006)
Log Message:
-----------
Updating the changelog and release notes for the 2.0.16 release
Modified Paths:
--------------
XoopsCore/branches/2.0.x/2.0.16/docs/changelog.txt
XoopsCore/branches/2.0.x/2.0.16/release_notes.txt
Modified: XoopsCore/branches/2.0.x/2.0.16/docs/changelog.txt
===================================================================
--- XoopsCore/branches/2.0.x/2.0.16/docs/changelog.txt 2006-11-08 02:55:49 UTC (rev 799)
+++ XoopsCore/branches/2.0.x/2.0.16/docs/changelog.txt 2006-11-13 03:44:23 UTC (rev 800)
@@ -2,7 +2,7 @@
XOOPS Changelog
============================
-XXXX/XX/XX: Version 2.0.16
+2006/11/12: Version 2.0.16
============================
- Fixed bug #1538291 : Mailer Return-Path header is not set correctly (skalpa/alienhand)
- Fixed bug #1548771 : Criteria doesn't handle IS NULL correctly (skalpa/garrath)
Modified: XoopsCore/branches/2.0.x/2.0.16/release_notes.txt
===================================================================
--- XoopsCore/branches/2.0.x/2.0.16/release_notes.txt 2006-11-08 02:55:49 UTC (rev 799)
+++ XoopsCore/branches/2.0.x/2.0.16/release_notes.txt 2006-11-13 03:44:23 UTC (rev 800)
@@ -1,20 +1,11 @@
-XOOPS 2.0.15 release notes (2006/08/24)
+XOOPS 2.0.15 release notes (2006/11/12)
------------------------------------------------------------------------------
-An up-to-date version of this document can be found at:
-http://devteam.xoops.org/releases/xoops-2.0.15.html
-The XOOPS development team is pleased to announce the release of XOOPS 2.0.15.
+The XOOPS development team is pleased to announce the release of XOOPS 2.0.16.
-This is mainly a maintenance release containing a lot of bugfixes. It also provides
-security enhancements and thus all 2.0.x users are strongly advised to upgrade.
+This is a maintenance release containing several bugfixes.
-What's new
- * Various bug fixes.
- * Several enhancements to XoopsForm, including a new ColorPicker element.
- * Magic ink support in the "blank page" to help webmasters diagnose problems more easily.
- * Experimental WYSIWYG editors support (see below)
-
Read the full changelog for details.
System requirements
@@ -42,29 +33,36 @@
Upgrading from a previous version
-----------------------------------
-Upgrading from XOOPS 2.0.14
+Upgrading from XOOPS 2.0.14/2.0.15 (easy way)
-If you downloaded the 2.0.14-to-2.0.15 upgrade package:
-- Just copy the content of the htdocs/ folder over your existing installation
+ 1. Get the appropriate update package from the sourceforge file repository
+ 2. Overwrite your existing files with the new ones
+ 3. Access <your.site.url>/upgrade/ with a browser
+ 4. Follow the instructions to update your database
+ 5. Delete the upgrade folder
-If you downloaded the complete 2.0.15 package:
-- Copy the content of the htdocs/ folder over your existing installation after having deleted
- "mainfile.php" and the "install" folder it contains
+Upgrading from XOOPS 2.0.14/2.0.15 (using the full package)
+ 1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs)
+ 2. Delete htdocs/mainfile.php, and htdocs/install
+ 3. Upload the content of the htdocs folder over your existing files
+ 4. Access <your.site.url>/upgrade/ with a browser
+ 5. Follow the instructions to update your database
+ 6. Delete the upgrade folder
-Upgrading from any XOOPS ranging 2.0.7 to 2.0.13.2:
- 1. Copy the content of the htdocs/ folder except mainfile.php over your existing installation.
- 2. Delete the following folders and files from your server (they belong to an old version):
+Upgrading from any XOOPS ranging from 2.0.7 to 2.0.13.2 (using the full package):
+ 1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs)
+ 2. Delete htdocs/mainfile.php, and htdocs/install
+ 3. Upload the content of the htdocs folder over your existing files
+ 4. Delete the following folders and files from your server (they belong to an old version):
* class/smarty/core
* class/smarty/plugins/resource.db.php
- 3. Empty the templates_c folder (except index.html)
- 4. Upload the upgrade folder to your site
- 5. Ensure the server can write to mainfile.php
- 6. Login using an administrator account
+ 5. Empty the templates_c folder (except index.html)
+ 6. Ensure the server can write to mainfile.php
7. Access <your.site.url>/upgrade/ using your browser, and follow the instructions
8. Write-protect mainfile.php again
9. Remove the upgrade folder after use
+ 10. Update the "system" module from the modules administration interface
-
Files integrity check
The full XOOPS package is now released with a script able to check if all the system files were correctly uploaded to the server. To use it, follow these instructions:
@@ -80,30 +78,20 @@
the cause of the error, this page contains additional messages that are hidden by default. To reveal them, use
your browser "select all" function (for most browsers, you can use "Ctrl+A").
-Experimental WYSIWYG support
+Unsupported templates access
-This version contains an experimental patch that allows the use of 3rd party WYSIWYG editors to replace the old
-"DHTML" one. Due to a lack of extended testing, this functionality has been disabled by default and requires that
-you modify one file manually to configure it.
+It has come to our knowledge that some modules contain a hacked version of the XOOPS module installation routine and access the templates/blocks database tables directly, bypassing the regular templates declaration mechanisms. Because of this, some recent changes in the templates handling system made those modules unable to access their template data.
+If you use one of these modules, you may fix this problem by replacing the resource.db.php file located in the class/smarty/xoops_plugins/ folder by the one provided in the package extras folder. Please note however that such bypassing of standard interfaces through the inclusion of hacked core parts is not supported and that those modules won't work with future versions.
-To enable it:
-- Edit the file class/xoopsform/formdhtmltextarea.php
-- Change the "htmlEditor" line, specifying the location of the editor you want to use.
- An example would be: var $htmlEditor = array( 'XoopsFormTinyeditorTextArea', '/class/xoopseditor/tinyeditor/formtinyeditortextarea.php' );
-
-To disable it:
-- Change the "htmlEditor" line back to its default value:
- var $htmlEditor = array();
-
Modules
The packages do not contain any module apart from the system one. You are invited to browse the XOOPS modules repository to get some.
Some of the best modules can be found in the following locations:
- * Herve Thouzard's site (News, mydownload, shortcuts...)
- * Panther Software Publishing (xProject, xAsset)
- * Smart Factory (SmartSection and many others)
- * XForge site (CBB forum, Wordpress, MediaWiki...)
+ * Herve Thouzard's site (News, mydownload, shortcuts... http://www.herve-thouzard.com/ )
+ * Panther Software Publishing (xProject, xStreamer, xAsset http://xprojects.co.uk/ )
+ * Smart Factory (SmartSection and many others http://www.smartfactory.ca/ )
+ * XForge site (CBB forum, Wordpress, MediaWiki... http://www.xoopsforge.com/ )
-We also highly recomment the installation of the Protector module which will bring additional protection and logging capabilities to your site.
+We also highly recommend the installation of the Protector module which will bring additional protection and logging capabilities to your site.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|