Nevermind. I was reading more topics and I found a reply that said why IP addresses will not be supported. Does me no good at work, but maybe I'll find a personal use.

As a follow-up, I modified the hosts file on my Windows box to map the IP address to the actual hostname of the Linux web server. I can connect OK, but I still cannot login. This is really tiresome as I've reinstalled OPN seven times now. Cookies are enabled and every other PHP app works fine. There has to be more to this issue than IP addresses.

Attention. A hostname is sometimes not a FQDN (Full Qualified Domain Name).
And did you install OPN after you changed your hosts file?
When not then please do that. Cause then the OPN config holds the IP adress as the URL.
When yes, please delete all OPN cookies and delete the content of the tables prefix_opn_opnsession and prefix_opn_session. Where prefix_ is the prefix that you have entered in the installscript.

Yes, I have re-installed multiple times after changing hosts file. I have dropped and created the database each time. I have wasted an entire day on trying to install this. It isn't supposed to be this hard. Here is the data I enter for the install script:

http://core104/opn/install.php ### to start install
Database Host: localhost
Database Driver: MySQL
Database Connection String: ### leave blank
Database Username: rossler
Database Paswword: xxxxx ### the appropriate password
Database Name: nuke
Table Prefix: opn
URL: http://core104/opn
Physical Path: /srv/www/htdocs/opn/
Install Directory: ### left blank
### according to directions, not needed unless
### I were installing at /srv/www/opn
Encription Type: MD5

When install finishes. I can go to http://core104/opn/index.php to get the login page. It will never let me login and now on my 12th install I get WARNING [8] Undefined Offset: -1

Here is what the hosts file looks like:
127.0.0.1 localhost
172.xx.xx.xxx core104.oklaosf.state.ok.us core104 ### proper IP address of course

This is unbelievably frustrating. This is not rocket science.

Some hints for easier testing:

When you are testing with OPN you can use the Core Download....Much smaller than the Full and not so much uploadtime. After playing around it' very easy to install the whole modules (or to do the Full Install if you solved the first problems) That's because OPN is fully modular, you can install an deinstall each module from the Modules Package for it's own.

It's not necessary to upload all the files before each install. Before doing a fresh install, check the directory html/cache : There you find a file install.lock. Delete this file. This file prevents you from accidentially make a new install. Also delete the subdirectories in html/cache/. These subdirectories are made by OPN while installing. That's all.

manne

But you must empty the database for OPN before a new install.

Quote:
URL: http://core104/opn

Seems to be a bad entry:
OPN assumes a Fully Qualified Domainname (Hope it's the right name)
e.g http://www.example.com
or http://www.example.com/opn

or something like this

manne

Quote:
2004-08-26 20:43
manne wrote:
Some hints for easier testing:

When you are testing with OPN you can use the Core Download....Much smaller than the Full and not so much uploadtime. After playing around it' very easy to install the whole modules (or to do the Full Install if you solved the first problems) That's because OPN is fully modular, you can install an deinstall each module from the Modules Package for it's own.

It's not necessary to upload all the files before each install. Before doing a fresh install, check the directory html/cache : There you find a file install.lock. Delete this file. This file prevents you from accidentially make a new install. Also delete the subdirectories in html/cache/. These subdirectories are made by OPN while installing. That's all.

manne

But you must empty the database for OPN before a new install.

Those are fine tips for testing, but they don't point me in a direction for solving the problem. File size and upload time are not my concerns. I have two windows open. An ssh connection to provide root access on the web server and a browser window to access the application. I have the opn files unpacked in a personal subdirectory and can copy (cp -r) those files to the web server directory in seconds. My unpacked location is ~/opn2/. I copy everything from ~/opn2/html (including all subdirs) to /srv/www/htdocs/opn. I change the permissions on ./cache to 777 as mentioned in docs, I touch mainfile.php and set it also to 777, then I swap to the browser and point to http://core104/opn/install.php. Each time I do this procedure I drop the database and re-create it.

I'd like to know what module in the code, I can troubleshoot to find out what happens at login. In all my attempts, not a single cookie has been generated for the browser. Nor do any subdirectories get created in opn/cache.

Thanks for the tip, I can save a little time by skipping the delete and re-copy of the filesystem by removing the install.lock file.

Now the login problem needs to be solved.

As I and manne told. OPN need a FQDN for proper work. and http://servername is not a FQDN.
So you must change your hosts file entrie to a FQDN and when you use Apache or Apache2 as webserver you can create a virtual host for it.

Quote:
2004-08-26 20:56
manne wrote:
URL: http://core104/opn
>
> Seems to be a bad entry:
> OPN assumes a Fully Qualified Domainname (Hope it's the right name)
> e.g http://www.example.com
> or http://www.example.com/opn
>
> or something like this
>
> manne
>

I re-installed again, replacing all occurances of "core104" with "core104.oklaosf.state.ok.us" and the WARNING about offset went away, but logins still don't work. Just keeps looping back to the login page.

BTW - If I haven't mentioned it, I am using version 2.1.2

The hosts file HAS the FQDN. A proper entry in the hosts file has the IP address, the FQDN and an alias. The alias is not required, but my hosts entry has all three. The TCP/IP connection is properly interpreting the IP address, the alias, and the FQDN all to the same location.

I have tried using all three in the install script and none of them work.