Hello,

We have recently migrated from StackIdeas EasySocial to Cre8 Social, and we are currently working through a number of compatibility issues. I appreciate that the development team appears to be actively working on the extension, and I’m hoping we can get a quick workaround for this particular issue.

We are currently getting a 500 error:

The class SocialFieldTableUserRelations does not exist for this field.

Go to:

Users → Custom Fields → Relationship Status

The field is provided by the following app:

• App: Relationship Status – Allows users to create relationship status type fields in Social
• Version: 2.1.0

The error occurs when a user has a Relationship Status value saved:

1. Visit that user's About page → 500 error
2. If the currently logged-in user has a Relationship Status value saved, going to Edit Profile also results in the same error.

I have also tried unpublishing the Relationship Status app, expecting the field to be ignored once the app is unpublished. However, the error still occurs.

The About page error ends with:

SocialFieldModelUserRelations->getActorRelationship() JROOT/media/com_easysocial/apps/fields/user/relationship/relationship.php:220 SocialFieldsUserRelationship->onDisplay() JROOT/administrator/components/com_easysocial/includes/fields/handlers.php:42
SocialFieldHandlers->getOutput() JROOT/administrator/components/com_easysocial/includes/fields/handlers.php:320
SocialFieldHandlers->onDisplay() JROOT/administrator/components/com_easysocial/includes/fields/triggers.php:313
SocialFields->trigger() JROOT/administrator/components/com_easysocial/models/users.php:1207
EasySocialModelUsers->getAbout() JROOT/components/com_easysocial/views/profile/view.html.php:300

For Edit Profile, the call stack includes:

SocialFieldModelUserRelations->getActorRelationship() JROOT/media/com_easysocial/apps/fields/user/relationship/relationship.php:37

The main issue appears to be that the Relationship Status field is still being processed even after the app has been unpublished, and the required SocialFieldTableUserRelations class cannot be found.

Since this is happening on a production site, could you please provide a workaround as soon as possible to prevent users from reaching the 500 error page?

In particular, I'd appreciate guidance on either:

1. Completely disabling/skipping this field when the Relationship Status app is unpublished, or
2. Temporarily disabling the Relationship Status field/trigger through configuration or another supported method, or
3. Providing a patch/workaround until the underlying issue is fixed.

Please let me know if you need any additional information from the production site to reproduce the issue.

Thank you.

Hello Pascal,

Thank you for quick response while you are on holidays.

At this moment I have hide the Relationship Status field from Profile pages: about and edit profile. I am able to access the pages without error now but we need that field to be active and visible to all our site users.

Hi Pascal,

Have you tried to add Relationship status field and checked the issue? 
On admin side when accessing user details, If user have value added in that field it throws error:
500 The class SocialFieldTableUserRelations does not exist for this field.

Hi Pascal,

Thank you for reproducing issue on your side and planning to patch in next release.

I'll wait for the next release to check the fix.

Hi Pascal,

Thank you for the fix, Yes both pages are now showing relationship status field and values with out issue.