Does CB store the DB prefix somewhere?

Hi folks,

I migrated a site from 1.5 to 1.7 and we are now using a new prefix for the database tables, but now the custom fields are failing to store.

When I ran the DB check in CB Tools, it is still looking for the old prefix - despite the fact that all the CB tables are using the new prefix.

Where is this stored? The rest of the site is working perfectly fine so I assume that CB must have stored/hard coded it somewhere but I can't find where that might be. It seems to be specifically related to the extra fields table.

Joomla! version 1.7.3
CB version 1.7.1

Ruth

OK I've tracked down where this was - in the extra fields table the database prefix is hard-coded under the 'table' column - why?

If I try using #__ (which would be the more sensible thing to use, no?) it then reports that the field is not present in #__comprofiler so I manually added it. Seems to be working now, naughty hard coding of prefix though

Ruth

Where is this stored? The rest of the site is working perfectly fine so I assume that CB must have stored/hard coded it somewhere but I can't find where that might be. It seems to be specifically related to the extra fields table.

Isn't stored anywhere, it's done through Joomlas API from CB.

OK I've tracked down where this was - in the extra fields table the database prefix is hard-coded under the 'table' column - why?

It shouldn't be. It should be #__, some migration tools have a tendency to replace all occurrences of #__ regardless of location. Replace them with #__ and you shouldn't have any further issues.

If I try using #__ (which would be the more sensible thing to use, no?) it then reports that the field is not present in #__comprofiler so I manually added it. Seems to be working now, naughty hard coding of prefix though

I would need phpmyadmin access to see what's broken as the migration you used probably replaced all #__. If you'd like I can take a look, please PM phpmyadmin login credentials and backend super administrator access.

Hey there,

Just to clarify, every other field had #__ except for the custom fields, which all had the original database prefix hard-coded. Every other field worked perfectly, and when I changed the database prefix in the custom fields to #__ and then created the missing fields in the #__comprofiler table (which were missing) it worked fine.

As a bit of history, this site was a 1.0.x site which was migrated to 1.5.x and then 1.7.x - so it's going back a long way - but the first time we had any problems with this was when we migrated to 1.7.x. The database prefix being used was for the 1.5.x site.

I could understand it if *every* instance of #__ had been replaced by the migration, but just one field, in a table which contains loads of other references to tables? Seems kinda odd. That's why it led me to wonder if at some point in the past, this value (referring to the comprofiler table) had the database prefix hard-coded in the database. I checked in other installations of CB and couldn't see any with similar instances, so wondered if it was an olddddddd historical thing from the depths of time!

Ruth

I've no idea, sense past 3 years that I am aware its always been #__. At any rate glad your issue was resolved! Was this field perhaps created by a plugin rather then through CB > Field Management?