XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


(1) 2 »


1
Lisa_S
Re: Restored Xoops 1.3.10 and mysql backup but...

  • 2003/11/11 9:35

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


I did a cpanel backup of the entire site and the MySQL database.
problem tho is the backup is in a weird structure, it looks nothing like what the site did when i backed it up. it appears that i have all the same modules on the backup and the new installation.

So I'll try the debug thing.. only problem is, i can't even access admin or anything, the error comes up on ALL pages that I try to access... too tired to deal with this now, i will reinstall XOOPS again with a new database and put the installation in debug mode.. then restore the old database.

Question: If I do that, won't the old database restoration revert whatever settings I have changed (like putting it into debug mode) and thus putting me back to square one?

Topic | Forum


2
Lisa_S
Re: Restored Xoops 1.3.10 and mysql backup but...

  • 2003/11/11 8:32

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


How do I find out what module is causing this to happen?
It doesn't say!
Topic | Forum


3
Lisa_S
Restored Xoops 1.3.10 and mysql backup but...

  • 2003/11/10 20:26

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


I've gone back to XOOPS 1.3.10 until the issues with upgrading to 2.0.5 and using the existing database are sorted out.

I can get my old theme back after the installation of 1.3.10 but as soon as I use cpanel to restore the MySQL database backup, my website coems up with a XOOPS error, saying "selected module does not exist"!

Is there some way to fix this because obviously the database has set some values that don't exist in the new instalation of 1.3.10. Do I need to upload the backup of the modules folder or something?

Topic | Forum


4
Lisa_S
Re: Ok, now it won't read from the old database...

  • 2003/11/8 7:45

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


PHP version 4.3.2
MySQL version 4.0.15-standard

Geez, this is really confusing! First the mainfile.php error and now this!

The 2.0.5 installation will finish in full if I rename the prefix of the tables to something other than XOOPS because the XOOPS prefix is already being used by the existing database from the XOOPS 1.3.10 installation a few months ago.

But I don't want it to make new tables for 2.0.5, i want it to use the old ones!

I don't think I even am making sense to myself anymore hehe everything is muddled up in my brain from all this complexity!
Herko Coomans wrote:
the update script detects the existance of 2.0 tables. If they already exist, then the installer doesn't overwrite them because it assumes the tables already are in place, and that 2.0 is already installed (which is a good assumption). The detection script is definately not working on your server, which is very strange. Can you give us some more info on the php version you're using and on what kind of server the xoop site is running?

Herko[/quote]
Topic | Forum


5
Lisa_S
Re: Ok, now it won't read from the old database...

  • 2003/11/7 20:28

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


No, they are 1.3.10 tables i believe. I was under the impression that the 2.0.5 installation would detect them and upgrade them, but it would not and I had to rename the table prefix on the installation to upgradexoops_ so it would continue installing. How do I make the installation continue installing after it detects that i have old XOOPS tables in my database?
Topic | Forum


6
Lisa_S
Ok, now it won't read from the old database...

  • 2003/11/7 12:27

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


Finally got past that mainfile.php problem. Connected to the database, the installation saw that there were existing tables and said "tables already exist" and stopped right there.

I was under the impression that the install would be able to use the existing database... I don't want to lose all the information I have on the exisitng one and would like XOOPS 2.0.5 to use it.

How do I make it do that?
Topic | Forum


7
Lisa_S
Re: Could not write into mainfile.php

  • 2003/11/6 18:47

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


Still haven't fixed this issue... help anyone? I'd like to get XOOPS installed!
Topic | Forum


8
Lisa_S
Re: Could not write into mainfile.php

  • 2003/11/5 23:07

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


Hmm it didn't seem to make any difference. I noticed something though but I don't know what it means. The error I am getting is defined as:

Quote:
define("_INSTALL_L60","Could not write into mainfile.php. Please check the file permission and try again.");


so I went and searched thru index.php for the install_l60 thing and it is here:

Quote:
case "dbsave":
include_once "./class/mainfilemanager.php";
$title = _INSTALL_L88;
$mm = new mainfile_manager("../mainfile.php");

$ret = $mm->copyDistFile();
if(! $ret){
$content = _INSTALL_L60;
include 'install_tpl.php';
exit();
}

$mm->setRewrite('XOOPS_ROOT_PATH', $myts->stripSlashesGPC($HTTP_POST_VARS['root_path']));
$mm->setRewrite('XOOPS_URL', $myts->stripSlashesGPC($HTTP_POST_VARS['xoops_url']));
$mm->setRewrite('XOOPS_DB_TYPE', $myts->stripSlashesGPC($HTTP_POST_VARS['database']));
$mm->setRewrite('XOOPS_DB_PREFIX', $myts->stripSlashesGPC($HTTP_POST_VARS['prefix']));
$mm->setRewrite('XOOPS_DB_HOST', $myts->stripSlashesGPC($HTTP_POST_VARS['dbhost']));
$mm->setRewrite('XOOPS_DB_USER', $myts->stripSlashesGPC($HTTP_POST_VARS['dbuname']));
$mm->setRewrite('XOOPS_DB_PASS', $myts->stripSlashesGPC($HTTP_POST_VARS['dbpass']));
$mm->setRewrite('XOOPS_DB_NAME', $myts->stripSlashesGPC($HTTP_POST_VARS['dbname']));
$mm->setRewrite('XOOPS_DB_PCONNECT', intval($HTTP_POST_VARS['db_pconnect']));
$mm->setRewrite('XOOPS_GROUP_ADMIN', 1);
$mm->setRewrite('XOOPS_GROUP_USERS', 2);
$mm->setRewrite('XOOPS_GROUP_ANONYMOUS', 3);

$ret = $mm->doRewrite();
if(! $ret){
$content = _INSTALL_L60;
include 'install_tpl.php';
exit();
}


as well as here:

Quote:
case 'updateTables_go':
include_once "../mainfile.php";
$error = false;
$g_webmasters = isset($g_webmasters) ? intval($g_webmasters) : 0;
$g_users = isset($g_users) ? intval($g_users) : 0;
$g_anonymous = isset($g_anonymous) ? intval($g_anonymous) : 0;
if (empty($g_webmasters) || empty($g_users) || empty($g_anonymous)) {
$error = true;
} else {
include_once "./class/mainfilemanager.php";
$title = _INSTALL_L88;
$mm = new mainfile_manager("../mainfile.php");
$mm->setRewrite('XOOPS_GROUP_ADMIN', $g_webmasters);
$mm->setRewrite('XOOPS_GROUP_USERS', $g_users);
$mm->setRewrite('XOOPS_GROUP_ANONYMOUS', $g_anonymous);

$ret = $mm->doRewrite();
if(!$ret){
$content = _INSTALL_L60;
include 'install_tpl.php';
exit();


To me it looks like something to do with databases? This does not seem right but could it be possible that one of the entries I have for the configuration be wrong - like wrong database name, user, password or something like that?

Any more suggestions? I don't want to delete the database as I was told that once i removed the old files from ver. 1.3.10, and uploaded the new files for 2.05 and installed, it would automatically detect my existing database and upgrade/install etc.

Thanks
Topic | Forum


9
Lisa_S
Re: Could not write into mainfile.php

  • 2003/11/5 20:05

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


Thank you...

Ok, I reuploaded the install folder fresh but no go again.

I am looking in code now to find file access checks but can't see them yet. I don't know a great deal about php, just enough to get by and edit/fix some things. Could you be more specific so I can find the right lines easier?

: )
-Lisa
Topic | Forum


10
Lisa_S
Re: Could not write into mainfile.php

  • 2003/11/5 18:31

  • Lisa_S

  • Just popping in

  • Posts: 13

  • Since: 2003/1/30


Uh... I tried that (as I said in my previous post)

"I've done a search, tried replacing the mainfile with the contents of mainfile.dist.php and replacing my details in it... but no go"

When I do that and hit refresh, the error still comes up and the installation won't move past that point.

Can anyone help me out on this?
Topic | Forum



TopTop
(1) 2 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

209 user(s) are online (127 user(s) are browsing Support Forums)

Members: 0

Guests: 209

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits