Fabrik is connecting to wrong site database

[artonezero]

We recently changed the database for a Fabrik 3.0.8 site on Joomla 2.5.11 (to revert to an earlier backup). It has a new name. Both the old and new MySQL database are still on the server.

However Fabrik is still connecting to the old database when we try to create a new list, even though all the site connection records have been deleted (even in PHPMyAdmin). Joomla caching is switched off.

Is this a known problem? Can you advise how we might debug the problem?

Thanks
Mike

 

[lcollong]

In such situation, I open the fabrik connection record, verify that is pointing to the right database and then save it. You may got an error. Just redo once more the all thing then it should be ok. There is a test link to verify. Hope it may help.

 

[artonezero]

Thanks for the input, but we've been using Fabrik for over 4 years and this is a very obscure technical problem. Could someone from fabrik offer a suggestion please?

 

[troester]

even though all the site connection records have been deleted

So what are your fabrik connections?
Which connection with which id is pointing to which database?

 

[artonezero]

Solved: The problem is that Fabrik doesn't delete old site connections documents completely from the sql table. Therefore a site connection record with ID=1 remains in the table. The solution is to delete the old records with PHPMyAdmin and then edit the new site connection record in PHPMyAdmin and set the ID=1

 

[troester]

You shouldn't delete a fabrik connection but - as lollong said - just edit it and set (or just confirm) the new connection parameters.
This way you won't have to handle anything with PHPMyAdmin.

 

[artonezero]

Problem is that doesn't work. As I explained to begin with, we chnaged the database part way through development and that confused Fabrik ...

 

[rob]

note the connections are cached, so if you are logged in on the front end, edit the connection on the back end, you will still be using the previous connection. In this case log out/in on the front end to ensure you are using the latest connection details