41
skenow
Re: XOOPS 2.0.17.1 Final
  • 2007/9/29 12:10

  • skenow

  • Home away from home

  • Posts: 993

  • Since: 2004/11/17


Nope - I still don't get the message. But, if I do change the permissions on the folder to read-only, the message does appear.

Apache 2.2.4 (Windows)
PHP 5.2.1
MySQL 5.0.33

42
script_fu
Re: XOOPS 2.0.17.1 Final

Edit: Unrelated error to this topic.

43
irmtfan
Re: XOOPS 2.0.17.1 Final
  • 2007/9/29 16:39

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


script_fu:
do you check your mainfile.php? could you paste the content here just for test?

44
script_fu
Re: XOOPS 2.0.17.1 Final

Quote:

irmtfan wrote:
script_fu:
do you check your mainfile.php? could you paste the content here just for test?


If you want to see my mainfile all you half to do is download the XOOPS 2.0.17.1-rc package.

Its one in the same irmtfan.

If you think it will help... here you go!


// $Id: mainfile.dist.php 506 2006-05-26 23:10:37Z skalpa $
//  ------------------------------------------------------------------------ //
//                XOOPS - PHP Content Management System                      //
//                    Copyright (c) 2000 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
    // Example: define('XOOPS_ROOT_PATH', '/home/mydomain/public_html');
    
define('XOOPS_ROOT_PATH''/home/mydomain/public_html');

    
// XOOPS Virtual Path (URL)
    // Virtual path to your main XOOPS directory WITHOUT trailing slash
    // Example: define('XOOPS_URL', 'http://www.mydomain.com');
    
define('XOOPS_URL''http://www.mydomain.com');

    
define('XOOPS_CHECK_PATH'1);
    
// 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_replacestrpos$xoopsScriptPath'\\') ? '\\' DIRECTORY_SEPARATOR'/'$xoopsScriptPath);
        }
        if ( 
strcasecmpsubstr($xoopsScriptPath0strlen(XOOPS_ROOT_PATH)), str_replaceDIRECTORY_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''mydomain');

    
// 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''mydomain_mydomain');

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

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

    
// 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']) && XOOPS_ROOT_PATH != '') {
        include 
XOOPS_ROOT_PATH."/include/common.php";
    }
}
?>

45
irmtfan
Re: XOOPS 2.0.17.1 Final
  • 2007/9/29 17:03

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


yeah i just wanted to see if anything goes wrong through installation. because you install a fresh XOOPS and in a fresh install there is not a different except for "mainfile.php" and "environment". now we sure mainfile is correct somebody should try to reproduced from the same environment: ( php, mysql, apache,...)

also do you have the same result with 2.0.17.1 Final?

46
script_fu
Re: XOOPS 2.0.17.1 Final

I have not tryied 2.0.17.1 Final Yet. I dont belive the package contains anything different except the installer instructions. Also they changed the version number from 2.0.17.1-rc to 2.0.17.1

I could be wrong...

47
script_fu
Re: XOOPS 2.0.17.1 Final

Okay it's almost Sunday. One more full day to go... before 2.0.17.1 final...

bump...

ty...

Can we solve this - this weekend?

48
Chappy
Re: XOOPS 2.0.17.1 Final
  • 2007/9/30 3:24

  • Chappy

  • Friend of XOOPS

  • Posts: 456

  • Since: 2002/12/14


Just wanted to jump in here. This may, or may not help.

BUt, script_fu, you note that that is your mainfile.php. Is that the mainfile.php after your install or before?

After the install, it will not have the values you are noting in your previous reproduction of your mainfile.php:

define('XOOPS_ROOT_PATH''/home/mydomain/public_html');


The installation process edits the uploaded mainfile.php with the values that are unique to YOUR site. If - during the upgrade process - you replace the mainfile.php with the one from the package, you will kill your previous install.

The mainfile.php that you showed us previously is the stock mainfile.php that is intended to be overwritten. That is the reason that you set mainfile.php to have permissions 777 during the install process: so that the install process CAN overwrite mainfile.php.

Now, if you upgraded from an earlier install, and you uploaded and thereby overwrote the mainfile.php that was modified during the initial install, then XOOPS will simply not work.

Due to inattentiveness when upgrading, I have - on a number of occasions - overwritten my mainfile.php only to have similar kinds of headaches. Moreover, if you did overwrite it, you would need to set all the unique values in mainfile.php to the values unique to YOUR site. The values included in the file you posted are NOT going to be valid for your site.

What else leads me to wonder if this is what happened? Because of the following statement:

Quote:
If you want to see my mainfile all you half to do is download the XOOPS 2.0.17.1-rc package.

Its one in the same irmtfan.


Your mainfile.php (the one that you will have after your installation) will NOT be the same as the one in any of the packages. It will have different values.

Course of action IF I am correct?

1) Make certain mainfile.php is set with permissions at 777

2) Make sure the mainfile.php on your site reflects your sites unique values (eg. it will almost certainly not say the XOOPS_ROOT_PATH is /home/mydomain/public_html). Change the other values as well.

3) Reset Mainfile.php to 444

Just trying to help. I could be full of crap. But don't think I am. At least, that's what I would check...
MMM...It tastes like chicken! ...

49
script_fu
Re: XOOPS 2.0.17.1 Final

lol Chappy...

Okay this error has nothing to do with my mainfile. I only posted it because irmtfan wanted to see if it was truncated in some fashion.

I did edit the mainfile because it has my server info. Surly you don't want me to post that?

This error is php 5.2.4 related. If you do not have this version of php installed you will not have the problem I am.

When we upgraded our server all was fine untill 5.2.4

Xoops worked fine on 5.2.3 and below.

50
Dave_L
Re: XOOPS 2.0.17.1 Final
  • 2007/9/30 9:39

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


Billy, other than that error message, are there any functional problems? Should the release be delayed to resolve this, or is it just a "cosmetic" issue that can be ignored for now?

Login

Who's Online

228 user(s) are online (75 user(s) are browsing Support Forums)


Members: 0


Guests: 228


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