G'day itgl72
I know that you've struggled patiently with this problem for the past couple of months, but there's light at the end of the tunnel!
First of all, the answer to your question "Where are the signatures now?" The changes in
Kunena 1.0.10 and
Community Builder 1.2.1 have not changed where
Kunena obtains the signature information. The signature information, used in
Kunena's forums, has always been obtained from the
Kunena user profile.
What
has changed is that users can now update the
Kunena forum signatures directly from the
Community Builder user profile!
However, if you have just installed K 1.0.10 with CB 1.2.1, and you have set
Kunena Configuration »
Integration »
Profile Settings »
Profile = Community Builder, you may be wondering why your
Community Builder users' signatures are not appearing in your forum!
I think this is at the heart of itgl72's problem and what Matias was trying to suggest to overcome the problem.
Installing K 1.0.10 (or integrating it with CB 1.2.1) does not initialise the signature information.
Before K 1.0.10,
Community Builder didn't work with
Kunena w.r.t. the user's ability to update signature information (among other things). Matias offered a workaround to synch the information between CB's user table and the
Kunena user table - see
Signature, ordering and viewtype migration script for CB. The problem with this workaround was that the SQL procedure needed to be repeatedly run at regular intervals.
With K 1.0.10 the need for this "synchronisation" has disappeared ... except for the purposes of initialising the
Kunena signatures from the CB user profiles. This is the core of your problem.
Therefore, in order to initialise your
Kunena data with existing
Community Builder information, you will need to run this SQL procedure
once:
UPDATE
jos_fb_users AS a,
jos_comprofiler AS b
SET
a.ordering = b.fbordering,
a.signature = b.fbsignature
WHERE a.userid = b.user_id
The above procedure assumes that your Joomla table prefix is "jos_".
The reason that your attempt failed was an error in your WHERE clause.