Dear Xoopers,

I can connect to my DB but I can not log in or see my pages when I point to certain other data bases. I receive a "Can not access" prompt when I enter, "admin.php" But when I point back to the data base XOOPS created on the install - it works fine.

I would like to ask a couple of questions - Please assume that all the table in each data base has the same prefix and we are using the same server and server configurations and that all path statements are correct.

1 - Do different versions of XOOPS create tables that can not be read by other versions of Xoops?

2 - Can you install a more recent version of XOOPS and point it to a data base created with an earlier version? Or how about the other way, a data base created with a later verions and that can be displayed with an earlier version of Xoops?

Xoops 2.0.10 created database be read by XOOPS 2.0.13 ?
Xoops 2.0.13.2 created database be read by XOOPS 2.0.13 ?

I have been testing and I do see problems with compatability. Please help.

hhttps://xoops.org/modules/smartfaq/


1. no, but there maybe differences.. usually a later version either means bugfixes or extra features..

2. sure but whats the point? versions are different for obvious reasons, so it's obvious there will probably be issues.

compatibility?? u answered your own question..

use 2.0.10 files for a 2.0.10 db, isn't that what it's meant for??

what are you trying to accomplish??

Thank you for your reply Monty

I have databases that were created by earlier versions of XOOPS that seem to not display with later versions. I am thinking what would make an earlier created database not work with the later version of Xoops?

Does one need to upgrade and the data tables and other structures then also upgrade?

Here is another issue, I created a data base with 2.0.13 and now it will not work in 2.0.13.2. Should I have upgraded first? I did not upgrade I just installed new version of XOOPS 2.0.13.2 and pointed this version to the data base created with 2.0.13. Is this a problem and I should not be doing this?

g.

theres always a proper upgrade procedure which is best followed. you can find the upgrade patches in the downloads section.

2.0.13 > 2.0.13.2 does not have any database changes, they should work.. you must not have the correct info in mainfile.php

the faq section should help you..

also you must make sure you have exactly the same versions of modules (files) too when you are doing it like i think you are doing.. those factors alone if not correct can cause problems.

Did not think of the modules being different - that makes sense. That is what is possibily causing this problem. Thank you very much for your persistence in helping me.

g.

Sorry to be so much of a problem -

I have now done this proceedure:

-1- The data base is working on 2.0.13 and then I installed the same version 2.0.13 and gave the folder a different name.

-2- Upon setting up the config I gave the prefixed the same name as the data base I want to migrate

-3- I completed the install and removed "install.php" and set maincnf.php to 444

-4- I was then able to log on as admin and all was fine

-5- I went to phpmyadmin and dropped out all the tables and data and imported a duplicate of the working data base. Prior to this, I saved a backup of the working database and gave it a different name.

-6- After the import was finished I saw that the numbers of records were identical to the working data base and there no errors

-7- Still logged on the phpmyadmin, I then went to the browser and clicked on the URL

-8- I now get a blank screen

-9- I then go to the root and evoke the "admin.php" script

-10- Access denied

- 11-I clear my cache and go to the sessions table and empty it - still no access

-12- I went back to phpmyadmin and selected all tables and did a "check" all tables report "OK."

-13- I pointed back to the database where the structures were built by the install wizard - it works fine.

About Installed Modules
I have upoaded all of the modules that I have in the working database.

If I use the structures that are built during the install process, I can get into the admin and see all of these module in the folder uninstalled.

What a 2 two days of trying to figure this out -

When trying to mirgrate your data base to another install, the Protector module unless disabled entirely may cause you to have blank screens and lock you.