Database problem with two TP's on one database

[Nokonium]

I already had a TP test running, own folder and own table prefix, when I tried to install TP on another test board, again own folder and own table prefix. There were problems with the resulting SMF+TP so I uninstalled it. The uninstall exposed a problem with the other installation:

Table '##########.tportal_settings' doesn't exist
File: /[munge]/Sources/TPortal.php
Line: 46

It looks to me like the second install overwrote the first table entries and deleted all of them on the uninstall.

[Bjørn]

Yes..I am afraid the tables for TP is with a set prefix. So if you install multiple TP+SMF on the same database, there will be errors.

I might add this in future versions though.

[Nokonium]

Thanks Bloc

[borgBOB]

Bloc, I have 3 installs of SMF with TP on the same server, and no problems.   All are in the same root directory, and all have seperate databases in MySQL.

Check my profile for specs.

[Nokonium]

I only have one database available, so I can only use different table prefixes for the different instalations.

[Bjørn]

I will see if I can make all calls to the tportal_xxx tables use a settable prefix. That way you can at least set a new prefix in one place, change it physically in the databse, and just install a new version with the normal prefix. And so on.

[hivelord]

I only have one database available, so I can only use different table prefixes for the different instalations.

Out of personal interest, why do you only have 1 database? Is it your hosting deal?

[Nokonium]

I only have one database available, so I can only use different table prefixes for the different instalations.

Is it your hosting deal?

Yes

[Nokonium]

I will see if I can make all calls to the tportal_xxx tables use a settable prefix. That way you can at least set a new prefix in one place, change it physically in the databse, and just install a new version with the normal prefix. And so on.

Thanks Bloc

[Kindred]

Bloc,  what if you just append the SMF prefix from the smf instance?

so, default would be smf_tportal_
if you has a second smf installed, in the same database using jpw as the prefix, the call would go to jpw_tportal_



so call for
FROM $db_prefix.tportal_settings
instead of just
FROM tportal_settings