Unforseen

I'm not sure, I just deleted the mysql database and deleted the folder that I installed xoops to and reinstalled it. It all fixed itself.

john

Keep looking through the script then. I had a case where I deleted a block of code that didn't suit me, and it wouldn't go away. Found out it was in more than one place. Eventually got it.

I'm going to check out the index.html file in templates_c. I may send you a copy to put in there, as there has always been one in my installs, and I've always been told to never delete it.

Hmmm...

John

__________________
servers: dedi - petra1.petrahosting.net, petra2.petrahosting.net

Homepage: fernau.us (on petra1)

Failure is not an option. It comes standard with all Microsoft products.

john

Ahh... Gremlins. A nasty little bunch... :evil:

__________________
servers: dedi - petra1.petrahosting.net, petra2.petrahosting.net

Homepage: fernau.us (on petra1)

Failure is not an option. It comes standard with all Microsoft products.

asche

Hi Xoopsies,

I have a problem connecting to the database while installing xoops. I am not quite sure where to place my question, so I am glad to find this thread "XOOPS Help Area". Is it possible to establish a Xoops-Forum or shall questions like this be posted in Scripta-Forum (not all questions can be posted in this thread).

My Problem:
First I tried to install Xoops via Scripta and everything seemed to work fine. But no database was created. After creating db manually and installing again, no tables were written into the database. When trying to access http://66.195.17.52/~fporg/ I receive the error "Unable to connect to database in file class/database/databasefactory.php line 34".

Trying to install manually by calling .../install/index.php I receive the error "Could not connect to the database server".

Can you please tell me, why it is not possible to connect to the databaseserver?
Are there any logfiles for installation? I could not find any in cpanel relating to this installation.

Does anybody know a solution?

Asche

john

asche,

I'm afraid that I'm too tired to think at the moment, but I will try to duplicate your problem on Monday, and we'll go from there. I haven't tried the xoops install, because I found that it was very easy to install "manually".

I'll give it a go and see what I can see.

John

__________________
servers: dedi - petra1.petrahosting.net, petra2.petrahosting.net

Homepage: fernau.us (on petra1)

Failure is not an option. It comes standard with all Microsoft products.

asche

thanks Ryan for your reply and offer assistance.

Support meanwhile resetted dbserver (can I do this myself?), and in reinstalling with scripta a new database was created with the name fporg_xoop1 (I chose the name fporg_xoops, but no tables were written into this preinstalled db and fporg_xoop1 was created by scripta). So installation works, but I cant connect to db of my choice and have different dbname to my localsystem.

One thing I noticed, that installing xoops with scripta sets up an database with the prefix of the account-user (in this case fporg_). This does not happen in manual install and so xoops-customers should be aware of it (otherwise they have to reinstall db on surpass or locally).

Just a remark concerning "xoops-forum"/"XOOPS Help Area":
It would make sense, if this would be written down in the forum, but right now, I don't find a place. I would post in scripta forum, but that does not fit for a manual install of xoops. It would be useful and transparent to have a xoops-forum, so that all questions concerning xoops is in one place (otherwise you'll find my dummy-questions scattered in all forums :-))). "XOOPS Help Area" is the wrong place for a "xoops-forum", because it is in news-forum, but ought to be next to scripta-forum or subforum of it.

thanks and regards

asche

Kayla

We offer many different programs to install, and all questions should go into Shared Hosting Support if you have a shared account, or into the Reseller Forum if you are a reseller. We cannot have a XOOPS forum, or we would have to add 50 more forums. The ideal place that we prefer any topic to be discussed on anything available in Scripta, is the Scripta forum.

asche

xoops installation error solved: Could not connect to the database server

I think it was all about prefixes of database and dbuser in manual install .... I'll describe later.

tanks for having a look at my question :-)))

newshax

Howdy, I am defecting from a rather poor host (CI) and am trying to migrate my existing Xoops site over but I am seeing a potential minor problem already for a guy who is a little more of a content person than a webmaster. I want to be able to create a database named the same as the DB I have with CI, but when I create a mySQL database here through scripta, it adds my domain name as a prefix to the DB name I chose.

I've done one server migration in the past but I seemingly recall that I had to keep my database name and all admin logins the same as before. I'm not a mySQL expert, I can just do the basics like take backups and drop tables though mySQL admin, etc. and I don't know what options are available to solve this problem, or if I even need to worry about it.

Anyone have any advice? Thanks