Weird "notice" message after new-install

Previous topic

Install & configuration

Next topic

Author	Message
mikael lindqvist	Thursday 17 April 2003 4:28:36 am I deleted the old installation, unzipped the files (as usual, with "tar xvfz ez.tar.gz"). When I try to run setup by loading index.php I get this really weird message: Notice: Constant EZ_LEVEL_NOTICE already defined in /home/m/myportal/www/publish1/lib/ezutils/classes/ezdebug.php on line 85 Yes, indeed, "publish1" was the old catalog for the previous installation, but that catalog is long gone - deleted - finito. So where the heck does this message come from? Has ez publish planted an early eastern egg in my webhost's apache server? /Vardagen är långsam, du springer lätt ifrån den!
Scot Wilcoxon	Thursday 17 April 2003 5:54:44 am publish1 being in a URL does not mean there is a directory by that name. As you suggest the publish1 directory no longer exists, eZp might be finding that word in site.ini, a reused database table, or a rewritten URL. Check subdirectories within "settings" for files which mention "publish1" (find settings -type f -print \| xargs grep -i publish1). Check your web server URL rewrite rules (/etc/httpd/.../httpd.conf ?). I don't know what DB tables might have such a URL path; I mentioned it because your phrasing did not indicate that the DB was cleared out.
mikael lindqvist	Thursday 17 April 2003 6:38:13 am You are right, it used the old database. Clearing that solved the problem. Thanx :>

Author

Message

mikael lindqvist

Thursday 17 April 2003 4:28:36 am

I deleted the old installation, unzipped the files (as usual, with "tar xvfz ez.tar.gz").

When I try to run setup by loading index.php I get this really weird message:

Notice: Constant EZ_LEVEL_NOTICE already defined in /home/m/myportal/www/publish1/lib/ezutils/classes/ezdebug.php on line 85

Yes, indeed, "publish1" was the old catalog for the previous installation, but that catalog is long gone - deleted - finito. So where the heck does this message come from? Has ez publish planted an early eastern egg in my webhost's apache server?

/Vardagen är långsam, du springer lätt ifrån den!

Scot Wilcoxon

Thursday 17 April 2003 5:54:44 am

publish1 being in a URL does not mean there is a directory by that name. As you suggest the publish1 directory no longer exists, eZp might be finding that word in site.ini, a reused database table, or a rewritten URL.

Check subdirectories within "settings" for files which mention "publish1" (find settings -type f -print | xargs grep -i publish1). Check your web server URL rewrite rules (/etc/httpd/.../httpd.conf ?). I don't know what DB tables might have such a URL path; I mentioned it because your phrasing did not indicate that the DB was cleared out.

mikael lindqvist

Thursday 17 April 2003 6:38:13 am

You are right, it used the old database. Clearing that solved the problem. Thanx :>