1
Jackwan
Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/24 17:20

  • Jackwan

  • Not too shy to talk

  • Posts: 129

  • Since: 2004/9/8 2


I uploaded the files to the server and when I executed the /upgrade/ I got the following error message

Quote:
This page cannot be displayed due to an internal error.

You can provide the following information to the administrators of this site to help them solve the problem:

Error: Smarty error: the $compile_dir 'XOOPS_VAR_PATH/caches/smarty_compile' does not exist, or is not a directory.



I checked the smarty subdirectories and they are there and the attributes are set to 777

Help

2
badcase
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/24 22:09

  • badcase

  • Just popping in

  • Posts: 17

  • Since: 2007/3/1 1


the variable XOOPS_VAR_PATH is not set, it is normally stored in mainfile.php, are you sure you followed all steps of the upgrade instructions?

3
Jackwan
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 0:08

  • Jackwan

  • Not too shy to talk

  • Posts: 129

  • Since: 2004/9/8 2


I believe that I did it to the letter.

right now htdoc/ does not have the mainfile.php. The mainfile.php on the server has been set to 777 and it had a different date from today's upload.

here is the current mainfile.php

Quote:

// $Id: mainfile.dist.php,v 1.6 2004/06/16 23:07:42 skalpa Exp $
// ------------------------------------------------------------------------ //
// XOOPS - PHP Content Management System //
// Copyright (c) 2000 XOOPS.org //
// <https://xoops.org/> //
// ------------------------------------------------------------------------ //
// This program is free software; you can redistribute it and/or modify //
// it under the terms of the GNU General Public License as published by //
// the Free Software Foundation; either version 2 of the License, or //
// (at your option) any later version. //
// //
// You may not change or alter any portion of this comment or credits //
// of supporting developers from this source code or any supporting //
// source code which is considered copyrighted (c) material of the //
// original comment or credit authors. //
// //
// This program is distributed in the hope that it will be useful, //
// but WITHOUT ANY WARRANTY; without even the implied warranty of //
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the //
// GNU General Public License for more details. //
// //
// You should have received a copy of the GNU General Public License //
// along with this program; if not, write to the Free Software //
// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA //
// ------------------------------------------------------------------------ //

if ( !defined("XOOPS_MAINFILE_INCLUDED") ) {
define("XOOPS_MAINFILE_INCLUDED",1);

// XOOPS Physical Path
// Physical path to your main XOOPS directory WITHOUT trailing slash
define('XOOPS_ROOT_PATH', '/home/twkince/public_html');

// XOOPS Virtual Path (URL)
// Virtual path to your main XOOPS directory WITHOUT trailing slash
// define('XOOPS_URL', 'http://66.xxx.xxx.xxx/~yyyyyyy/credata/');
define('XOOPS_URL', 'http://www.creforum.net');

define('XOOPS_CHECK_PATH', 0);
// Protect against external scripts execution if safe mode is not enabled
if ( XOOPS_CHECK_PATH && !@ini_get('safe_mode') ) {
if ( function_exists('debug_backtrace') ) {
$xoopsScriptPath = debug_backtrace();
if ( !count($xoopsScriptPath) ) {
die("XOOPS path check: this file cannot be requested directly");
}
$xoopsScriptPath = $xoopsScriptPath[0]['file'];
} else {
$xoopsScriptPath = isset($_SERVER['PATH_TRANSLATED']) ? $_SERVER['PATH_TRANSLATED'] : $_SERVER['SCRIPT_FILENAME'];
}
if ( DIRECTORY_SEPARATOR != '/' ) {
// IIS6 may double the \ chars
$xoopsScriptPath = str_replace( strpos( $xoopsScriptPath, '\\\\', 2 ) ? '\\\\' : DIRECTORY_SEPARATOR, '/', $xoopsScriptPath);
}
if ( strcasecmp( substr($xoopsScriptPath, 0, strlen(XOOPS_ROOT_PATH)), str_replace( DIRECTORY_SEPARATOR, '/', XOOPS_ROOT_PATH)) ) {
exit("XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.");
}
}

// Database
// Choose the database to be used
define('XOOPS_DB_TYPE', 'mysql');

// Table Prefix
// This prefix will be added to all new tables created to avoid name conflict in the database. If you are unsure, just use the default 'xoops'.
define('XOOPS_DB_PREFIX', 'xoops');

// Database Hostname
// Hostname of the database server. If you are unsure, 'localhost' works in most cases.
define('XOOPS_DB_HOST', 'localhost');

// Database Username
// Your database user account on the host
define('XOOPS_DB_USER', '');

// Database Password
// Password for your database user account
define('XOOPS_DB_PASS', '');

// Database Name
// The name of database on the host. The installer will attempt to create the database if not exist
define('XOOPS_DB_NAME', '');

// Use persistent connection? (Yes=1 No=0)
// Default is 'Yes'. Choose 'Yes' if you are unsure.
define('XOOPS_DB_PCONNECT', 0);

define('XOOPS_GROUP_ADMIN', '1');
define('XOOPS_GROUP_USERS', '2');
define('XOOPS_GROUP_ANONYMOUS', '3');


foreach ( array('GLOBALS', '_SESSION', 'HTTP_SESSION_VARS', '_GET', 'HTTP_GET_VARS', '_POST', 'HTTP_POST_VARS', '_COOKIE', 'HTTP_COOKIE_VARS', '_REQUEST', '_SERVER', 'HTTP_SERVER_VARS', '_ENV', 'HTTP_ENV_VARS', '_FILES', 'HTTP_POST_FILES', 'xoopsDB', 'xoopsUser', 'xoopsUserId', 'xoopsUserGroups', 'xoopsUserIsAdmin', 'xoopsConfig', 'xoopsOption', 'xoopsModule', 'xoopsModuleConfig', 'xoopsRequestUri') as $bad_global ) {
if ( isset( $_REQUEST[$bad_global] ) ) {
header( 'Location: '.XOOPS_URL.'/' );
exit();
}
}
if (!isset($xoopsOption['nocommon'])) {
include XOOPS_ROOT_PATH."/include/common.php";
}
}
?>


4
Jackwan
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 0:26

  • Jackwan

  • Not too shy to talk

  • Posts: 129

  • Since: 2004/9/8 2


btw, in the include/common.php the xoops_var_path is set to null.

5
dbman
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 0:33

  • dbman

  • Friend of XOOPS

  • Posts: 172

  • Since: 2005/4/28


You should see something like this in your mainfile.php
define'XOOPS_VAR_PATH''/some/path/outside/web' );


Also you should set the mainfile to 444 permissions ASAP. You don't need to change anything in the common.php file.

6
Jackwan
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 0:50

  • Jackwan

  • Not too shy to talk

  • Posts: 129

  • Since: 2004/9/8 2


sorry, I have searched the entire file and the xoops_var_path is not there. this mainfile.php was used by 2.0.18 should I use the new one from the download? per instruction the 2nd step is to delete mailfile.php from the distributed download.

7
dbman
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 1:01

  • dbman

  • Friend of XOOPS

  • Posts: 172

  • Since: 2005/4/28


Normally the install script will write the necessary changes to the mainfile.php assuming the file was writable at the time of upgrade (777).

If you have a backup of the site I would say you could replace the mainfile.php with the copy from the XOOPS distribution you upgraded with.

The instructions for upgrade would have stated to remove the mainfile.php when upgrading so you'll likely have to unpack the XOOPS archive file again to retrieve it.

Make the changes where necessary in the mainfile.php and add to your web directory. You should also clear your cache folders in the xoops_data directory. Don't forget to set the mainfile permissions to 444.


8
Jackwan
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 3:25

  • Jackwan

  • Not too shy to talk

  • Posts: 129

  • Since: 2004/9/8 2


I've checked the mainfile.php from the download, as you said, it requires to run the install.

Quote:
If you have a backup of the site I would say you could replace the mainfile.php with the copy from the XOOPS distribution you upgraded with.


I do have the mainfile.php from the 2.0.18 and have post it in the above message. In that mainfile.php, there is no reference to Xoops_var_path variable. So, where can I find a mainfile.php that has one?

9
dbman
Re: Upgrade from 2.0.18 to 2.3.3 help
  • 2009/8/25 4:48

  • dbman

  • Friend of XOOPS

  • Posts: 172

  • Since: 2005/4/28


If you have a backup you could roll back to your 2.0.18 version and try the upgrade again. You could also try re-uploading the upgrade files over the existing installation. Complete the upgrade as described in the directions here.

Check out the section of the installation/upgrade procedure in the article under this section:
Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.* (using the full package)


If you have protector installed read a couple of paragraphs above regarding necessary file placement to upgrade it.

10
iHackCode
Re: Upgrade from 2.0.18 to 2.3.3 help

i have a post on my blog with screenshots describing the update process. it could be useful.

http://blog.bandit-x.net/2008/09/upda ... e-to-xoops-230-final.html

Login

Who's Online

46 user(s) are online (35 user(s) are browsing Support Forums)


Members: 0


Guests: 46


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Oct 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits