Failed to upgrade 3.0.6 to 3.0.7

[Hawiak]

Hey folks,


I have to upgrade a running 3.0.6 to the newer version 3.0.7. As I am new to PhpList I looked up the upgrade guide which is found here: http://docs.phplist.com/PhplistUpgrade.html
I followed the steps and after i was done I launched the browser on the adres /admin and I found a page with only the header (With the phpList.com logo and a login button)
I clicked on the login button and the page stayed blank.
I opened up my Chrome debug console and in the network tab I saw that the page returned a 500 internal error after which i ofcourse looked in my error logs, where I couldn't find any errors.

After this I decided to make a new folder called /new/ in the root of the, now backed up to 3.0.6, phplist and start a new installation in that folder. After which I created a new database scheme and edited the config files. If I now load the page I get a bunch of errors and I cannot seem to initialize the database anywhere.

Can someone please provide me with some help?

Greetings,
Hawiak

[danwaterloo]

It doesn't sound like after the upgrade, the page with the login button, that you had to enter the username and password (i.e. admin and whatever the password is)? usually this is in a /lists/admin location... not just /admin.

If all was working before the upgrade, here's what I would do to upgrade the system.... rename the original3.06 'lists' folder to 'lists306' (using the move command...) that way, worst case, you can just move it back and you're back to where you started.

download the 3.07, unzip, and move the 'lists' folder to the directory of the original installation. now you have, basically, a 3.07 version installed where the 3.06 was installed, without any of the config.php file settings.

Lastly, you can copy the config.php file from the 3.06 installation, over to 3.07 installation. the file 'lives' in the /lists/config/ folder...

Once you do that, you should be able to go to the original login page, and login. It will ask you if you want to upgrade your database, say yes (a couple of times), and you should be good to go.

[Hawiak]

Thanks for your answer,

The thing is though, that I moved the content from /lists/admin to /admin on the server.
Phplist was working before.

[Dragonrider]

I think you skipped item 3: Replace your old phpList with the new version.

By uploading the entire package to lists/admin, you've overwritten the actually files in admin with the lists folder.

Strongly recommend that you do as Dan suggests, upload the contents of "lists" from the 3.0.7 zip/tg file to a new directory, eg: lists37, try to recover your older config.php file, adjust the $pageroot to lists37 and try to access your phpList at domain/lists37, then update the database

[Hawiak]

Does the /lists/ folder matter that much in PhpList that it has to be there?
To me it seems kind of pointless to have an empty folder container another folder. Why just dont have the 1 folder.
As I also already mentioned in my first post. I have tried to install PhpList as a new application in a folder /new/ (Where i dragged contents of the /lists/ folder) and as I mentioned I do get the mysql errors if i devine an empty database and if i use my old database the error reoccurs)

Does it really matter so much to have /lists as the root folder?

[danwaterloo]

The /lists folder is there so that if you put this in the same directory as a website, it keeps the phpList installation separate from all the other files, and easy to upgrade (i.e. the index.php or index.html won't overwrite the default page in your website).

If you want to eliminate it, you need to go and change a bunch of the default settings in the install... web based settings, and settings in the config.php.

To keep the confusion down to 'a dull roar' , I would recommend that you retain the /lists folder. It makes it easier to do upgrades etc. Of course, you can make any modifications you want, you are just 'off the beaten path' when you do so...

[Dragonrider]

Does it really matter so much to have /lists as the root folder?

The ONLY reason you would do this would be if your domain is dedicated to your phpList install. If you have a web site at your domain, then not using the highly recommended /lists/ directory will usually overwrite your web site files, thus ruining your entire site.

[duncanc]

The "lists" directory is not empty, it contains the phplist public pages. So if your directory is empty then you have mistakenly deleted the files.
phplist has a two-level directory structure. You can change "lists" to whatever you like, then record that in config.php,

Code: Select all

$pageroot = '/lists';

Or you can put phplist in the root directory of your web server but then you might have a problem if you already have an index.php file in your root directory.

[Hawiak]

Alright thanks for your enlightment on this matter.

Yes I do have a dedicated Vhost to the mailer, so it is actually a stand alone app.
It also is a running process for a ton of users so I can't just go around and change all the existing systems, thats why I can't simply change it to the lists folder instead of the root.

Thanks for your answers!
Ill keep you up to date once I succeed in upgrading PhpList

[Hawiak]

I would like to bump this thread.

I tried installing 3.0.8 yesterday and I failed horribly.

The issue remains the same (even with the mentioned rootpage property in the config)

Code: Select all

$pageroot = '/lists';

Doesnt work (When changed).

Also, when i try to install the application on my local server (Fresh install + fresh database) the initilising of the database fails. (As in, after clicking the button the screen is blank except for the header)
The error logs are also empty.

I've used windows + xampp for the local setup.