Hi all,

My first XOOPS site is up and running finally! (http://www.pnins.school.nz). I had a few problems installing, not sure what it was, so in the end, as the host had Fantastico available, I used that to install XOOPS at the top level.

The site's working fine and users login (just two or three people have access) by putting "/user.php" at the end of the URL for the site. The problem I'm finding is that no matter what machine I sit at...PC, Mac....no matter what browser I'm using....I end up having to log in twice?

What happens is that it accepts my login and welcomes me...it often even gives me access to the back area of the site....but if I try and do anything, it says I don't have permission and redirects me to the main page. The only way to overcome it is to start the process over again and the second time it then works.

As I say, I've tried this on a few different machines, so I'm not sure what it is. It was suggested in another posting about a different issue, that a Fantastico installation causes these problems, but how do I overcome them? I really don't want to have to go through a manual install.

Any suggestions?

Cheers,

Phil

Congrats on the new site. It should be good for the school. If you've been around the board and found all the Fantastico or whatever it's called problems than I'm not sure. But since you have no control of the server my best advice is to find a better service.

Do you have high speed access at the school? An idea might be a project for the techies, artists, and whatnot to build the server and locate it at the school. If you have an expert guide to help than it is the best thing to have control of the site. You just need the right people to look over and maintain things.

Now if you were a little closer than the almost absolute farthest away from me in Canada I'd love to teach the project.

But then how close does a person need to be in virtual space?.....

Thanks...the Fantastico comment was just one that I picked up on in another thread, but didn't actually say what the cause was or how to solve it...just that people that had used Fantastico as an installer sometimes experienced this.

With regards the other comments....no, that's way out of the league of what I or the school would want to do...and we're very happy with the new host of the website, who we moved to because of PHP, mySQL etc...as I knew that I wanted to use Xoops.

Any other ideas anyone?

Thanks again.

Phil

Installing XOOPS manually is not hard. It's easier than any other cms I've tried. If you don't want to install manually, then I suggest reuploading the user.php and the common.php files without overwriting but uploading them fresh. Also check the file size of the files and see if there is a difference between the size of them on your server and the size in the original XOOPS folder. Fantastico does not always upload files correctly and you could have files that are not complete.

I had a similar problem. It was a bug in the theme. Try one of the themes that is in the distribution to see if it works.
I did not debug the theme I just moved on to the next one.

Yeehah....cracked it....and no, it wasn't any of the above (well, I didn't try changing the theme).

I was trying the suggestion of replacing the 'user' and 'common' files but noticed that on my first login attempt, the site was saying 'welcome' and then redirecting tohttp://pnins.school.nz (Note that there's no www in that address).

That's odd I thought...so I tried quitting Safari (it caches everything!) and tried the shorter domain with the '/user.php' added....result...only needed to login once!

So, what I did...and now everything is working....is altered the setting in the mainfile.php that said...
Quote:
to
Quote:
and now it all works.

I'm not sure what causes it...but perhaps when using Fantastico, the install process puts the domain name into this mainfile.php config file as too short a URL.....perhaps the complete one is needed?

Thanks for all the advice though guys.

Phil

I had something similar (maybe the same?).
We moved our Intranet site to a new machine.
I changed the XOOPS_URL def in mainfile to the new IP address.
(the old XOOPS_URL washttp://intranet.. and the newhttp://192.168....)
After anything was running on the new machine, our admin changed the IP setting of Intranet from the old IP to the new IP.
Every time I wanted to login underhttp://intranet I was redirected to thehttp://192.168.... and had again to login.

I think this was because of the cookie.
The first login created a XOOPS cookie forhttp://Intranet
after login I was redirected tohttp://192.168.... and no cookie there.
No cookie for 192.168... means have to login again, but now underhttp://192.168.... and then the cookie was ok.