31
ViperSBT
Re: Upgrade to 2.0.14 went south
  • 2006/6/30 14:23

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I have tested that the webserver will generate and report errors by testing some small scripts of my own. But still not getting anything from XOOPS but the blank page.

I have reviewed the mainfile.php and cleaned it up to resemble the dist.php. Basically this involved removing old protector script that was added to mainfile. But still not getting anything.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



32
ViperSBT
Re: Upgrade to 2.0.14 went south
  • 2006/6/30 13:46

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I've completely gone through the system and re-CHMODed all files and directories to appropriate settings, still nothing.

I've disabled all modules, still nothing.

I tried going to user.php and was redirected to userinfo.php?uid=3 but the page was still blank and no errors were generated.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



33
ViperSBT
Re: Upgrade to 2.0.14 went south
  • 2006/6/30 13:14

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I have turned on Register-Globals which did nothing.

I made sure the cache directory was properly CHMODed. While looking in the cache directory I noted that there was a backend.php cache. I executed the backend.php script and it displayed properly.

Uploaded and changed back to phpkaox theme to see if it was a theme problem and still nothing.

Made sure that the cache, uploads, templates_c directories are CHMOD 777, still nothing.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



34
ViperSBT
Re: Upgrade to 2.0.14 went south
  • 2006/6/30 12:57

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I have gone into recovery.php and set debugging to 1 and still not getting any additional errors that are showing what is the problem. As backup insurance I edited common.php to for error reporting to E_ALL, and still not getting any errors either on screen on in my phperror.log.

I then checked my php.ini settings. I had Display_Errors = Off, but I was using Error_Logging. So just to follow the FAQs I enabled Display_Errors and restarted Apache, still nothing.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



35
ViperSBT
Upgrade to 2.0.14 went south
  • 2006/6/30 7:05

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Upgraded from 2.0.13 to 2.0.14, went through all the steps and everything appears to have gone normal, but when I go to the site everything is blank. I am not getting any errors that I can identify, but all the pages come up blank. If I force it to admin.php it takes me there and allows me to login with my password.

All of the preferences links show nothing or send me back to the previous screen. The rest of the admin section appears to work normally... What gives?

PHP 4.4.1
Apache 2.0.54
MySQL 4.1.16
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



36
ViperSBT
Re: Protector: Warnings & Notices
  • 2005/12/28 18:20

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Thanks, that was it.. Upgraded to the new version, problem solved...
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



37
ViperSBT
Protector: Warnings & Notices
  • 2005/12/28 17:09

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Well I got my site up and running, but when I went to look at my error log I found the following:
Quote:
[28-Dec-2005 10:03:04] PHP Notice: unserialize(): Error at offset 9 of 50 bytes in /home/.../modules/protector/include/precheck.inc.php on line 44
[28-Dec-2005 10:03:04] PHP Warning: Invalid argument supplied for foreach() in /home/.../modules/protector/include/precheck.inc.php on line 46

There are thousands of these... They appear to be coming up each time a user visits a page, but I can't be totally sure it is EVERY time a user visits a page.

Is this normal operation for protector, or do I have something configured wrong?
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



38
ViperSBT
Re: Custom Blocks weird behavior
  • 2005/12/20 16:48

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


OK, I figured out the problem and am documenting it here in the hopes that it may help others out in the future. When I moved to my new server I thought I would make things cleaner by simply having a single user that would have access to my XOOPS DB and my statistics DB. On my old server these were two seperate users.

So I created a new user for the statistics DB, updated my config.php to reflect the new user and password. Everything is working fine! No changes to any of my PHP code were needed.

So why was this a problem? My best guess has to do with when you create a new DB select it maintains that select for all future queries and there must be a query after the blocks that was not able to execute properly since I had a new DB selection. If anyone can better explain this, I would love to understand it better.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



39
ViperSBT
Re: Custom Blocks weird behavior
  • 2005/12/20 16:19

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Yes, the constants are being controlled from the config.php file.

Changing the DB select to
Quote:
mysql_select_db(SQL_DB);

creates the same problem.

I did not mention in my original post that there is one error that I am getting that changes based upon the module I have assigned to the start page. Currently I have News assigned as that module and am getting the following error:
Quote:

Fatal error: Call to a member function on a non-object in /home/httpd/vhosts/ufli/include/notification_functions.php on line 95


Now this module works fine on its own, it works fine as the start page module when my custom blocks are not set to visible, and it worked fine on the old server with the custom blocks, so I am pretty sure it isn't the modules fault.

The blocks work fine on their own, and they work find on the start page if I have no modules set for the front page. It is only when combining modules with these blocks that I am getting a problem.

Specifying the absolute path made no difference either. I have checked to verify that all the constants are being loaded and they are.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com



40
ViperSBT
Custom Blocks weird behavior
  • 2005/12/20 0:57

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


OK, after migrating my site to a new environment I am now experiencing something really weird with any of my custom blocks that are .php files using an include function. Here is a snippet of one of the files (they all start out this way):
Quote:
<?
require('config.php');

// Connects to the database
$conn = mysql_connect(SQL_HOST, SQL_USER, SQL_PASS) or die(mysql_error());
mysql_select_db(SQL_DB,$conn);


The problem seems to be with the
Quote:
mysql_select_db(SQL_DB,$conn);
with it there (which it has to be) I get a blank page. If I comment that single line out, XOOPS works normally, but I am not connecting to my DB to pull any data... There are no errors being shown, if I turn on debugging I don't get anything besides the normal Notices.

I am using XOOPS 2.2.3 Final. The block is set to PHP Script and has a single line of:
Quote:
include XOOPS_ROOT_PATH.'/blockname.php';
and the template is:
Quote:
<{$block.content}>
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com




TopTop
« 1 2 3 (4) 5 6 7 ... 9 »



Login

Who's Online

253 user(s) are online (176 user(s) are browsing Support Forums)


Members: 0


Guests: 253


more...

Donat-O-Meter

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

Latest GitHub Commits