By Andy on Thursday, 19 March 2015
Posted in Technical Issues
Replies 11
Likes 0
Views 859
Votes 0
If someone tries to create an account on my site with the standard quick registration they are getting hit with this ugly error......

TABLE '(my db).JOS_SOCIAL_PRIVACY' DOESN'T EXIST SQL=INSERT INTO `CA1_SOCIAL_PRIVACY_ITEMS` (`PRIVACY_ID`, `USER_ID`, `UID`, `TYPE`, `VALUE`) SELECT `D`.`ID` AS `PRIVACY_ID`, '3689' AS `USER_ID`, `A`.`ID` AS `UID`, `D`.`TYPE`, `D`.`VALUE` FROM `CA1_SOCIAL_FIELDS` AS `A` LEFT JOIN `CA1_SOCIAL_FIELDS_STEPS` AS `B` ON `B`.`ID` = `A`.`STEP_ID` LEFT JOIN `CA1_SOCIAL_APPS` AS `C` ON `C`.`ID` = `A`.`APP_ID` LEFT JOIN (SELECT PI.`ID`, PI.TYPE, PI.RULE, IFNULL(PIM.`VALUE`, PI.VALUE) AS `VALUE` FROM JOS_SOCIAL_PRIVACY AS PI LEFT JOIN JOS_SOCIAL_PRIVACY_MAP AS PIM ON PI.`ID` = PIM.`PRIVACY_ID` AND PIM.`UTYPE` = 'PROFILES' AND PIM.`UID` = '1' WHERE PI.`TYPE` = 'FIELD') AS `D` ON `D`.`RULE` = `C`.`ELEMENT` WHERE `D`.`TYPE` = 'FIELD' AND `B`.`TYPE` = 'PROFILES' AND `B`.`UID` = '1' AND `A`.`ID` NOT IN (SELECT `E`.`UID` FROM `CA1_SOCIAL_PRIVACY_ITEMS` AS `E` WHERE `E`.`TYPE` = 'FIELD' AND `E`.`USER_ID` = '3689')

Any ideas on the cause / fix for this!
Hello Andy,

It's probably the same, I missed another section which has the jos_ prefix
·
Thursday, 19 March 2015 10:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Andy,

This is a known issue and we will be releasing another version shortly to address this issue. Temporary fix, download the attached file and upload it into /administrator/components/com_easysocial/models/
·
Thursday, 19 March 2015 02:38
·
0 Likes
·
0 Votes
·
0 Comments
·
didn't work i still get

1146 - Table 'thismightwork.jos_social_privacy' doesn't exist SQL=INSERT INTO `f7kth_social_privacy_items` (`privacy_id`, `user_id`, `uid`, `type`, `value`) SELECT `d`.`id` AS `privacy_id`, '640' AS `user_id`, `a`.`id` AS `uid`, `d`.`type`, `d`.`value` FROM `f7kth_social_fields` AS `a` LEFT JOIN `f7kth_social_fields_steps` AS `b` ON `b`.`id` = `a`.`step_id` LEFT JOIN `f7kth_social_apps` AS `c` ON `c`.`id` = `a`.`app_id` LEFT JOIN (select pi.`id`, pi.type, pi.rule, ifnull(pim.`value`, pi.value) as `value` from jos_social_privacy as pi left join f7kth_social_privacy_map as pim on pi.`id` = pim.`privacy_id` and pim.`utype` = 'profiles' and pim.`uid` = '1' where pi.`type` = 'field') AS `d` ON `d`.`rule` = `c`.`element` WHERE `d`.`type` = 'field' AND `b`.`type` = 'profiles' AND `b`.`uid` = '1' AND `a`.`id` NOT IN (SELECT `e`.`uid` FROM `f7kth_social_privacy_items` AS `e` WHERE `e`.`type` = 'field' AND `e`.`user_id` = '640')
·
Thursday, 19 March 2015 03:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes... confirming Jeff's experience here.... I've added that replacement file, refreshed all cache data, and still get the error coming up.
·
Thursday, 19 March 2015 04:00
·
0 Likes
·
0 Votes
·
0 Comments
·
There is still hard coded call to jos_social in the file Mark provided. Simply edit line 1472 in Marks file and change jos_social to #__social and it works fine. The line should read:

$privacyTable .= " from #__social_privacy as pi";
·
Thursday, 19 March 2015 04:36
·
0 Likes
·
0 Votes
·
0 Comments
·
i'll wait for an offical patch from the dev's but thanks
·
Thursday, 19 March 2015 04:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks papageek... Made that tiny tweak and yes confirming it all looks ok now....

...Hopefully someone from the SI super-hero team can just confirm this was all it needed too (so no wider implications or issues?)
·
Thursday, 19 March 2015 04:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey guys,

Please try this file instead
·
Thursday, 19 March 2015 10:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark.... I just applied the additional code tweak papageek mentioned.... Is there more in your latest file?
·
Thursday, 19 March 2015 10:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Great. Thanks Mark. Working good for me now.
·
Thursday, 19 March 2015 10:16
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem Andy
·
Thursday, 19 March 2015 10:20
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post