In the XOOPS 2.3.0 Alpha 2 release annoucement they say:

Quote:
So may be the best upgrading strategy for us 2.2.2 users is just wait until that happens and go straight to 2.3 and don't mess with any middle steps.

Sniff... :(

200 hits already and yet not a single comment to my post...

Nobody has ever gone through this upgrade before?

Trying to document myself before doing this upgrade I've found some contradictory posts in the forums that still keep me unsure how to proceed. In essence, options are:

A.- Going the full way, step by step through all these:

2.2.2 to 2.2.3a upgrade
2.2.3a to 2.2.4 upgrade
2.2.5 full version (no upgrade patch is available)
2.2.5 security patch
2.2.5 to 2.2.6 upgrade

B.- Skip some of those steps: probably the first two, since 2.2.5 full will overwrite everything previous; and most likely the security patch, which should be covered well enough by 2.2.6 upgrade. Hence, only two steps would remain:

Overwrite 2.2.2 with 2.2.5 full
2.2.5 to 2.2.6 upgrade

C.- Forget all about the gradual approach and just apply 2.2.6 full version directly on top of 2.2.2

From what is said in the UPDATE.html instructions that come with the 2.2.6 full package, I gather that option C.- should be OK. Those instructions state "Upgrade From Previous 2.2.x", so I understand that applies to 2.2.2 as well.

However, I've read somewhere that if you do it like that things may not turn up well, and that option B.- might be safer. This doesn't make much sense to me, but certainly I'd love to hear some advice from you before I start messing up my site.

BTW, the 2.2.6 UPDATE.html literally instructs to "Upload the 2.2.x files, overwriting existing files", but I assume before that chmod 444 should be applied in order to protect mainfile.php, right? If so, that would better be noted in the instructions, don't you think?.

Thanks for reading me and please have a nice day.
MD

As far as I know proper "if...else" syntax is:

if (expression) {
sentences
}
else {
sentences
}


Therefore I think that your code should read like this:

if($num1<5{
echo "Sold Out";
}
else{
echo "Buy Now";
}

The problem's gone now. I can get into the admin area again. Here's what I did:

1. Went back to XOOPS 2.0.13 from my last backup before the update to 2.2
2. New update to XOOPS 2.2, running again xoopsupdate.php

That's it. No more troubles to get in the admin section.

In your case, since you're still with 2.0.13, may be you could backup your current files and try an update to 2.2

Good luck

I'm having exactly the same trouble, only with XOOPS 2.2 and in my case I do see a click button under the message. However, clicking on it has no effect (only a message for a while saying that it's making a connection, but then it comes back to the same place).
It's strange, I've updated to 2.2 a few days ago and everything went fine, accesing to the admin area many times before without this problem. Don't know why all of a sudden the system decides that this is my first time to the admin area.
Permissions of my cache directory are also ok.

Sorry, not much of a help, but at least I hope it makes you feel not to be the only one in the world having this (I thought I was, before reading your post; one always thinks so, but never is).

Yes, thank you very much for your advice. I'm trying to do so, however I'm not being able to do the upgrade to News 1.3.

One of the steps involved is running a script which I cannot get, since the URL given both at the readme file and the download page only takes me to the dreaded message File Not Found on This Server.
I've tried also a fresh install, which seems not to require the script, but it won't work either.

I'll keep trying.

Have a nice day.

Just instaled XOOPS 2.0.9.2 locally over Mac OS X 10.3.8/Apache 1.3.33 (Darwin)/PHP 5.0.1/MySQL 4.0.21.

Everything behaved properly until I activated Module News 1.1 that comes with the package:

FIRST. When I click on 'Submit News' the expected form to write the piece of news will open, but below I get:

Warning [PHP]: Invalid argument supplied for foreach() in file modules/news/submit.php line 34
Notice [PHP]: Undefined index: anonpost in file modules/news/include/storyform.inc.php line 39

If I fill in the form and click submit then I get back the same window with the form cleared and no news have been published at all.

Going to line 34 of the file mentioned by the warning I see that the variable $HTTP_POST_VARS is used there. This array was deprecated since PHP 4.1 in favour of $_POST and has given me some trouble before (any time I write a form with PHP, after submitting, my system seems unable to read the contents of the old $HTTP_POST_VARS and I'm therefore always obliged to use $_POST). But I must declare that regarding PHP I'm only less than a not very able amateur.

SECOND. The control panel of the module News is not behaving properly either. Out of the three options expected there, I can only enter into Preferences (Config options), while the Topic Manager and Post/Edit News take me nowhere.

THIRD. I read in some posts in this same forum that newer versions of News are available somewhere. The one I got included with XOOPS 2.0.9.2 is News 1.1 but at least I've heard of 1.3 being around. However I don't know how to upgrade to see if this might solve my problems. I can't find this neither at the Module Repository section nor following the links given in those posts, which only take me to a 404 error.

Have a nice day and thanks to all.