I backed up the database and uninstalled phpList using the server’s automatic installation system. This deleted all the phpList files and also the unique folder that they were loaded into. This also deleted the SQL database which had been used by phpList.
I started from scratch with a manual install of phpList version 3.5.5 from phplist.org, and unzipped this into a new “lists” subfolder of public_html.
I created a new database on the server and added the details to the config.php file in the config subfolder as per the manual installation instructions.
I then navigated in the browser to mysite/lists/admin/ and got BLANK SCREEN. This time not even a request to login.
The html created by admin/index.php has “body” of class “invisible”, which has style visibility:hidden.
Removing that class results in some display (left hand column and login button). However nothing much else appears and I suspect here are other parts of the page which also have the “hidden” style.
I noticed that phpList3ToBootstrap.js calls a function “removeClass” to remove the invisible class from “body” and the comment says that this happens “after loading”. I suspect that after the page loads, subject to security checks etc. the relevant parts of the page are supposed to display. Bearing in mind that my current page is a completely fresh installation the part which should display is that described in the manual, which would enable me to create the correct tables in the database.
However, it looks like something is preventing this happening. Perhaps phpList3ToBootstrap.js is not being loaded for some reason or there is a switch which is preventing the usual “unhiding” procedures from being implemented.
This will be too complicated for me to try to fix and I haven’t got the time to do this anyway - also any repair would be rubbed out on the first update.
I do not think I have any unusual arrangement. My site is hosted by Crazy Domains in Australia and I am using Google Chome, although MS Edge gives the same results - and as I said it worked perfectly before. It is very strange however that no one else has reported this issue.
Sorry, you did ask whether there was an error message in the html and I didn’t answer that.
I found this:-
This did not add any error message to the html, however I did notice that the developer tools of both Chrome and Edge reported a 500 (Internal Server Error) when loading the page. This is reported irrespective of the error_reporting(-1); line being added.