Hello,

first, this post will get a bit longer. Please take the time to read it all, especially if you're a XOOPS core developer.
I hope you understand it all. I'm a german user and not all the time perfect with my english.

It seems to me, that the upgrade procedure from 2.0.13 up to 2.2 don't work.
I'm sitting here for hours on my testmachine to find out the reason why the update to 2.2 don't work for my website.
Now I've stopped to look inside of my current production website and tried an upgrade with a fresh install of 2.0.13 and it ends in the same problems.
I've checked the forum here on xoops.org and found several people with similar problems but with no solution to me.

Oh, I forgot to explain what the problems are. Here it comes.
After the xoopsupdate.php scripe I've got "error.php?c=XOOPS_REFERER_BLOCKED" in my URL, the header of the page and nothing more.

Ok, please let me take you all to the following steps of my update procedure and maybe some of you can explain me what I'm doing wrong.

My testsystem based on a BigApache installation under Windows-XP Pro.

First step is installing a fresh installation of 2.0.13.
I copied all the files to X:\www\xoops.
I call a browser and open the urlhttp://localhost:85/xoops
The installation wizards starts and I follow all the instructions as I have done about 100 times in my live.
A minute later I got a running 2.0.13 installation with no acitve modules. All seems ok and I removed the install directory and write protect the mainfile.php.

Now, without doing any more, it's time for update to 2.2.
From the 2.0.13->2.2 update package I copied all files under html into my installation on X:\www\xoops.
Next I call the xoopsupdate.php.
Ok, I see a screen with a missing picture in the upper left (Home Page) and a submit button.
At the end of the screen I see some messages with notice and warnings.

Maybe interesting are the warnings:

Warning [PHP]: in_array(): Wrong datatype for second argument in file X:\www\xoops\include\common.php line 235
Warning [PHP]: in_array(): Wrong datatype for second argument in file X:\www\xoops\class\theme.php line 448
Warning [PHP]: main(X:/www/xoops/language//notification.php): failed to open stream: No such file or directory in file X:\www\xoops\modules\system\xoops_version.php line 215
Warning [PHP]: main(): Failed opening 'X:/www/xoops/language//notification.php' for inclusion (include_path='.;\usr\local\PHP\includes;x:/www/mambo45') in file X:\www\xoops\modules\system\xoops_version.php line 215
Warning [PHP]: in_array(): Wrong datatype for second argument in file X:\www\xoops\footer.php line 50

Ok, I click on submit button to start the xoopsupdate.php procedure.
After only 1 second a new screen apear. My URL changed to "http://localhost:85/xoops/error.php?c=XOOPS_REFERER_BLOCKED"
I see the standard XOOPS header and a "User Actions" menu.
In this menu I choose "Administration".
No I got into the new administration screen of 2.2.
A warning appear that again the install directory exists.
The drop down menus work but Preferences seems to be empty.
I choose Modules/Administration for updating the System Admin Module.
After clicking the update button I see again the URL: "http://localhost:85/xoops/error.php?c=XOOPS_REFERER_BLOCKED" and again an empty screen with only the "User Actions" menu.

Now I choose logout. The logout message appear and the "User Actions" menu don't shown anymore. I see the standard XOOPS header, the current date on the upper left and a white emtpy screen. No menu, no blocks... nothing.
I call the user.php file to log in again, but every times it says "Incorrect login" and I'm 100% sure that I give the right username and the right password.

So I'll stop here. The update procedure 2.0.13 to 2.2 will not work and I have no clue why. It couldn't be a problem of any modules, themes or templates, because it fails on a really fresh install of full XOOPS 2.0.13.

I've repeated the same procecdure 3 times with no luck. I've tried the update als with a copy of my production site (www.neotrax.de), but with the exact same problems.
To prevent browser problems, I've done the update with IE6 and Firefox1.06 too.

Ok, now I'm ready for tips and solutions.

Thank you.

Markus

I'm getting the same REFERER_BLOCKED error.

I did a clean install of XOOPS 2.2, set up the admin account, and started working. Everything went well until I started to set up user groups. Then I get this error. I can't make other changes, either.

What goes?

well the way you posted it sounds like you just ftp'd the whole folder up at one time... when you should idealy do it a folder at a time.... so fror example if you are doing pub_html/language/english/... then you should ftp up the files in this directory and work your way back dow to public_html. it takes alot longer.... but well you wont crash out :)

Quote:

No FTP. As you could see in my description, I connect to localhost and for local file copy I don't need ftp. I don't think it is a problem of a file copy, because I had no problem s after copying all the 2.0.13 files, so why should I have a problem on copying the 2.2 files?

Ok, I've tried it again today on my business notebook with a fresh install of XAMPP from apachefriends.org. Again the same procedure with exact the same problems. Installing 2.0.13 went fine with no problems until I do the update to 2.2.

Hmm, what should I say. Two different computer, two different installations of apache, php any mysql, two different browsers (IE and Firefox) but the same problems with the update 2.0.13 -> 2.2.

What the hell I'm doing wrong?

regards
Markus

you're not doing anything wrong, that's the first thing to say. However, it should work, so we have to look at the cause of this.

First of all, you are using 2.0.13 non-english, and are upgrading to 2.2. The HTTP_REFERRER_BLOCKED error is triggered when a database query fails and the HTTP REFERER check also fails. So make sure that your localhost is added to the 'trusted sites' list of your software firewall (this being the most common cause for the HTTP REFERRER info being blocked).

With that fixed, we can proceed to what is causing the query to fail.

Herko

Quote:

I have no firewall (XP firewall is deactivated) and my 2.0.13 was english as the 2.2 too. Remember, my testsite is on localhost (127.0.0.1) and most firewalls don't block anything on this adapter.

But, I think I've found the reason for the problem and it seems to me a bug or a bad feature in the XOOPS update procedure. My webservers on both computers weren't running on port 80, that was the problem and looks to me like a bug.
Now I've changed my webserver to port 80 and the update script works.

But more. After the update I changed my webserver back to port 85 and on every login the referer block error message with hints on firewalls etc. do occur. It's not a big problem, but it shows that the referer checking in xoops-2.2 have problems with webservers not running on port 80.

I never had such problems with 2.0.x versions of XOOPS and I'm not sure if this referer block checking in 2.2 was a good idea.

regards
Markus

Quote:

It was already there in 2.0.x, but must have been changed if buggy now. I'll check this.

Thanks for the details

skalpa.>

As with Markus, I'm running XOOPS 2.2 English on my notebook through localhost, so there shouldn't be a firewall issue. I didn't get this error when I ran XOOPS 2.0.9. I'm running MAMP, on which Apache is running on port 8888, not port 80. If the REFERER_BLOCKED message stems from a port issue, can XOOPS be adjusted to ignore the port if the webserver is a localhost? I'd rather not change my Apache and MySQL port settings on my development notebook.

Quote:

I stuffed up both my sites when I upgraded.

I've managed to 95% fix one of them but the last few bugs are very hard for me to fix...

i have proformed the upgrade once safely. when i proformed the upgrade the second time on another XOOPS install i forgot to turn on the php debug on and i pressed the the button more than 1 on the XOOPS update page.

if you upload all the files correctly set the permissions and make sure the php debug is on before you start the upgrade it should work. when you load the xoopsupdate for the first time don't do anything but hit the refresh button after that page loads then press the update button 1 time only after that update all of your modules. that is how the succssfull update is done. if you don't follow the directions or are asleep while upgrading a site you will screw up badly. i have to now download and install a 2.0.13 to get the users and groups and other stuff working so basically i have to redo the site from ground up taking stuff from an old database to a new one without causing downtime. hopefully i can do it safely. just have everything backed up and do the things you try on a non production site. i will post my findings after i finish if i get it working.