| Bookmark this article at these sites |
|---|
|
!!!!!
great. thx a lot there a 2.0.13.2 to 2.0.14 update package?
Due to a switch to the Subversion version control system since the release of XOOPS 2.0.13.2, there will be no 2.0.14 incremental upgrade packages released, to ensure both fresh installs and upgraded systems contain the exact same set of files.
tnx to core team
This page cannot be displayed due to an internal error.
If you are the administrator of this site, please visit the XOOPS Troubleshooting Page for assistance.
![Open in new window](javascript:CaricaFoto("http://members.lycos.nl/mcdonaldsstore/smilies/worshippy.gif");)
./class/mail/xoopsmultimailer.php content invalid
(xoops.md5=b7c27c5085d16e14265b96d33e9a6de9 ; myValue=def2d9befd173f0bf91ad5c8159fec59)
./class/xml/rpc/xmlrpcparser.php content invalid
(xoops.md5=065845bf8d0c0dae725585745dd50a85 ; myValue=091cbbbcad5ebf5464a03c5c222967bd)
./kernel/privmessage.php content invalid
(xoops.md5=86afd71e8786c9b00e1d4206dff38820 ; myValue=1ff46f567517d068f9bf6a3e34fa252b)
The 2006/05/23 security patch has been released to fix the security issue disclosed as Secunia Advisory 20176.
Upgrading from 2.0.14-RC1
If you had previously upgraded from a previous version to 2.0.14-RC1 without applying the 2006/05/23 security patch or were unable to access the authentication preferences panel, follow the above upgrade instructions to ensure the patch gets applied and the authentication related values are inserted into the database.
If you upgrade from a 2.0.14-RC1 installation with the patch installed, you just need to copy the content of the htdocs/ folder except mainfile.php over your existing installation.
You can see how to install/upgrade at http://devteam.xoops.org/releases/xoops-2.0.14.html
Due to a switch to the Subversion version control system since the release of XOOPS 2.0.13.2, there will be no 2.0.14 incremental upgrade packages released, to ensure both fresh installs and upgraded systems contain the exact same set of file. We apologize for this inconvenience. You may want to use the newly provided checksum verification script to ensure there was no problem during the files upload (see instructions below).
Upgrading from any XOOPS version between 2.0.10 and 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:
* 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
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
- Several constants changed in modules/system/admin/preferences (_MD_AM_DEBUGMODE1,_MD_AM_DEBUGMODE2,_MD_AM_THEMEFILE,_MD_AM_THEMEFILEDSC)
- Added 3 new constants to the modules/system/admin/blocksadmin (_AM_CBBOTTOM, _AM_CBBOTTOMLEFT, _AM_CBBOTTOMRIGHT)
- Added one constant to language/english/comment.php (_CM_RE)
- And about 40 new constants added to modules/system/admin/preferences.php
(starting on line 183 with)
// XOOPS Authentication constants
...
Due to a switch to the Subversion version control system since the release of XOOPS 2.0.13.2, there will be no 2.0.14 incremental upgrade packages released, to ensure both fresh installs and upgraded systems contain the exact same set of files
Changes for translators:
- Added 3 new constants to the system/admin/blocksadmin (_AM_CBBOTTOM, _AM_CBBOTTOMLEFT, _AM_CBBOTTOMRIGHT)
- Several constants changed in system/admin/preferences (_MD_AM_DEBUGMODE1,_MD_AM_DEBUGMODE2,_MD_AM_THEMEFILE,_MD_AM_THEMEFILEDSC)
- Added one constant to language/english/comment.php (_CM_RE)
ZPC:
@fbs777:
OK, again and more precisely
- Several constants changed and 40 new added to
/modules/system/language/english/admin/preferences.php
- Added 3 new constants to
/modules/system/language/english/admin/blocksadmin.php
- Added one constant to
/language/english/comment.php
Is it clear enough now?
Fatal error: Call to undefined method XoopsErrorHandler::getinstance() in /....../...../public_html/portal/include/common.php on line 39
Our goal is to try to make some releases without bugs at all, so the more you report this and use the beta/RCs, the more we can fix bugs.
Poster: skalpa Posted: 2006/6/28 23:10:17
@max: From now on all next releases will contain an upgrade script for both 2.0 and 2.2 users.
We know how the situation can be and are trying to make the best choices to ensure it ends as soon as possible (next weeks dev will be focused on that).
Poster: m0nty Posted: 2006/6/28 23:22:52
even tho those using 2.2.x version were told hundreds of times to use 2.0.x
Poster: m0nty Posted: 2006/6/28 23:22:52
2.2.4 users wait for 2.4..
Poster: m0nty Posted: 2006/6/28 23:22:52
2.0 and 2.2 are different.
(...)However they didn't discover anything, they just put another name on something else (the same applies to AJAX in fact: the emergence of these terms are just the symptoms of a society that has become so stupid and uncreative that it tries to disguize recycling into progress).
Honestly, wouldn't it be preferable to have that new code into a new branch/project rather than to sew the new fabric with the old one?
a society that has become so stupid and uncreative that it tries to disguize recycling into progress
(...) we intend to share more and more ideas in the future to ensure both XOOPS and xcube users can benefit from our thinking (...)
- tweaks were in module and template files rather than system files. I presume these will not need to change... Guess I'll just have to try it and see, eh?
NOTE ABOUT CHARSETS
This file uses the UTF-8 charset. If you use this file in a server with english language support, consider replacing the following directives:
file language/english/global.php:
< define('_CHARSET', 'ISO-8859-1');
> define('_CHARSET', 'UTF-8');
< define("XOOPS_USE_MULTIBYTES", "0");
> define("XOOPS_USE_MULTIBYTES", "1");
(< means the old value, and > means the new one)
$xoopsTpl->assign('xoops_module_header', '<meta http-equiv="Refresh" content="'.$time.'; url='.$url.'" />');
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=<{$xoops_charset}>" />
<meta http-equiv="Refresh" content="<{$time}>; url=<{$url}>" />
<title><{$xoops_sitename}></title>
how to downgrade from 2.2.x to 2.0.14?!:)
Some of the Smart factory modules even lack english texts and are unusable due to that and the complete absence of documentation.
Thanks for being too lazy to include some default modules.
This was annoying in 2.2 and now you adapted it for 2.0.14. Thanks a lot.
Devs spent entire days or even weeks working on this, and you're talking about lazyness coz spend 1/2 hour on something is too much for you...I am really frustrated because I had to search for a simple links module for hours now
like a sport that wouldn't require too much strategy.
There are also some bundles based on what kind of site at this link
Click on "module repository" on the left, there's a "weblinks" category right in front of you. That's 30 seconds...
News download:
...
Oh... and did you notice? The language files are located under "Documentation"... my heaven... a clear structure must be really soooo difficult to set up...
Mostly it was because of your method of wording, which was slightly offensive
Not as people are "lazy" - but as people don't get enough time to check everything unfortunately
). However, up to XOOPS 2.0.13 this was always one of the big advantages that XOOPS had: It ran straight out of the box. I would like to see XOOPS back on that track.
