By Marc on Wednesday, 12 September 2018
Posted in General
Likes 0
Views 540
Votes 0
Hey Marc,

This should be included the latest version of Easysocial, you can take a look of my attached screenshot below.

If the user already requested this before, system will return him this following message.

You have already submitted a verification request. For more information please contact site admin.


If this message still not appear for you, perhaps you can start a new thread on our forum and provide us with your site backend and FTP access so we can better have a check.


Hi there,

When we use the request verification menu, it works fine when the member is not verified.
However, we get an error if the member is already verified.

We are using the latest EasySocial 2.2.4 and still get the 500 error.
We are also using the Office template, but testing with Prostar template gives the same error.
Based on what i checked this user account 'kiwi_xxx', the strange part is somehow this table `kk31_social_verification_requests` doesn't record this 'kiwi_xxx' user request verification before.

May i know do you have remove any record from this table before `kk31_social_verification_requests` or how to you verify this user last time? Because when the user request for this verification from frontend, it will store 1 row record into this table.

Once admin approve this user verification, that row record will not delete it, that `state` value will mark it as 1, mean this user already verified.

If this user verified it manually from backend under Easysocial user listing page, it seems like that is bug, can you try download my attached file and replace into this file location and see how it goes JoomlaFolder/administrator/components/com_easysocial/includes/verification/verification.php
·
Wednesday, 12 September 2018 20:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you.
New file fixed the problem.

We have many members who are verified by other means (eg attending one of our events) and we verify them from the back-end without waiting for them to submit a "Request for verification".
This means there is never any record of the verification request in the #_social_verification_requests table.
So we get the above mentioned errors.

The new verification.php file you provided resolves this problem.
Now things are working correctly irrespective of how the verification was done.
·
Friday, 14 September 2018 14:53
·
0 Likes
·
0 Votes
·
0 Comments
·
You're most welcome, this fix will included in next release version.
·
Friday, 14 September 2018 17:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.
·
Friday, 14 September 2018 17:19
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post