I do have some general errors that now show, these show on my home page:

Errors
Notice: Undefined index: query in file /modules/statistics/include/hitcounter.php line 64
Notice: Undefined index: fragment in file /modules/statistics/include/hitcounter.php line 68
Notice: Undefined offset: 14 in file /modules/news/blocks/news_top.php line 345
Notice: Undefined variable: showselfrefer in file /modules/statistics/blocks/referaccum.php line 54
Warning: MyTextSanitizer::makeTboxData4Show is deprecated in file /class/module.textsanitizer.php line 665
Warning: MyTextSanitizer::makeTboxData4Show is deprecated in file /class/module.textsanitizer.php line 665
Warning: MyTextSanitizer::makeTboxData4Show is deprecated in file /class/module.textsanitizer.php line 665
Warning: MyTextSanitizer::makeTboxData4Show is deprecated in file /class/module.textsanitizer.php line 665
Warning: MyTextSanitizer::makeTboxData4Show is deprecated in file /class/module.textsanitizer.php line 665
Warning: MyTextSanitizer::makeTboxData4Show is deprecated in file /class/module.textsanitizer.php line 665

And these three show on the profile page:

Errors
Notice: Undefined index: query in file /modules/statistics/include/hitcounter.php line 64
Notice: Undefined index: fragment in file /modules/statistics/include/hitcounter.php line 68
Notice: Undefined variable: showselfrefer in file /modules/statistics/blocks/referaccum.php line 54

The only change is the statistics module required an edit to header.php

Incidentally not overly enthused with this statistics module and if it is a problem I can lose it. Although I like integrated stats. Any recommendations on XOOPS statistics modules?

Ken

Quote:

OK well here is something interesting, as admin I cannot see the admin profile. Then when I try to see another user, blank page that tries to redirect to the legacy site. See here is the thing, the new site is not being pointed to by the DNS, yet, so I am testing by connecting to the IP address directly. The DNS for now points to the legacy site which is closed and of course is 2.0.15 so it does not have a modules/profile out there.

That being said I might have to wait to solve this for when I change the DNS. Maybe that in itself will solve it. On a side note in the mainfile I do have the XOOPS url as the ip address on the new site.

Honestly I can go live with it being a little flakey, but I can't leave it like that long.

Oh and as to the other question, English yes.

Ken

Quote:

In no particular order (these are all active, I have a few inactive ones as well):

System - Upgraded
Profile - Upgraded
Priv Msg - Upgraded
Protector - Upgraded

News
NewBB/CBB 3
catads
piCal
*Liaise
addresses
xoops faq
myreviews
*statistics

The two I starred have been installed recently and the fact is the profile was not working before I installed them.

Since seeing module incompatibility issues posted here I did deactivate the following:

xoopspoll
phpMyAdmin
Net2FTP
randomquote
downloads

I also have several that are in the modules directory but not installed:

sections
partners
links
xoopsmembers
xoopsheadline

That about covers it. Other information, I noticed here on Xoops.org the user.php file redirects to modules/profile/user.php, mine redirected to userinfo.php under the site root, I changed that in the code and that still did not resolve the issue. I have also tried navigating to modules/profile and that also produces a blank page with no errors.

Oh and in case it is relevant:
XOOPS Version - XOOPS 2.3.3
PHP Version - 5.2.9
MySQL Version - 5.0.77-log
Server API Version - apache2handler
OS Version - Linux (CentOS 5)

safe_mode - Off
register_globals - Off
magic_quotes_gpc - Off
allow_url_fopen - On
fsockopen - On
allow_call_time_pass_reference - Off
post_max_size - 8M
max_input_time - 60
output_buffering - 4096
max_execution_time - 30
memory_limit - 32M
file_uploads - On
upload_max_filesize - 2M

And the machine I am connecting on is an Aspire One running Foresight Linux and Firefox 3.0.3

Ken

Sorry to bump so soon but I need help. user.php and userinfo.php are blank with NO errors. Edit User works but not view user. With no errors and no past posts that I can find dealing with a no error blank page here I am stuck. Looking to bring the site back up today, please advise.

Ken

I just upgraded from 2.0.15 to 2.3.3
my userinfo.php even as admin is blank, debug mode shows no errors.

not sure where to go from here, please help.

Ken

Quote:

I did not think of that.

Tough decision here. OK then here is what I would suggest. Incidentally core impact matters to me just for the sake of tracking components when I do FTP upgrades. It always seems to be the breaking point when I do an install or upgrade.

Anyway suggestions. There should be two different installs. Expert and Bundle. Expert would be just the core and maybe ONE editor (Koivi, the lightest). If not maybe no editor. This would be for people who are well versed in XOOPS Installation. The Bundle package would be the install as it is now with maybe a few basic pieces people would consider necessary for a basic page creation tool. AMS for example. Something like that.

Just brainstorming outloud.

OK since I am finally back to work on this site, I need to go figure out why my install is not working so off to that forum. On a side note once I get past the deadlines I have this month, I would be willing to do some doc work for Xoops. From what I am gathering some Quick start guides might be useful. From Zero to XOOPS blog in 3,2,1 or something like that. Etc etc. If that is something that could be useful I will look into it.

Ken

Well this weekend I was working on test 1 of upgrading a 2.0.15 XOOPS site I have to 2.3.1. At the same time I also did a new install of 2.3.1 to use as comparison to see if something that should have happened in my upgrade did not.

After everything the upgrade site is now running although there are obviously some theme and template issues. The new install is not and I can't get to admin to turn on debug (I know how to do it in MySQL and if I have problems that will go in that forum).

Anyway the reason I write all this is that during the new install a lot of files did not transfer as indicated by checksum.php. Seems an old FileZilla bug has arisen that was supposedly fixed. So I went about fixing all those problems to try and repair the fresh install. I also noticed the huge file scope of the system now. So I did a compare. Looking at the old 2.0.15 htdocs folder I see about 600+ files with a total size of around 3 megs. I look at the same folder in 2.3.1 and I see now a file count of 3,000+ and a disk usage space near about 10 megs.

This seems just a massive increase, a 4 fold increase, that does not represent 4 fold value added to the end user. And that is without any modules or module packs added. This is a huge file/server impact for the baseline core in my opinion and I think something should be mentioned to the developers about it. It seems to me it could be slimmer. Granted that is not a programmatic analysis of the file scope, just an uneducated guess.

Also I have found that the installer although "prettier" seems a little less logical than it used to be. For one I think the DB configuration pages (2) should be merged to 1 page. There is easily the screen real estate and I think it makes things cleaner in the logic sense. Also there seems to be a lot of manual steps that would turn off the more timid users.

I think these are significant, one of the reasons I used to always choose XOOPS over Drupal were reasons that are disappearing. First of all I have found Drupal and XOOPS to be equal on the file impact I am talking about, until 2.3.1 that is. Both came just about empty allowing you to add just what you needed. The advantage XOOPS has had were the easier install and better admin for non-tech users. Also I alway felt that out of the box XOOPS had more professional looking modules, and that one heck of a site could be made with less coding knowledge.

However now at this point XOOPS has far exceeded Drupal in core size and is becoming just as complicated to install and upgrade. The file impact becomes a bigger deal when you compare Drupals multisite feature.

I am not trying to turn this into a Drupal vs XOOPS discussion. I am trying to mention that I think these areas are things XOOPS developers could look into for improving XOOPS over all. That is all.

Anyway I hope this doesn't start a flame war, I know I haven't posted in here in a while but I have been keeping up to speed as much as I can with one of my biggest sites being a XOOPS site, www.raleighmusic.com.

Anyway just some opinions from lowly old me!

Ken

I got this same error upgrading our test site from 2.0.15 to 2.0.16. We don't have articles installed. If I put the mainfile from the clean 2.0.16 install in the install comes up but when I put our existing mainfile in there and go anywhere (including the upgrade directory so I can finish the upgrade I get this error).

OK got to my work computer this morning to test and it works fine. I can only wager it is some type of problem with the cache on my home desktop. Please ignore this question as the answer is obviously not XOOPS or even web programming related.

Ken

OK I think I have answered my own question. I think TinyD is the way to go on this. WF-Channel would work as well so I am still debating them. The reason I am going with TinyD right now is it is very easy to create multiple TinyD installs if I want to use TinyD for another area where I want the full portal menus. Hope this helps someone looking for a similar setup.

Ken